wojciech.kapcia@tigase.net opened 4 years ago
|
|
@wojtek I'm not able to replicate the issue - the timer is working correctly for me. I've only got that entry when I stopped processing of the request with a debugger. Could you state JVM which is used in your case? Maybe JVM changed something and the issue is JVM specific. In my testing I was using TTS-NG config for Tigase 8.1.0, so it used following JVM:
|
|
I'm using rather normal configuration of the server and Java is in the following version:
From the config dump:
I was just working on #issue #88 and was making a lot of requests and for example (from IDEA):
Also generated a lot of entries:
|
|
@wojtek Were you executing multiple calls/requests at the same time? I'm asking as this timer will fire only if the request was received but not started executing in |
|
Nope. I just started fresh copy of Tigase, pasted:
in idea and executed it. There result was rather normal:
And almost immediately I saw in the logs:
What's curious is the For completeness, this is my configuration:
Log (with 'http' enabled) attached (with trimmed startup) |
|
With IDEA I was able to replicate the issue and with increased logging found out that there are some requests that are accepted but never executed - just like connection would be established and then dropped without sending any HTTP request or data. I've added a way to cancel timer for those requests (as they just ended anyway), and that solved the issue. |
Type |
Bug
|
Priority |
Minor
|
Assignee | |
Version |
tigase-server-8.1.0
|
-
Customers/catapush-s-r-l#16 You are not authorized to access this issue
Execute any simple call to REST API (for example those from https://projects.tigase.net/issue/helpdeskpr-546#focus=streamItem-4-26369.0-0):
And it will result in WARNING in the logs, even though the connection is closed correctly
I think we should fix the timer, or at least don't print it with WARNING…