Last night I received notification from Sun's Java update scheduler that 1.6.7 of the runtime was available form me to install.
I've always had Glassfish installed and co-existing with ES/SET anti-virus software quite happily.
Suddenly since scheduled update appeared, I can't get into the admin console.
The server fails to start with the following type of messages in the log file:
An error occured during initialization
com.sun.appserv.server.ServerLifecycleException: Cannot bind to URL [rmi://JGF-DELL-M4300:8686/management/rmi-jmx-connector]: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
java.net.SocketTimeoutException: Read timed out] .....
Caused by: java.io.IOException: Cannot bind to URL [rmi://JGF-DELL-M4300:8686/management/rmi-jmx-connector]: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
java.net.SocketTimeoutException: Read timed out]
Now I've got TCPView installed on my pc and if I'm reading things correctly ES/SET's software ekrn.exe is using port? or socket? 948.
If I disable the antivirus software everything boots.
Can someone tell me would scheduler or a JRE update change the way Glassfish behaves? Only I find this most peculiar and haven't had this happen before.
The only other thing I can think of is ES/SET anti-virus software has changed the port or socket it uses and this is now causing a conflict.
But the sheer conincide this started happening after the schedule update appeared. (Which I installed afterwards intially thinking this process might have been blocking Glassfish from starting up initially, but I'm still having problems,..
I have also recently deployed the javax77.jar to a webapp in Tomcat too and this relates to JMX, but since it's a seperate Web-app the chances of that causing the conflict seem extremely slim since all my other servers (Jetty, Tomcat, IIS and JBoss) aren't started so as to cause some sort of contention of ports or sockets.
[Message sent by forum member 'jgf1' (jgf1)]
http://forums.java.net/jive/thread.jspa?messageID=286138