2 Replies Latest reply on Jun 23, 2005 4:40 PM by tatkinson

    Error starting JBoss server

    nkj

      When the JBoss server is started locally, I get the error message that

      07:28:17,468 ERROR [NamingService] Starting failed jboss:service=Naming
      java.rmi.server.ExportException: Listen failed on port: 1098; nested exception is:
      java.net.SocketException: Invalid argument: listen failed
      at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:245)


      I have attached more log information below

      ===============================================================================
      .
      JBoss Bootstrap Environment
      .
      JBOSS_HOME: C:\JBoss\bin\\..
      .
      JAVA: C:\Java\jdk1.5.0_03\bin\java
      .
      JAVA_OPTS: -Dprogram.name=run.bat
      .
      CLASSPATH: C:\Java\jdk1.5.0_03\lib\tools.jar;C:\JBoss\bin\\run.jar
      .
      ===============================================================================
      .
      07:28:14,484 INFO [Server] Starting JBoss (MX MicroKernel)...
      07:28:14,484 INFO [Server] Release ID: JBoss [WonderLand] 3.2.7 (build: CVSTag=JBoss_3_2_7 date=200501280217)
      07:28:14,484 INFO [Server] Home Dir: C:\JBoss
      07:28:14,484 INFO [Server] Home URL: file:/C:/JBoss/
      07:28:14,484 INFO [Server] Library URL: file:/C:/JBoss/lib/
      07:28:14,484 INFO [Server] Patch URL: null
      07:28:14,484 INFO [Server] Server Name: default
      07:28:14,484 INFO [Server] Server Home Dir: C:\JBoss\server\default
      07:28:14,484 INFO [Server] Server Home URL: file:/C:/JBoss/server/default/
      07:28:14,484 INFO [Server] Server Data Dir: C:\JBoss\server\default\data
      07:28:14,484 INFO [Server] Server Temp Dir: C:\JBoss\server\default\tmp
      07:28:14,500 INFO [Server] Server Config URL: file:/C:/JBoss/server/default/conf/
      07:28:14,500 INFO [Server] Server Library URL: file:/C:/JBoss/server/default/lib/
      07:28:14,500 INFO [Server] Root Deployment Filename: jboss-service.xml
      07:28:14,500 INFO [Server] Starting General Purpose Architecture (GPA)...
      07:28:14,734 INFO [ServerInfo] Java version: 1.5.0_03,Sun Microsystems Inc.
      07:28:14,734 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_03-b07,Sun Microsystems Inc.
      07:28:14,734 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
      07:28:15,281 INFO [Server] Core system initialized
      07:28:17,156 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
      07:28:17,250 INFO [WebService] Using RMI server codebase: http://DDDW8W61:8083/
      07:28:17,468 ERROR [NamingService] Starting failed jboss:service=Naming
      java.rmi.server.ExportException: Listen failed on port: 1098; nested exception is:
      java.net.SocketException: Invalid argument: listen failed
      at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:245)
      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:180)
      at java.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.java:293)
      at java.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.java:256)
      at org.jnp.server.Main.initJnpInvoker(Main.java:299)
      at org.jnp.server.Main.start(Main.java:262)

        • 1. Re: Error starting JBoss server
          tatkinson

          I had this same (or at least very similar) problem the other day. After restarting Windows, JBoss worked fine again. Still not sure what the problem was....

          Trey

          • 2. Re: Error starting JBoss server
            tatkinson

            Nevermind that previous message. The problem has resurfaced. From using netstat -an | grep 1098, I have found that the port is being used by the Windows domain controller. After speaking with our NT Admins, I have been advised to only use ports over 5000 to make sure there are no Windows port conflicts.

            Trey