Skip to content
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.

Sign up for GitHub

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

Jump to bottom

It shouldn't be an error if the jmx plugin looses cached connections #8

Open
tomdz opened this issue Feb 29, 2012 · 1 comment
Open

It shouldn't be an error if the jmx plugin looses cached connections #8

tomdz opened this issue Feb 29, 2012 · 1 comment

Comments

@tomdz
Copy link
Contributor

tomdz commented Feb 29, 2012

The error seems to happen when the connection is actually used, e.g. in the shutdown method.
@tomdz tomdz mentioned this issue Mar 1, 2012
Closed
tomdz pushed a commit that referenced this issue Mar 1, 2012
Fix for #8: It shouldn't be an error if the jmx plugin looses cached …
974d469 
…connections
tomdz pushed a commit that referenced this issue Mar 1, 2012
Added some more reconnect handling and related documentation (for #8)
d1ed0ab
@tomdz tomdz closed this as completed Mar 1, 2012
@tomdz tomdz reopened this Mar 9, 2012
@tomdz
Copy link
Contributor Author

tomdz commented Mar 9, 2012

There might be another exception that the plugin has to catch:

Mar 9, 2012 7:30:32 PM ClientCommunicatorAdmin restart
WARNING: Failed to restart: java.io.IOException: Failed to get a RMI stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: [host]; nested exception is:
java.net.ConnectException: Connection refused]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tomdz