-
Notifications
You must be signed in to change notification settings - Fork 870
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Orientdb connection problem #4842
Comments
Please could you send us the entire log? I'm interested to the underlying reason of such exception. It should be lower in logs. |
Here is the full log. The interrupt exception comes from us trying to interrupt the thread which is not responding in 10 sec. We have seen it many times that it gets stuck @ORemoteConnectionManager.acquire(ORemoteConnectionManager.java:101).
|
Even Better, we took an automated thread dump when this problem happened, i'm gonna paste it in the next comment: |
|
[2015-08-20 19:44:08,278] [[notification-distributor-service-v1.0.0-SNAPSHOT].mule-stats-notification-consume-flow.stage1.37] [WARN] [LogUtils:44] [warn] [serviceName:NotificationDistributor]=> [eventType:FindSubscribersTimeout] [topics:[/sports/cricket/series/25/teams/60002, /sports/cricket/series/25/teams/60001, /sports/cricket/series/25/matches/Test20150705]] [exception:2015-08-20 19:44:07 "StreamGobblerThread-7" prio=10 tid=0x00007f0438503800 nid=0x2768 runnable [0x00007f0382c87000] |
Hi @sajid2045, fixing the shutdown call this should be fixed, can i close it ? |
@tglman : are you talking about the tx.shutdown() call inside the client code? |
2.1.2 seems to have fixed it. closing |
We are seeing a lot of connection issue in our soon to be live production system.
Please let me know if you need any more logs.
The text was updated successfully, but these errors were encountered: