1 2 Previous Next 17 Replies Latest reply on Jun 28, 2012 10:25 AM by Oscar Garcia

    Problems starting JBoss for a second ou third time

    Marcos Ferreira Newbie

      Hi guys!

      I've downloaded and installed JBoss 3.2.7 and i'm having problems when trying to execute it for a second time.
      After it stops working, i have to wait about 30 min to start it again without errors, otherwise it shows that there are some ports that have been used by others process, but it not true.
      It shows the log lines below:

      2005-06-17 15:44:59,930 ERROR [org.jboss.naming.NamingService] Starting failed 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:299)
      at org.jnp.server.Main.start(Main.java:262)

      I'd appreciate If anyone could help me.

      Best regards,

      Marcos

        • 1. Re: Problems starting JBoss for a second ou third time
          Peter Johnson Master

          What operating system are you running?

          If Linux, try running "netstat -an | grep 1098" to see what process is using the port. (I used 1098 based on the error message you supplied, if other ports are also in use, alter the command line accordingly.)

          If Windows, download tcpview.exe from www.sysinternals.com, run it and determine what process(es) are using the ports.

          • 2. Re: Problems starting JBoss for a second ou third time
            Marcos Ferreira Newbie

            Hi, Peter!

            I´ve done what u said i there is no process listening any port that JBoss used to listen.
            Altough, after u replied i tried to start JBoss and it executed with success.
            But i shut it down and tried to put it up again.
            There was something wrong with ports 1098 and 4444 only, wich were linked to binds done by JBoss.
            It logged two different errors:

            2005-06-17 16:52:55,628 ERROR [org.jboss.naming.NamingService] Starting failed 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)


            and



            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)


            Since it had something wrong with this two ports, i'd like a help ou an explain about this kind of trouble, and if JBoss is ok even with this two kind of problems.


            Best regards,

            Marcos

            • 3. Re: Problems starting JBoss for a second ou third time
              Peter Johnson Master

              When you got these errors did you immediately run the utility to determine who was using the ports?

              • 4. Re: Problems starting JBoss for a second ou third time
                Marcos Ferreira Newbie

                Hi, Peter!

                I used to maintain tcpview app executing when i shutdown jboss.
                There isn't no app using this two ports even during jboss execution.

                Thanx
                Marcos

                • 5. Re: Problems starting JBoss for a second ou third time
                  Peter Johnson Master

                  Are you running a firewall? One that block ports? For example, I run Sygate at work and ZoneAlarm at home. Both are set to ask if ports can be opened. When Java asks to open a port, I give it termporary permission (this time only). If you have afirewall, did you by any chance disallow Java from opening a port at any time in the past, and make that decision permanent? If so, you will have to reconfigure your firewall to ask each time Java want to open a port.

                  If the firewall is not the problem, then I have run out of ides because you have stated that no programs have ports 1098 and 4444 open, yet JBoss says that they are already in use. (Possible virus/spyware infection?)

                  • 6. Re: Problems starting JBoss for a second ou third time
                    Marcos Ferreira Newbie

                    Hi, Peter!

                    I've only a firewall client running. This not shows me that it could be a problem. Otherwise i've trend micro antivirus client running too.

                    I'm still having this problem and didn't see any light at the end of the tunnel.
                    My coworker is having the same problem with JBoss 4.01.

                    I'm putting two list views from TcpView, showing JBoss before and after starting it.

                    Take a look:

                    before
                    svchost.exe:416 TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
                    System:8 TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
                    System:8 UDP 0.0.0.0:445 *:*
                    LSASS.EXE:236 UDP 0.0.0.0:1027 *:*
                    WINLOGON.EXE:172 UDP 0.0.0.0:1054 *:*
                    mstask.exe:884 TCP 0.0.0.0:1070 0.0.0.0:0 LISTENING
                    System:8 TCP 0.0.0.0:1089 0.0.0.0:0 LISTENING
                    System:8 TCP 0.0.0.0:1123 0.0.0.0:0 LISTENING
                    System:8 TCP 0.0.0.0:1140 0.0.0.0:0 LISTENING
                    explorer.exe:1304 UDP 0.0.0.0:1211 *:*
                    mplayer2.exe:1568 TCP 0.0.0.0:1290 0.0.0.0:0 LISTENING
                    mplayer2.exe:1568 TCP 0.0.0.0:1296 0.0.0.0:0 LISTENING
                    firefox.exe:2468 TCP 0.0.0.0:1468 0.0.0.0:0 LISTENING
                    System:8 TCP 0.0.0.0:3206 0.0.0.0:0 LISTENING
                    tmlisten.exe:920 UDP 0.0.0.0:3414 *:*
                    tmlisten.exe:920 TCP 0.0.0.0:12345 0.0.0.0:0 LISTENING
                    System:8 UDP 10.17.5.166:137 *:*
                    System:8 UDP 10.17.5.166:138 *:*
                    System:8 TCP 10.17.5.166:139 0.0.0.0:0 LISTENING
                    LSASS.EXE:236 UDP 10.17.5.166:500 *:*
                    System:8 TCP 10.17.5.166:1123 10.17.0.1:445 ESTABLISHED
                    mplayer2.exe:1568 TCP 10.17.5.166:1290 10.17.0.3:80 CLOSE_WAIT
                    mplayer2.exe:1568 TCP 10.17.5.166:1296 10.17.0.3:80 ESTABLISHED
                    System:8 TCP 10.17.5.166:1878 0.0.0.0:0 LISTENING
                    System:8 TCP 10.17.5.166:1878 7.0.0.28:139 ESTABLISHED
                    System:8 TCP 10.17.5.166:1888 7.0.0.29:80 TIME_WAIT
                    System:8 TCP 10.17.5.166:1889 7.0.0.29:80 TIME_WAIT
                    System:8 TCP 10.17.5.166:1892 7.0.0.29:80 TIME_WAIT
                    System:8 TCP 10.17.5.166:12345 7.0.0.29:4758 TIME_WAIT
                    POP3Trap.exe:1792 TCP 127.0.0.1:110 0.0.0.0:0 LISTENING
                    aengine.exe:540 TCP 127.0.0.1:1065 0.0.0.0:0 LISTENING
                    mstask.exe:884 TCP 127.0.0.1:1069 0.0.0.0:0 LISTENING
                    tmlisten.exe:920 TCP 127.0.0.1:1075 0.0.0.0:0 LISTENING
                    OfcPfwSvc.exe:840 TCP 127.0.0.1:1091 0.0.0.0:0 LISTENING
                    spoolsv.exe:444 TCP 127.0.0.1:1104 0.0.0.0:0 LISTENING
                    PccNTMon.exe:1620 TCP 127.0.0.1:1145 0.0.0.0:0 LISTENING
                    explorer.exe:1304 TCP 127.0.0.1:1210 0.0.0.0:0 LISTENING
                    mplayer2.exe:1568 TCP 127.0.0.1:1294 0.0.0.0:0 LISTENING
                    firefox.exe:2468 TCP 127.0.0.1:1466 0.0.0.0:0 LISTENING
                    firefox.exe:2468 TCP 127.0.0.1:1467 0.0.0.0:0 LISTENING
                    firefox.exe:2468 TCP 127.0.0.1:1467 127.0.0.1:1468 ESTABLISHED
                    firefox.exe:2468 TCP 127.0.0.1:1468 127.0.0.1:1467 ESTABLISHED
                    IEXPLORE.EXE:1616 TCP 127.0.0.1:1578 0.0.0.0:0 LISTENING
                    IEXPLORE.EXE:1616 UDP 127.0.0.1:1579 *:*
                    javaw.exe:1756 TCP 127.0.0.1:1666 0.0.0.0:0 LISTENING
                    Tcpview.exe:2368 TCP 127.0.0.1:1857 0.0.0.0:0 LISTENING
                    POP3Trap.exe:1792 TCP 127.0.0.1:4533 0.0.0.0:0 LISTENING


                    after
                    svchost.exe:416 TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
                    System:8 TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
                    System:8 UDP 0.0.0.0:445 *:*
                    LSASS.EXE:236 UDP 0.0.0.0:1027 *:*
                    WINLOGON.EXE:172 UDP 0.0.0.0:1054 *:*
                    mstask.exe:884 TCP 0.0.0.0:1070 0.0.0.0:0 LISTENING
                    System:8 TCP 0.0.0.0:1089 0.0.0.0:0 LISTENING
                    System:8 TCP 0.0.0.0:1123 0.0.0.0:0 LISTENING
                    System:8 TCP 0.0.0.0:1140 0.0.0.0:0 LISTENING
                    explorer.exe:1304 UDP 0.0.0.0:1211 *:*
                    mplayer2.exe:1568 TCP 0.0.0.0:1290 0.0.0.0:0 LISTENING
                    mplayer2.exe:1568 TCP 0.0.0.0:1296 0.0.0.0:0 LISTENING
                    firefox.exe:2468 TCP 0.0.0.0:1468 0.0.0.0:0 LISTENING
                    System:8 TCP 0.0.0.0:1909 0.0.0.0:0 LISTENING
                    java.exe:1348 UDP 0.0.0.0:1910 *:*
                    System:8 TCP 0.0.0.0:3206 0.0.0.0:0 LISTENING
                    tmlisten.exe:920 UDP 0.0.0.0:3414 *:*
                    java.exe:1348 TCP 0.0.0.0:4445 0.0.0.0:0 LISTENING
                    java.exe:1348 TCP 0.0.0.0:8083 0.0.0.0:0 LISTENING
                    java.exe:1348 TCP 0.0.0.0:8093 0.0.0.0:0 LISTENING
                    java.exe:1348 TCP 0.0.0.0:8787 0.0.0.0:0 LISTENING
                    tmlisten.exe:920 TCP 0.0.0.0:12345 0.0.0.0:0 LISTENING
                    System:8 UDP 10.17.5.166:137 *:*
                    System:8 UDP 10.17.5.166:138 *:*
                    System:8 TCP 10.17.5.166:139 0.0.0.0:0 LISTENING
                    LSASS.EXE:236 UDP 10.17.5.166:500 *:*
                    System:8 TCP 10.17.5.166:1123 10.17.0.1:445 ESTABLISHED
                    mplayer2.exe:1568 TCP 10.17.5.166:1290 10.17.0.3:80 CLOSE_WAIT
                    mplayer2.exe:1568 TCP 10.17.5.166:1296 10.17.0.3:80 ESTABLISHED
                    System:8 TCP 10.17.5.166:1878 0.0.0.0:0 LISTENING
                    System:8 TCP 10.17.5.166:1878 7.0.0.28:139 ESTABLISHED
                    System:8 TCP 10.17.5.166:1888 7.0.0.29:80 TIME_WAIT
                    System:8 TCP 10.17.5.166:1889 7.0.0.29:80 TIME_WAIT
                    System:8 TCP 10.17.5.166:1892 7.0.0.29:80 TIME_WAIT
                    System:8 TCP 10.17.5.166:12345 7.0.0.29:4758 TIME_WAIT
                    POP3Trap.exe:1792 TCP 127.0.0.1:110 0.0.0.0:0 LISTENING
                    System:8 TCP 127.0.0.1:445 127.0.0.1:1909 ESTABLISHED
                    aengine.exe:540 TCP 127.0.0.1:1065 0.0.0.0:0 LISTENING
                    mstask.exe:884 TCP 127.0.0.1:1069 0.0.0.0:0 LISTENING
                    tmlisten.exe:920 TCP 127.0.0.1:1075 0.0.0.0:0 LISTENING
                    OfcPfwSvc.exe:840 TCP 127.0.0.1:1091 0.0.0.0:0 LISTENING
                    spoolsv.exe:444 TCP 127.0.0.1:1104 0.0.0.0:0 LISTENING
                    PccNTMon.exe:1620 TCP 127.0.0.1:1145 0.0.0.0:0 LISTENING
                    explorer.exe:1304 TCP 127.0.0.1:1210 0.0.0.0:0 LISTENING
                    mplayer2.exe:1568 TCP 127.0.0.1:1294 0.0.0.0:0 LISTENING
                    firefox.exe:2468 TCP 127.0.0.1:1466 0.0.0.0:0 LISTENING
                    firefox.exe:2468 TCP 127.0.0.1:1467 0.0.0.0:0 LISTENING
                    firefox.exe:2468 TCP 127.0.0.1:1467 127.0.0.1:1468 ESTABLISHED
                    firefox.exe:2468 TCP 127.0.0.1:1468 127.0.0.1:1467 ESTABLISHED
                    IEXPLORE.EXE:1616 TCP 127.0.0.1:1578 0.0.0.0:0 LISTENING
                    IEXPLORE.EXE:1616 UDP 127.0.0.1:1579 *:*
                    javaw.exe:1756 TCP 127.0.0.1:1666 0.0.0.0:0 LISTENING
                    Tcpview.exe:2368 TCP 127.0.0.1:1857 0.0.0.0:0 LISTENING
                    java.exe:1348 TCP 127.0.0.1:1908 0.0.0.0:0 LISTENING
                    System:8 TCP 127.0.0.1:1909 127.0.0.1:445 ESTABLISHED
                    POP3Trap.exe:1792 TCP 127.0.0.1:4533 0.0.0.0:0 LISTENING


                    U'll see that there is no signal of 4444 and 1098 ports.

                    I'd like to tanx u for ur help.
                    I'll try to solve it and i think i'll do it.

                    Best regards,

                    Marcos

                    • 7. Re: Problems starting JBoss for a second ou third time
                      Peter Johnson Master

                      Since you and your co-worker are having the same problem I think it has something to do with the configuration of your machines; configurations probably dictated by by your IT staff (I know I have similar restrictions at work and some things that work at home just will not work on my PC at work). Perhaps you should try running on your PC at home (if you have one) to verify it does indeed work.

                      When you find out what the problem is, let me know.

                      Good luck!

                      • 8. Re: Problems starting JBoss for a second ou third time
                        Nathan Goss Newbie

                        Marcos,

                        Did you manage to work out this issue?

                        I am having EXACTLY the same problem as you described.

                        If you managed to work out a fix, I would love your help.

                        Kind regards,

                        Nathan

                        • 9. Re: Problems starting JBoss for a second ou third time
                          Marcos Ferreira Newbie

                          Sorry, Nathan!

                          But i'm still having this ugly problem.
                          I found a topic about the same problem and the only different thing is that if you unplugged the network, everything works fine and this is, unfortunatelly is true, but I think its not our case.

                          I'm still looking for a solution if i find it i'll tell u too.

                          Best regards,

                          Marcos

                          • 10. Re: Problems starting JBoss for a second ou third time
                            Laura Gonzalez Newbie

                            Hi guys
                            I'm having the same problem but in my case there is a process which is using the port 1098, but is a system process, I can't get any description of what it is and I have tried several ways: I already disconenct my network but the process doesn't release the port.
                            I'm afraid of terminate the process.
                            Any ideas??
                            Thanks in advance.
                            Laura

                            • 11. Re: Problems starting JBoss for a second ou third time
                              hasith yaggahavita Newbie

                              I had also faced the similar problem. I found that the Skype process uses the port 1098. If u r on windows xp try command "netstat -a -n -o" and get the processid which uses the port, and then use command "tasklist" to get the name of the process holding that processid.

                              <a href="hasith.net> Hasith Yaggahavita

                              • 12. Re: Problems starting JBoss for a second ou third time
                                Anurag Sharma Newbie

                                Hi Marcos,

                                I had the problem and came through your post. On the base this problem is because JBoss is trying to start a service on port that is already in user (1098). Now which process is using this port is another discussion (I couldn't find it yet except that it's owned by system).

                                Solution to the problem is that you change port number to the one that you are sure is not in use (conf/jboss-services.xml). Below is the one that I'm using now.

                                "5098"

                                -fg

                                • 13. Re: Problems starting JBoss for a second ou third time
                                  Andrei Karneyenka Newbie

                                  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>
                                  


                                  • 14. Re: Problems starting JBoss for a second ou third time
                                    Kanagavelan Newbie

                                    I had the same problem. Then I referred to other sites and understand that other applications such as OUTLOOK, Oracle etc make use of this port 1098. We can stop these services/processes using Windows Task Manager. Now start the JBoss. Hopefully there will be no problems.

                                    Alternatively, one can change the RmiPort definition of JBoss service from 1098 to some other ports. eg 10098. RmiPort is defined in the JNDI part of jboss-service.xml file inside the conf directory.

                                    With warm regards,
                                    kanags

                                    1 2 Previous Next