[jbosstools-issues] [JBoss JIRA] (JBIDE-10074) shutdown the second time throw stack trace to the console

[Andre Dietisheim (Issue Comment Edited) (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-10074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12639316#comment-12639316 ] 

Andre Dietisheim edited comment on JBIDE-10074 at 11/2/11 11:49 AM:
--------------------------------------------------------------------

If I understand your report right, you actually run the shutdown batch a 2nd time (just after running it once already) and it showed you the above stack-trace?
If that is the case then you filed a bug against jboss tools whereas this is a jboss as (and not tooling) related issue.

Could you please indicate what AS you're trying to stop?
                
      was (Author: adietish):
    If I understand your report right, you actually run the shutdown batch a 2nd time (just after running it once already) and it showed you the above stack-trace?
Could you please indicate what AS you're trying to stop?
                  
> shutdown the second time throw stack trace to the console
> ---------------------------------------------------------
>
>                 Key: JBIDE-10074
>                 URL: https://issues.jboss.org/browse/JBIDE-10074
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: JBossAS/Servers
>         Environment: Windows 7
>            Reporter: Larry Chan
>            Assignee: Rob Stryker
>            Priority: Minor
>
> I'm filing for my coworker who doesn't have an account here.
> shutdown.bat -o 16.89.22.157
> Exception in thread "main" java.io.IOException: Failed to retrieve RMIServer stu
> b: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectE
> xception: Connection refused to host: 16.89.22.157; nested exception is:
>         java.net.ConnectException: Connection refused: connect]
>         at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:33
> 8)
>         at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFacto
> ry.java:248)
>         at org.jboss.Shutdown.main(Shutdown.java:235)
> Caused by: javax.naming.ServiceUnavailableException [Root exception is java.rmi.
> ConnectException: Connection refused to host: 16.89.22.157; nested exception is:
>         java.net.ConnectException: Connection refused: connect]
>         at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java
> :101)
>         at com.sun.jndi.toolkit.url.GenericURLContext.lookup(GenericURLContext.j
> ava:185)
>         at javax.naming.InitialContext.lookup(InitialContext.java:392)
>         at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnect
> or.java:1886)
>         at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.j
> ava:1856)
>         at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:25
> 7)
>         ... 2 more
> Caused by: java.rmi.ConnectException: Connection refused to host: 16.89.22.157;
> nested exception is:
>         java.net.ConnectException: Connection refused: connect
>         at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:601)
>         at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198
> )
>         at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184)
>         at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:322)
>         at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
>         at com.sun.jndi.rmi.registry.RegistryContext.lookup(RegistryContext.java
> :97)
>         ... 7 more
> Caused by: java.net.ConnectException: Connection refused: connect
>         at java.net.PlainSocketImpl.socketConnect(Native Method)
>         at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
>         at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
>         at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
>         at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
>         at java.net.Socket.connect(Socket.java:529)
>         at java.net.Socket.connect(Socket.java:478)
>         at java.net.Socket.<init>(Socket.java:375)
>         at java.net.Socket.<init>(Socket.java:189)
>         at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirect
> SocketFactory.java:22)
>         at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMaster
> SocketFactory.java:128)
>         at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:595)
>         ... 12 more
> Press any key to continue . . .
> EXPECTED BEHAVIOR: 
> It is better and more standard just output message of "already shutdown".

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira