Hello,

I've been working with JBoss 3.2.6 to run a propietary application for more than one year now, and had no problem until now. But it appears that the Naming Service cannot start anymore, though the same configuration (same version of JBoss with the same version of the propietary application, same configuration files except for the TCP ports used) still works on another server.
I'm sure that no configuration change has been done for more than a year now.

From what I can see in the logs, the problem is that the port 11098 is already in use when the naming service tries to bind it. I checked that the port was free before starting JBoss, and I tried to reserve the port as explained on the wiki page http://wiki.jboss.org/wiki/DebugBindException, but it was unsuccessful.

I thus wrote a simple test software that just tries to bind the port, and then immediately frees it, all that in a loop, until an error occurs. Before starting JBoss, this software runs normally, but it stops when JBoss starts : I conclude from this that this is JBoss itself which reserves the port. But JBoss then fails with the BindException, and then the ports gets free again.

I tried to configure several ports, but the problem remained.
I also googled a while, but only found cases where the port was obviously reserved by another application before JBoss starts.

I have now no idea on what I can do to solve this issue. It may be a race condition, but this kind of problem is usually difficult to reproduce, and may appear or disappear according to subtil runtime conditions. I'm thus not really keen on just upgrading JBoss, as I will have no clue on what was the problem, and if it is really solved or not in the new version.

Does someone already encountered such an issue ? Is it a configuration problem, or is it a known issue solved in the latest version JBoss ?

Thank you very much in advance for your help !

Pierre