| Shutdown issues after modifying Virgo's ports [message #650379] |
Mon, 24 January 2011 12:02  |
Eclipse User |
|
|
|
Hello
I modified the file tomcat-server.xml to change the ports used by VIrgo. After that, I am not able to stop the server using shutdown.sh. Each time I try, I get an exception "The Server could not be reached, it may already be stopped.", and I need to kill the Virgo process to be able to stop it.
On a distant server (where I might not have all ports permissions), I get the following exception :
java.rmi.ConnectIOException: Exception creating connection to:
192.168.3.152; nested exception is:
java.net.NoRouteToHostException: No route to host at
sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:614) 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.invoke(UnicastRef.java:110) at
javax.management.remote.rmi.RMIServerImpl_Stub.newClient(Unknown Source) at
javax.management.remote.rmi.RMIConnector.getConnection(RMIConnector.java:2327) at
javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:279) at
javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248) at
org.eclipse.virgo.kernel.shutdown.ShutdownClient.doShutdown(ShutdownClient.java:63) at
org.eclipse.virgo.kernel.shutdown.ShutdownClient.performShutdown(ShutdownClient.java:50) at
org.eclipse.virgo.kernel.shutdown.ShutdownClient.main(ShutdownClient.java:43)
Caused by: java.net.NoRouteToHostException: No route to host
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
com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:559) at
com.sun.net.ssl.internal.ssl.SSLSocketImpl.<init>(SSLSocketImpl.java:360) at
com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl.createSocket(SSLSocketFactoryImpl.java:71) at
javax.rmi.ssl.SslRMIClientSocketFactory.createSocket(SslRMIClientSocketFactory.java:105) at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:595)
... 10 more
Did I miss something in the configuration, or is it a bug i need to open in Bugzilla?
|
|
|
|
|
|
|
|
| Re: Shutdown issues after modifying Virgo's ports [message #651552 is a reply to message #651400] |
Mon, 31 January 2011 11:00  |
| Eclipse User |
|
|
|
Thanx for your answer. I will check if the issue is still existing on this server, but this is a production machine, and I don't have all the access. I'm not sure if the JMX port have been modified on this Virgo instance. But there is a big chance that the port is not opened.
On the other hand, I still have my shutdown issue on my developement machine. Each time I start the server with a ./startup.sh -clean &, and I try to shut it down with ./shutdown.sh, I get the message "The Server could not be reached, it may already be stopped.", and I have to kill the Virgo process to stop it. I think this is a bug in Virgo, but I would like a go before I open a bug in Bugzilla...
Regards,
Lorie.
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.05700 seconds
Home