You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Shiny Cheng (JIRA)" <ji...@apache.org> on 2009/09/07 05:30:57 UTC
[jira] Created: (GERONIMO-4849) Such warning will be shown after
deleted a remote monitoring server via JMX
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
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.
Re: [jira] Commented: (GERONIMO-4849) Such warning will be shown
after deleted a remote monitoring server via JMX
Posted by Siqi Du <si...@gmail.com>.
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) <ji...@apache.org> 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.
>
>
[jira] Assigned: (GERONIMO-4849) Such warning will be shown after
deleted a remote monitoring server via JMX
Posted by "Shawn Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shawn Jiang reassigned GERONIMO-4849:
-------------------------------------
Assignee: Shawn Jiang
> 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
> Assignee: Shawn Jiang
> Fix For: 2.2
>
> Attachments: monitor_jmx_2.1.patch, 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.
[jira] Updated: (GERONIMO-4849) Such warning will be shown after
deleted a remote monitoring server via JMX
Posted by "Siqi Du (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Siqi Du updated GERONIMO-4849:
------------------------------
Attachment: monitoring_jmx.patch
Please help to check it, ^_^
> 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.
[jira] Updated: (GERONIMO-4849) Such warning will be shown after
deleted a remote monitoring server via JMX
Posted by "Siqi Du (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Siqi Du updated GERONIMO-4849:
------------------------------
Attachment: (was: monitoring_jmx.patch)
> 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.
[jira] Commented: (GERONIMO-4849) Such warning will be shown after
deleted a remote monitoring server via JMX
Posted by "Siqi Du (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12752857#action_12752857 ]
Siqi Du commented on GERONIMO-4849:
-----------------------------------
It seems that the connection to JMXServer is not closed after used, I will keep eyes on this.
> 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
>
>
> 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.
[jira] Commented: (GERONIMO-4849) Such warning will be shown after
deleted a remote monitoring server via JMX
Posted by "Shawn Jiang (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (GERONIMO-4849) Such warning will be shown after
deleted a remote monitoring server via JMX
Posted by "Shawn Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12754848#action_12754848 ]
Shawn Jiang commented on GERONIMO-4849:
---------------------------------------
1, I noticed you only added mrc.dispose() at part of finally blocks. Shouldn't mrc.dispose() be added to all finally blocks ?
2, Please identify from which branch your patch is created.
> 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.
[jira] Updated: (GERONIMO-4849) Such warning will be shown after
deleted a remote monitoring server via JMX
Posted by "Siqi Du (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Siqi Du updated GERONIMO-4849:
------------------------------
Attachment: monitor_jmx_2.1.patch
branch 2.1 also has the same problem, and the patch monitor_jmx_2.1.patch could help to solve it.
> 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: monitor_jmx_2.1.patch, 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.
[jira] Resolved: (GERONIMO-4849) Such warning will be shown after
deleted a remote monitoring server via JMX
Posted by "Shawn Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shawn Jiang resolved GERONIMO-4849.
-----------------------------------
Resolution: Fixed
Applied the patch to branch 21, branch 22, trunk. Thanks Siqi for the patch !
> 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
> Assignee: Shawn Jiang
> Fix For: 2.2
>
> Attachments: monitor_jmx_2.1.patch, 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.
[jira] Commented: (GERONIMO-4849) Such warning will be shown after
deleted a remote monitoring server via JMX
Posted by "Bin He (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12752001#action_12752001 ]
Bin He commented on GERONIMO-4849:
----------------------------------
When I create a ejb server,it doesn't have that 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
>
>
> 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.
[jira] Updated: (GERONIMO-4849) Such warning will be shown after
deleted a remote monitoring server via JMX
Posted by "Siqi Du (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Siqi Du updated GERONIMO-4849:
------------------------------
Attachment: monitoring_jmx.patch
> 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.