java.net.BindException: Address already in use: JVM_Bind

[tortoisetnt]

I am setting up a system to run on a test machine here and have been having a few problems with the port settings in JBoss.

When I start JBoss I get a message similar to the following:

java.net.BindException: Address already in use: JVM_Bind
Cause: java.rmi.server.ExportException: Port already in use: 1098; nested exception is:
java.net.BindException: Address already in use: JVM_Bind

Using netstat it appears that port 1098 is NOT being used which has left me scratching my head.

In the past I have managed to get around this by changing the ports to unlikely values (i.e. 10098). This allowed me to start JBoss once but if we needed to restart JBoss again we problem re-appears and doesn't go away without a restart of the machine or changing the port to something different and as equally unlikely.

This suggests that windows (im using 2003 server) may not be releasing ports as i expect. Has anybody come across this before or has any idea what might be happening?

Thanks in advance for your help,

James

[peterj]

Two threads realetd to this issue are

http://www.jboss.org/index.html?module=bb&op=viewtopic&t=65494

and

[url]http://www.jboss.org/index.html?module=bb&op=viewtopic&t=65377[url]

Unfortunately, neither thread appears to offer a solution. My best guess is that the Windows Active Domain, or some other administrative tool, has denied permissions on opening the port(s) in question (in one case, the person said it works fine for them at home but doesn't work at work and at work their coworker has the same problem).

[tracyorf]

In my case, there is a firewall client installed that I have to disable before starting JBoss. If the firewall client is enabled, JBoss will start okay the first time, but subsequent starts will complain of the address already in use. Disabling the firewall client, always works. This is on my development workstation which is Windows XP SP2.

[bdh]

I'm getting the exact same error as TortoiseTNT - bind error on 1098, and 1098 is definitely not in use according to Netstat, both before and after attempting to start up JBoss. What's weird is that JBoss worked just fine on this server up until a few days ago, and I know *I* didn't install anything or change any of the settings on the server.

I'm going to check my server for Windows security patches, etc. and compare to my last working logfile date to see if there's a correlation. I'll report back if I find anything interesting...

[bdh]

OK - using TCPView as suggested in one of the other threads, I was able to see that once JBoss has started, it was able to bind to 1098 after some time. So, I stopped and restarted JBoss, only to have a bind error on 1099. I went right back to TCPView and found that one of the ISS tasks grabbed up 1099.

Since we're using this server for EJB stuff only (we're running Apache on another box for serving up content), I stopped the ISS service and changed it to manual startup. Killed the existing Java process for JBoss and restarted, and viola! No errors!

Hope this helps...

Brad

[rolz]

The same problem on 4.0.3 SP1.

The problem seems to be related to ISA firewall client. You have to turn it off to make JBoss work.


I've found another solution though -

you have to remove _ALL_ ${jboss.bind.address} encounters from jboss-service.xml:

 <attribute name="Port">1099</attribute>
 <attribute name="BindAddress">${jboss.bind.address}</attribute>
 <attribute name="RmiPort">5098</attribute>
 <attribute ame="RmiBindAddress">${jboss.bind.address}</attribute>

to:

 <attribute name="Port">1099</attribute>
 <attribute name="RmiPort">5098</attribute>

[denisius]

One more solution - to set {jboss.bind.address} during start up:

jboss_home\bin\run.bat -b my.host.here

(or using -Djboss.bind.address=my.host.here and passing it to JVM)

[benoitx]

I guess it is never too late to add my £0.02 worth...

Kill GoogleTalk seems to have fixed my issue when I have a similar problem.

Benoit

[rohit1183]

I encountered this problem after I once restarted my system. I did a netstat & found that Microsoft Office communicator (Which I started before eclipse) was using port 1098. Below is the output from netstat:


TCP 172.21.50.11:1098 192.168.200.37:5060 ESTABLISHED 2528
C:\WINDOWS\system32\mswsock.dll
C:\WINDOWS\system32\WS2_32.dll
C:\Program Files\Microsoft Office Communicator\lcapi.dll
C:\WINDOWS\system32\USER32.dll
C:\Program Files\Microsoft Office Communicator\Communicator.exe
[Communicator.exe]

I closed communicator, restarted eclipse and then JBOSS worked fine. When i started communicator again even it was working fine.

[rajeshhanu]

Hi Guys,

I got also same problem with jboss 4.2.3GA.
I solved this problem with the following code in conf/jboss-server.xml

i changed the port numbers 1098, 1099 to 11098,11099.
then the error is gone.

I hope it will be worked.

[frankthetank]

From my exp MS Office or MS OfficeCommunicator will steal these ports at random times.

My solution is to shut down these two programs, then start up JBoss again and restart them.
Then it will work fine for another 26853 +/- 68952 starts. ;)

[malcolmshen]

Many applications would randomly pick some available ports to use. I have also experienced this issue before. Here is how I solve this issue:

I'm using windows. For linux, you may find similar commands.
1. In MS-DOS, send command "netstat -ao". You can get network information for all processes.
2. Find out the one using port 1098, get the PID.
3. Find out the process with the PID you just got from windows task manager and shut it down.
4. Restart JBoss.
5. Restart the application you've just shutdown.

Hope this helps.

[developeraaron]

I ran netstat -ab on Windows XP and found that Firefox was using ports 1097, 1098, 1099, and 1100. I currently have firefox 3.0.9 and multiple development plug-ins. I stoped firefox and restarted my JBoss server and it worked!
I then restarted firefox and changed to ports 3031, 3032, 3033, and 3034.

[xmedeko]

Windows systems do not conform to RFC, so they assign ports lower then 32k for the client processes.

For WindowsXP use this http://support.microsoft.com/kb/314053 It help to release the used ports quickly. If I ermember it right, Vista should have some settings to limit port numbers for clients. W7 shoudl do it fine.

[darkziik]

The solution to this problem is: setup the local machine IP into .bat installer of JBoss service. If you setup other IP into installer, JBoss can´t start correctly.([e-mail])