1 2 Previous Next 20 Replies Latest reply on Sep 21, 2004 5:32 AM by Tore Gard Andersen

    Port already in use - Jboss 3.2.3 Problem

    Navdeep Newbie

      Hi,
      I hope I am posting this in the right forum. I had posted a similar problem for JBoss 3.2.2 but did not get any reply for this. In 3.2.1 this problem does not exist.
      I am using JBoss 3.2.3 on Windows 2000 Professional and JDK 1.4.1_01.

      Essentially what happens is that when I restart my JBoss 3.2.3 server, even if I have no Application of my own deployed. It reports an error

      java.rmi.server.ExportException: Port already in use: 1098; nested exception is:

      this happens for ports 1099, 1098 and 4444 mostly, but sometimes it happens for port 8080 on which Tomcat is also running. Using NetStat sometimes I see those ports as in use, though it is tough to descipher which application from netstat in Win2000 . And sometimes the ports are not even in use according to netstat . Also restarting the machine does not help either. But waiting for 20 minutes before restarting the srver clears the ports. I have checked and no other appplication seems to run on these ports. I have also tried changing these ports to 9098,9099,9444 etc. but even that does not help. Next time the server is run. it reports these ports as in use, and netstat does not show them as in use.Please help me with this, if anyone can, it is very irritating as I cant figure out why no one else is having thsi problem. And why it does not happen in JBOss 3.2.1 or 3.2.0
      Here is the printstacktrace thrown by JBoss


      11:57:32,312 INFO [NamingService] Starting jnp server
      11:57:32,421 ERROR [NamingService] Starting failed
      java.rmi.server.ExportException: Port already in use: 1098; nested exception is:
      java.net.BindException: Address already in use: JVM_Bind
      at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:243)
      at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:178)
      at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:382)
      at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:116)
      at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:145)
      at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:129)
      at java.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.java:275)
      at java.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.java:206)
      at org.jnp.server.Main.initJnpInvoker(Main.java:376)
      at org.jnp.server.Main.start(Main.java:249)
      at org.jboss.naming.NamingService.startService(NamingService.java:164)
      at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192)
      at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:976)
      at $Proxy0.start(Unknown Source)
      at org.jboss.system.ServiceController.start(ServiceController.java:394)
      at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
      at $Proxy4.start(Unknown Source)
      at org.jboss.deployment.SARDeployer.start(SARDeployer.java:226)
      at org.jboss.deployment.MainDeployer.start(MainDeployer.java:832)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:642)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:605)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:589)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
      at $Proxy5.deploy(Unknown Source)
      at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:384)
      at org.jboss.system.server.ServerImpl.start(ServerImpl.java:291)
      at org.jboss.Main.boot(Main.java:150)
      at org.jboss.Main$1.run(Main.java:395)
      at java.lang.Thread.run(Thread.java:536)
      Caused by: java.net.BindException: Address already in use: JVM_Bind
      at java.net.PlainSocketImpl.socketBind(Native Method)
      at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:331)
      at java.net.ServerSocket.bind(ServerSocket.java:309)
      at java.net.ServerSocket.(ServerSocket.java:183)
      at org.jboss.net.sockets.DefaultSocketFactory.createServerSocket(DefaultSocketFactory.java:79)
      at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:615)
      at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:231)
      ... 44 more
      11:57:32,703 WARN [ServiceController] Problem starting service jboss:service=Naming
      java.rmi.server.ExportException: Port already in use: 1098; nested exception is:
      java.net.BindException: Address already in use: JVM_Bind
      at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:243)
      at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:178)
      at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:382)
      at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:116)
      at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:145)
      at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:129)
      at java.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.java:275)
      at java.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.java:206)
      at org.jnp.server.Main.initJnpInvoker(Main.java:376)
      at org.jnp.server.Main.start(Main.java:249)
      at org.jboss.naming.NamingService.startService(NamingService.java:164)
      at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192)
      at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:976)
      at $Proxy0.start(Unknown Source)
      at org.jboss.system.ServiceController.start(ServiceController.java:394)
      at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
      at $Proxy4.start(Unknown Source)
      at org.jboss.deployment.SARDeployer.start(SARDeployer.java:226)
      at org.jboss.deployment.MainDeployer.start(MainDeployer.java:832)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:642)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:605)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:589)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
      at $Proxy5.deploy(Unknown Source)
      at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:384)
      at org.jboss.system.server.ServerImpl.start(ServerImpl.java:291)
      at org.jboss.Main.boot(Main.java:150)
      at org.jboss.Main$1.run(Main.java:395)
      at java.lang.Thread.run(Thread.java:536)
      Caused by: java.net.BindException: Address already in use: JVM_Bind
      at java.net.PlainSocketImpl.socketBind(Native Method)
      at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:331)
      at java.net.ServerSocket.bind(ServerSocket.java:309)
      at java.net.ServerSocket.(ServerSocket.java:183)
      at org.jboss.net.sockets.DefaultSocketFactory.createServerSocket(DefaultSocketFactory.java:79)
      at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:615)
      at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:231)
      ... 44 more
      11:57:32,968 INFO [JNDIView] Started jboss:service=JNDIView
      11:57:32,984 INFO [SecurityConfig] Started jboss.security:service=SecurityConfig
      11:57:33,218 INFO [XMLLoginConfig] Started jboss.security:service=XMLLoginConfig
      11:57:33,296 INFO [JaasSecurityManagerService] Started jboss.security:service=JaasSecurityManager
      11:57:33,375 INFO [TransactionManagerService] Started jboss:service=TransactionManager
      11:57:33,437 ERROR [JRMPInvoker] Starting failed
      java.rmi.server.ExportException: Port already in use: 4444; nested exception is:
      java.net.BindException: Address already in use: JVM_Bind
      at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:243)
      at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:178)
      at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:382)
      at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:116)
      at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:145)
      at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:129)
      at java.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.java:275)
      at java.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.java:206)
      at org.jboss.invocation.jrmp.server.JRMPInvoker.exportCI(JRMPInvoker.java:394)
      at org.jboss.invocation.jrmp.server.JRMPInvoker.startService(JRMPInvoker.java:305)
      at org.jboss.invocation.jrmp.server.JRMPInvoker$1.startService(JRMPInvoker.java:108)
      at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192)
      at org.jboss.invocation.jrmp.server.JRMPInvoker.start(JRMPInvoker.java:566)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:976)
      at $Proxy0.start(Unknown Source)
      at org.jboss.system.ServiceController.start(ServiceController.java:394)
      at org.jboss.system.ServiceController.start(ServiceController.java:411)
      at org.jboss.system.ServiceController.start(ServiceController.java:411)
      at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
      at $Proxy4.start(Unknown Source)
      at org.jboss.deployment.SARDeployer.start(SARDeployer.java:226)
      at org.jboss.deployment.MainDeployer.start(MainDeployer.java:832)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:642)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:605)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:589)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
      at $Proxy5.deploy(Unknown Source)
      at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:384)
      at org.jboss.system.server.ServerImpl.start(ServerImpl.java:291)
      at org.jboss.Main.boot(Main.java:150)
      at org.jboss.Main$1.run(Main.java:395)
      at java.lang.Thread.run(Thread.java:536)
      Caused by: java.net.BindException: Address already in use: JVM_Bind
      at java.net.PlainSocketImpl.socketBind(Native Method)
      at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:331)
      at java.net.ServerSocket.bind(ServerSocket.java:309)
      at java.net.ServerSocket.(ServerSocket.java:183)
      at org.jboss.net.sockets.DefaultSocketFactory.createServerSocket(DefaultSocketFactory.java:79)
      at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:615)
      at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:231)
      ... 48 more
      11:57:33,734 WARN [ServiceController] Problem starting service jboss:service=invoker,type=jrmp
      java.rmi.server.ExportException: Port already in use: 4444; nested exception is:
      java.net.BindException: Address already in use: JVM_Bind
      at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:243)
      at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:178)
      at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:382)
      at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:116)
      at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:145)
      at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:129)
      at java.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.java:275)
      at java.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.java:206)
      at org.jboss.invocation.jrmp.server.JRMPInvoker.exportCI(JRMPInvoker.java:394)
      at org.jboss.invocation.jrmp.server.JRMPInvoker.startService(JRMPInvoker.java:305)
      at org.jboss.invocation.jrmp.server.JRMPInvoker$1.startService(JRMPInvoker.java:108)
      at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:192)
      at org.jboss.invocation.jrmp.server.JRMPInvoker.start(JRMPInvoker.java:566)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:976)
      at $Proxy0.start(Unknown Source)
      at org.jboss.system.ServiceController.start(ServiceController.java:394)
      at org.jboss.system.ServiceController.start(ServiceController.java:411)
      at org.jboss.system.ServiceController.start(ServiceController.java:411)
      at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
      at $Proxy4.start(Unknown Source)
      at org.jboss.deployment.SARDeployer.start(SARDeployer.java:226)
      at org.jboss.deployment.MainDeployer.start(MainDeployer.java:832)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:642)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:605)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:589)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:546)
      at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:177)
      at $Proxy5.deploy(Unknown Source)
      at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:384)
      at org.jboss.system.server.ServerImpl.start(ServerImpl.java:291)
      at org.jboss.Main.boot(Main.java:150)
      at org.jboss.Main$1.run(Main.java:395)
      at java.lang.Thread.run(Thread.java:536)
      Caused by: java.net.BindException: Address already in use: JVM_Bind
      at java.net.PlainSocketImpl.socketBind(Native Method)
      at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:331)
      at java.net.ServerSocket.bind(ServerSocket.java:309)
      at java.net.ServerSocket.(ServerSocket.java:183)
      at org.jboss.net.sockets.DefaultSocketFactory.createServerSocket(DefaultSocketFactory.java:79)
      at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:615)
      at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:231)
      ... 48 more

        • 1. Re: Port already in use - Jboss 3.2.3 Problem
          Jon Barnett Master

          It seems like the nested exception is probably the cause, rather than the report port problem. So is the address correctly set for the system such that the JVM can resolve it? See the FAQ forum on 127.0.0.1 if you have note already browsed that topic. Also, you might try setting a bind address - see the Java environment variable, jboss.bind.address used in JBOSS_HOME/server/default/conf/jboss-service.xml - and see if that affects anything.

          • 2. Re: Port already in use - Jboss 3.2.3 Problem
            Navdeep Newbie

            Hi,
            thanks for the reply. Maybe I am missing the point here, but do you want me to change the ports that JBoss is using in the jboss-service.xml . If yes then I have already tried that and, the next time I restart, I face the same problem.

            Any other idea that I could try?

            • 3. Re: Port already in use - Jboss 3.2.3 Problem
              Jon Barnett Master

              No, indications are that it probably isn't port related. The binding problem looks to be related to the address - so make sure that the hosts file and networking is properly set up on your machine.

              • 4. Re: Port already in use - Jboss 3.2.3 Problem
                Colin Wilson-Salt Newbie

                 

                "colinws" wrote:
                We've seen that problem here. If you wait long enough after stoppping JBoss before restarting it then it will start up fine.

                The problem doesn't appear on WinXP, and is only on certain versions of JBoss. (3.2.1 and 3.2.3).

                This doesn't help you solve the problem, but at least you know you're not the only person seeing it.


                • 5. Re: Port already in use - Jboss 3.2.3 Problem
                  knuterik Newbie

                   

                  "knuterik" wrote:
                  "colinws" wrote:
                  We've seen that problem here. If you wait long enough after stoppping JBoss before restarting it then it will start up fine.

                  The problem doesn't appear on WinXP, and is only on certain versions of JBoss. (3.2.1 and 3.2.3).

                  This doesn't help you solve the problem, but at least you know you're not the only person seeing it.



                  I have the same problem on my machine.
                  - And am running Windows XP + JDK 1.4.2 + JBoss 3.2.3.
                  - And even waiting till the next day will not resolve it.

                  The problem is quite weird, since I can run JBoss for extended periods of time, with numerous restarts, re-deployments etc without a problem - and then suddenly JBoss refuses to start and nothing I do can make it start again!


                  • 6. Re: Port already in use - Jboss 3.2.3 Problem
                    knuterik Newbie

                     

                    "knuterik" wrote:
                    "colinws" wrote:
                    We've seen that problem here. If you wait long enough after stoppping JBoss before restarting it then it will start up fine.

                    The problem doesn't appear on WinXP, and is only on certain versions of JBoss. (3.2.1 and 3.2.3).

                    This doesn't help you solve the problem, but at least you know you're not the only person seeing it.



                    I have the same problem on my machine.
                    - And am running Windows XP + JDK 1.4.2 + JBoss 3.2.3.
                    - And even waiting till the next day will not resolve it.

                    The problem is quite weird, since I can run JBoss for extended periods of time, with numerous restarts, re-deployments etc without a problem - and then suddenly JBoss refuses to start and nothing I do can make it start again!


                    AND, using these forums, I was led to the solution steps:
                    1. List all active connections on your computer using "netstat -a -o"
                    2. Open your Windows task manager. On the View-Select columns menu, enable display of PID (Process identifier).
                    3. Match the PID's from the ports in question (1098 in my case).
                    4. Voila, I found out that my SonyEricsson mobile handset synchronisation SW doesn't close port 1098/1099 after using it for synchronisation with my handset, and hence, after the synch - JBoss can not start. When I then killed the S-E processes (mRouterRuntime.exe and audevicemgr.exe) JBoss started just fine again.

                    Hope this can help others, as several posts suggests others are struggling with the same or similar problems.

                    Knut Erik Ballestad


                    • 7. Re: Port already in use - Jboss 3.2.3 Problem
                      ulf.klaas Newbie

                      Hi,

                      i have this problem, too.
                      I use JBoss 3.2.3, Windows 2000 Server (all Patches and SP's), Sun Java 1.4.2.
                      JBoss is started as a wrapper service at the server boot time.

                      In my case, the server services (sometimes DNS, sometimes IIS/ FTP, ...) use the Port 1098. I found out that with the tool tcpview
                      ->http://www.sysinternals.com/ntw2k/source/tcpview.shtml.

                      I tried several things:
                      1.) port-binding in /etc/services
                      2.) use another port
                      3.) disable the server services

                      But i got still this !@+{[@ problem.
                      Is there anybody, who knows a solution?

                      • 8. Re: Port already in use - Jboss 3.2.3 Problem
                        alan-uk Newbie

                        java.rmi.server.ExportException: Port already in use: 1098; nested exception is:
                        window 2000; sdk1.4.2; JBOSS 2.3.2

                        I downloaded the tool from

                        http://www.sysinternals.com/ntw2k/source/tcpview.shtml according to the information given by a user

                        I noticed even the java.exe (JVM) process is killed through the window task manager still the port 1098 is in use by the system.

                        I shutdown the my computer and restart it again and I noticed the port is not in use. JBOSS ,some times, leaves some ports open after shutting down. I do not know why

                        • 9. Re: Port already in use - Jboss 3.2.3 Problem
                          Emmanuel Eze Newbie

                          Check your computer properly to confirm that no IM that could properly use that port was started b4 Jboss. I had the same problem on my machine but figured out that MSN Messenger seem to use that same port.

                          The trick is to exit MSN Messenger, start Jboss, and then restart MSN Messenger again.

                          Hope this helps

                          Emmanuel

                          • 10. Re: Port already in use - Jboss 3.2.3 Problem
                            ulf.klaas Newbie

                            Hi,

                            I think, you haven't read all this posts!!!

                            -I don't have a running instance of Jboss
                            -I don't have any mad IM tool, Palm-Synchronisation tool or any other annoying tool on my computer, because my server is a productive server and not a playground!!!
                            -Any hints as "stopping manually the foo service and then start manually your jboss" are not very useful, because i must start JBoss, when i start the Windows OS. I use an Services-Wrapper for doing this! But, when the port 1098 is in use, the service can't start.
                            -Using another port as 1098 do not solve the problem.
                            -Binding the Windows-Services to other ports don't solve the problem.

                            The problem is:
                            Windows 2000 and JBoss 3.2.3 don't work together.


                            So, who can really solve this problem???

                            Thanx for any good ideas!

                            • 11. Re: Port already in use - Jboss 3.2.3 Problem
                              Jim Barritt Newbie

                              I have had the same symptoms - im running WinXP and have tried jboss 3.2.2 and the RC 3.2.4. Ive tried all the suggestions on this page and in the past i have seen some of them work but im still getting the bind error.

                              I tried to create some simple test code that opens a server socket or exports a remote object to the same port that jboss is complaining about and it works fine., right after i tried to start jboss and it failed.

                              The only time i can get the bind exception is if i explicitly try to open 2 sockets on the same port.

                              Using the TCPView utility mentioned on this thread i can see the ports being opened and closed so everything looks cool.

                              As mentioned elswhere in the thread, if you leave it for a while (approx 5mins) it stats up again fine.

                              I know this isnt providing any solutions but there is something going on here and it would be good to work it out - allthough the excuse for a tea break everytime i need to restart might be good ...

                              Jim

                              • 12. Re: Port already in use - Jboss 3.2.3 Problem
                                Jim Barritt Newbie

                                apologies - just noticed a typo in my previous post, i mean jbos 3.2.3

                                • 13. Re: Port already in use - Jboss 3.2.3 Problem
                                  Jim Barritt Newbie

                                  I just tried the beta developer release of 4.0.0 and it works fine, so there must be something about the 3.2.3 / 3.2.4 version which is different.

                                  • 14. Re: Port already in use - Jboss 3.2.3 Problem
                                    darren hartford Expert

                                    TCPView is a good start, and you can also use 'netstat -a' to see all ports that are in use.

                                    On Windows platforms, you need to be aware of various services that will randomly take ports. Some examples are Windows Update, Exchange/Outlook, and as you noticed IM tools, and many more than can be listed.

                                    For the safest bet on running production, look at changing the port numbers used by Jboss (see service-binding-manager or something like that) to much higher number ranges to avoid this problem (particularly 1098 and 1099 ports).

                                    my two coppers,
                                    -D

                                    1 2 Previous Next