Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
java.util.concurrent.TimeoutException for meta connect #843
We are facing an issue where occassionally for meta-connect calls from client,
Logs are attached.
1)What is causing this exception? Is there a way to resolve this ?
2)From stack trace the exception thrown is TimeoutException which should have resulted in error code 408. But client is recieving a 500 internal server error
Seems to me that you are hitting one or more Tomcat bugs.
The logs are too short to be useful. If you attach the full logs, I may be able to interpret better what's going on.
This is what I found from your logs.
A server event happens, the
and the server has
Now, the message arriving from the client has the timestamp extension, and the time is right (
This seems a bug in the client.
What client are you using?
CometD is definitely 4.0.x from your logs, not 3.1.4.
Do you have the client-side DEBUG logs?
@princejt can you please detail exactly how is your system architected?
Is there any network element (reverse proxies, firewalls, load balancers, etc.) in between the client and the server that may cache or otherwise alter the request body, or delay responses, or change in some way the normal traffic?
Can you get the client DEBUG logs?
The client version/upgrade isn't something driven by us. But will check if that can happen and see if that resolves the issue.
I dont have the client side debug logs right now. Will share as soon as I have it.
The request from the browser goes to a node.js server which act as a proxy and forwards the request to the cometd java server. There is a loadbalancer between the node.js server and cometd server.
We are working with client team to get the additional information.
Meanwhile trying to figure out why client is recieving 500 error.
From stack trace the exception thrown is TimeoutException which should have resulted in error code 408. But client is recieving a 500 internal server error
Figured out the reason for change in response code.
sendError we set
Tomcat is searching for corresponding error page of the exception. Since no page is mapped status code is updated to 500.
Also identified this exception is occurring when browser is refreshed.