jBoss port bind error

Sometimes, I’ve found that jBoss won’t start up cleanly because of the following error:

2008-06-11 13:38:56,820 ERROR [Naming] Could not start on port 1099
java.net.BindException: Address already in use: JVM_Bind
        at java.net.PlainSocketImpl.socketBind(Native Method)
        at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
        at java.net.ServerSocket.bind(ServerSocket.java:319)
        at java.net.ServerSocket.<init>(ServerSocket.java:185)
        at javax.net.DefaultServerSocketFactory.createServerSocket(ServerSocketFactory.java:170)
        at org.jnp.server.Main.initBootstrapListener(Main.java:371)
        at org.jnp.server.Main.start(Main.java:321)
        at org.jboss.naming.NamingService.startService(NamingService.java:284)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
        at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
        at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
... <snip>

When I dug further into this (I used Active Ports), I found that there was already an application binding to port 1099 – a part of Symantec Antivirus called ccApp.exe.

I rebooted, but sadly to no avail. ccApp.exe remained bound to 1099.

The solution was to go into the Windows services and stop the Symantec AntiVirus service and then start jBoss. I could then safely restart Symantec AntiVirus, finding that ccApp.exe had chosen a new random port.

It's only fair to share...
Share on FacebookGoogle+Tweet about this on TwitterShare on LinkedIn

Leave a Reply