mrc.dispose() is used to close jmx connection, I have check all the code used mrc to ensure every possible jmx connection is closed. I create the patch from branch 2.2 and it seems that 2.1 has not been tested according to the bug description.
-Siqi On Mon, Sep 14, 2009 at 3:20 PM, Shawn Jiang (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/GERONIMO-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754849#action_12754849] > > Shawn Jiang commented on GERONIMO-4849: > --------------------------------------- > > Does 21 branch have the same problem ? > > > Such warning will be shown after deleted a remote monitoring server via > JMX > > > --------------------------------------------------------------------------- > > > > Key: GERONIMO-4849 > > URL: https://issues.apache.org/jira/browse/GERONIMO-4849 > > Project: Geronimo > > Issue Type: Bug > > Security Level: public(Regular issues) > > Components: monitoring > > Affects Versions: 2.2 > > Environment: winxp sp3, jdk 1.6 > > Reporter: Shiny Cheng > > Fix For: 2.2 > > > > Attachments: monitoring_jmx.patch > > > > > > The following warning will be shown after these steps. > > First, create a remote monitoring server via JMX and meanwhile, start the > remote server. Then, you delete the monitoring server and stop the remote > server. You will see the following information via log or command line. > > WARN [misc] 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: 9.123.233.70; nested > exception is: > > java.net.ConnectException: Connection refused: connect] > > WARN [misc] 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: 9.123.233.70; nested > exception is: > > java.net.ConnectException: Connection refused: connect] > > WARN [rmi] Failed to call the method close():java.rmi.ConnectException: > Connection refused to host: 9.123.233.70; nested exception is: > > java.net.ConnectException: Connection refused: connect > > WARN [misc] Failed to check connection: java.net.ConnectException: > Connection refused: connect > > WARN [misc] stopping > > WARN [rmi] Failed to call the method close():java.rmi.ConnectException: > Connection refused to host: 9.123.233.70; nested exception is: > > java.net.ConnectException: Connection refused: connect > > WARN [misc] Failed to check connection: java.net.ConnectException: > Connection refused: connect > > WARN [misc] stopping > > WARN [misc] 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: 9.123.233.70; nested > exception is: > > java.net.ConnectException: Connection refused: connect] > > WARN [rmi] Failed to call the method close():java.rmi.ConnectException: > Connection refused to host: 9.123.233.70; nested exception is: > > java.net.ConnectException: Connection refused: connect > > WARN [misc] Failed to check connection: java.net.ConnectException: > Connection refused: connect > > WARN [misc] stopping > > WARN [misc] 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: 9.123.233.70; nested > exception is: > > java.net.ConnectException: Connection refused: connect] > > WARN [misc] 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: 9.123.233.70; nested > exception is: > > java.net.ConnectException: Connection refused: connect] > > WARN [rmi] Failed to call the method close():java.rmi.ConnectException: > Connection refused to host: 9.123.233.70; nested exception is: > > java.net.ConnectException: Connection refused: connect > > WARN [misc] Failed to check connection: java.net.ConnectException: > Connection refused: connect > > WARN [misc] stopping > > WARN [rmi] Failed to call the method close():java.rmi.ConnectException: > Connection refused to host: 9.123.233.70; nested exception is: > > java.net.ConnectException: Connection refused: connect > > WARN [misc] Failed to check connection: java.net.ConnectException: > Connection refused: connect > > WARN [misc] stopping > > WARN [misc] 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: 9.123.233.70; nested > exception is: > > java.net.ConnectException: Connection refused: connect] > > WARN [rmi] Failed to call the method close():java.rmi.ConnectException: > Connection refused to host: 9.123.233.70; nested exception is: > > java.net.ConnectException: Connection refused: connect > > WARN [misc] Failed to check connection: java.net.ConnectException: > Connection refused: connect > > WARN [misc] stopping > > I wonder maybe there are something left after having deleted the remote > monitoring server? Please help me to verify this. thx. :) > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > >
