|
|
|
|
|
Re: Shutdown issues after modifying Virgo's ports [message #651400 is a reply to message #650547] |
Sun, 30 January 2011 11:55 |
|
Hi Lorie,
Any progress with the shutdown?
I think that the problem is not in the connector but with the JMX port since the exception you posted reads:
javax.management.remote.JMXConnectorFactory.connect(JMXConne ctorFactory.java:248) at
and later you have NoRouteToHost.
This basically means that the port is not available or that the server port is not bound to 192.168.3.152 but to another network adapter (if you have more than one).
|
|
|
Re: Shutdown issues after modifying Virgo's ports [message #651552 is a reply to message #651400] |
Mon, 31 January 2011 16:00 |
Lorie Pisicchio Messages: 44 Registered: October 2010 |
Member |
|
|
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.
|
|
|
|
|
Re: Shutdown issues after modifying Virgo's ports [message #653429 is a reply to message #653337] |
Wed, 09 February 2011 17:48 |
|
If you edit the property then both startup and shutdown scripts use the same value. This is of course valid only if the change is made before the server is started, otherwise the shutdown script will have no way to stop Virgo.
If you changed the JMX port before Virgo startup please open a bug.
|
|
|
|
Powered by
FUDForum. Page generated in 0.30260 seconds