Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <2043732895.1252294497708.JavaMail.jira@brutus>
Date: Sun, 6 Sep 2009 20:34:57 -0700 (PDT)
From: "Bin He (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Commented: (GERONIMO-4849) Such warning will be shown after
 deleted a remote monitoring server via JMX
In-Reply-To: <1301568765.1252294257533.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ 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.