6 Replies Latest reply on Jan 29, 2003 4:48 PM by raja05

    Getting 1000 exceptions on startup

    odrec

      Hi, and thanks already for coming this far... you'd be like the first one to read my posts! I've posted like 10 things and yet no answer... but anyway..

      I execute run.jar, with Java_Home set, on WindowsXP, and I get a lot of exceptions, please let me know if you can deduce anything from the following exceptions..

      Thanx:

      (The log is attached if you need additional info...)

      13:46:29,541 ERROR [JRMPInvoker] Failed
      java.rmi.server.ExportException: Port already in use: 4444; nested exception is:
      java.net.BindException: Address in use: JVM_Bind
      java.net.BindException: Address in use: JVM_Bind
      at java.net.PlainSocketImpl.socketBind(Native Method)
      at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:405)
      at java.net.ServerSocket.(ServerSocket.java:170)
      at java.net.ServerSocket.(ServerSocket.java:82)
      at sun.rmi.transport.proxy.RMIDirectSocketFactory.createServerSocket(RMIDirectSocketFactory.java:30)
      at sun.rmi.transport.proxy.RMIMasterSocketFactory.createServerSocket(RMIMasterSocketFactory.java:312)


      ----


      13:46:38,484 WARN [jbossweb] WARNING: Failed to start: SocketListener@0.0.0.0:8080
      13:46:38,534 WARN [jbossweb] WARNING: Failed to start: AJP13Listener@0.0.0.0:8009
      13:46:38,564 ERROR [JettyService] multiple exceptions...
      13:46:38,605 ERROR [JettyService] exception
      java.net.BindException: Address in use: JVM_Bind
      at java.net.PlainSocketImpl.socketBind(Native Method)
      at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:405)
      at java.net.ServerSocket.(ServerSocket.java:170)
      at org.mortbay.util.ThreadedServer.newServerSocket(ThreadedServer.java:318)


      -----

      13:52:52,833 WARN [ServiceController] Problem starting service jboss.j2ee:jndiName=ejb/mgmt/MEJB,service=EJB
      java.rmi.ServerException: Could not bind home; nested exception is:
      javax.naming.CommunicationException [Root exception is java.rmi.NoSuchObjectException: object not exported]
      javax.naming.CommunicationException. Root exception is
      java.rmi.NoSuchObjectException: object not exported
      at sun.rmi.transport.ObjectTable.getStub(ObjectTable.java:102)
      at java.rmi.server.RemoteObject.toStub(RemoteObject.java:76)
      at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.writeExternal(JRMPInvokerProxy.java:183)


      -----

      13:53:20,384 WARN [ServiceController] Problem starting service jboss.j2ee:jndiName=ejb/jmx/ejb/Adaptor,service=EJB
      java.rmi.ServerException: Could not bind home; nested exception is:
      javax.naming.CommunicationException [Root exception is java.rmi.NoSuchObjectException: object not exported]
      javax.naming.CommunicationException. Root exception is
      java.rmi.NoSuchObjectException: object not exported
      at sun.rmi.transport.ObjectTable.getStub(ObjectTable.java:102)
      at java.rmi.server.RemoteObject.toStub(RemoteObject.java:76)
      at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.writeExternal(JRMPInvokerProxy.java:183)
      at java.io.ObjectOutputStream.outputObject(ObjectOutputStream.java:1172)

        • 1. Re: Getting 1000 exceptions on startup
          odrec

          Here's the log.. sorry

          • 2. Re: Getting 1000 exceptions on startup
            raja05

            java.rmi.server.ExportException: Port already in use: 4444;

            Check if ur machine runs any other service that uses 4444 port. Thats the cause of ur error. Many other Services may be dependent on this and all of them fail as this cannot be resolved. Run netstat or something similar to see if that port is in use.

            -Raj

            • 3. Re: Getting 1000 exceptions on startup
              odrec

              THANX!!! Tht'll be the first reply I get :D

              OK, so I now get only the following exception:

              14:47:51,249 ERROR [JettyService] exception
              java.net.BindException: Address in use: JVM_Bind
              at java.net.PlainSocketImpl.socketBind(Native Method)
              at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:405)
              at java.net.ServerSocket.(ServerSocket.java:170)
              at org.mortbay.util.ThreadedServer.newServerSocket(ThreadedServer.java:318)
              at org.mortbay.util.ThreadedServer.start(ThreadedServer.java:388)
              at org.mortbay.http.SocketListener.start(SocketListener.java:156)
              at org.mortbay.http.HttpServer.start(HttpServer.java:685)
              at org.jboss.jetty.JettyService.startService(JettyService.java:176)
              at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:165)
              at java.lang.reflect.Method.invoke(Native Method)
              at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)

              ....


              So what port is this using? I can't check if the port is busy since I don't know what port to check...

              THANX

              • 4. Re: Getting 1000 exceptions on startup
                raja05

                Its probably 8080
                I cant see it in the jboss-service.xml , i have to check that. But i could get to 8080 to view the console. so its mostly running on 8080

                • 5. Re: Getting 1000 exceptions on startup
                  odrec

                  8080 is clear... don't know what's going on, I'm sure that 8080 is not being used... any other hints?

                  • 6. Re: Getting 1000 exceptions on startup
                    raja05

                    Look for
                    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
                    <!-- Add and configure a HTTP listener to port 8080 -->
                    <!-- The default port can be changed using: java -Djetty.port=80 -->
                    <!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->




                    5
                    100
                    30000
                    5000




                    in your jboss-service.xml. Dfaults to 8080