2 Replies Latest reply on Nov 18, 2003 11:43 AM by Darran Lofthouse

    Failed to start JBoss3.2.2

    nortex Newbie

      I have downloaded JBoss 3.2.2 and run it on Windows XP Professional. I got following errors right after JBoss started:

      JBoss Bootstrap Environment
      JBOSS_HOME: C:\JBoss1\bin\\..
      JAVA: c:\j2sdk1.4.1_01\bin\java
      JAVA_OPTS: -Dprogram.name=run.bat
      CLASSPATH: ;c:\j2sdk1.4.1_01\lib\tools.jar;C:\JBoss1\bin\\run.jar
      09:15:42,589 INFO [Server] Starting JBoss (MX MicroKernel)...
      09:15:42,589 INFO [Server] Release ID: JBoss [WonderLand] 3.2.2 (build: CVSTag=JBoss_3_2_2 date=200310182216)
      09:15:42,599 INFO [Server] Home Dir: C:\JBoss1
      09:15:42,599 INFO [Server] Home URL: file:/C:/JBoss1/
      09:15:42,599 INFO [Server] Library URL: file:/C:/JBoss1/lib/
      09:15:42,599 INFO [Server] Patch URL: null
      09:15:42,599 INFO [Server] Server Name: default
      09:15:42,599 INFO [Server] Server Home Dir: C:\JBoss1\server\default
      09:15:42,599 INFO [Server] Server Home URL: file:/C:/JBoss1/server/default/
      09:15:42,599 INFO [Server] Server Data Dir: C:\JBoss1\server\default\data
      09:15:42,599 INFO [Server] Server Temp Dir: C:\JBoss1\server\default\tmp
      09:15:42,609 INFO [Server] Server Config URL: file:/C:/JBoss1/server/default/conf/
      09:15:42,609 INFO [Server] Server Library URL: file:/C:/JBoss1/server/default/lib/
      09:15:42,609 INFO [Server] Root Deployemnt Filename: jboss-service.xml
      09:15:42,619 INFO [Server] Starting General Purpose Architecture (GPA)...
      09:15:43,130 INFO [ServerInfo] Java version: 1.4.1_01,Sun Microsystems Inc.
      09:15:43,130 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.4.1_01-b01,Sun Microsystems Inc.
      09:15:43,130 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
      09:15:43,210 INFO [ServiceController] Controller MBean online
      09:15:43,671 INFO [MainDeployer] Started jboss.system:service=MainDeployer
      09:15:43,801 INFO [MainDeployer] Adding deployer: org.jboss.deployment.JARDeployer@8bdcd2
      09:15:43,801 INFO [JARDeployer] Started jboss.system:service=JARDeployer
      09:15:43,851 INFO [MainDeployer] Adding deployer: org.jboss.deployment.SARDeployer@12a0f6c
      09:15:43,861 INFO [SARDeployer] Started jboss.system:service=ServiceDeployer
      09:15:43,861 INFO [Server] Core system initialized
      09:15:43,881 INFO [MainDeployer] Starting deployment of package: file:/C:/JBoss1/server/default/conf/jboss-service.xml
      09:15:48,618 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
      09:15:49,028 INFO [LocalJBossServerDomain] Started jboss.management.local:j2eeType=J2EEDomain,name=Manager
      09:15:49,028 INFO [Log4jService] Started jboss.system:type=Log4jService,service=Logging
      09:15:49,028 INFO [AbstractDeploymentScanner$ScannerThread] Running
      09:15:49,058 INFO [WebService] Started WebServer with address:
      09:15:49,058 INFO [WebService] Using RMI server codebase:
      09:15:49,058 INFO [WebService] Started jboss:service=WebService
      09:15:49,068 INFO [NamingService] Starting jnp server
      09:15:49,179 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)
      ... ...

      then there were huge amount of error messages.
      Could anyone tell what's going on?


        • 1. Re: Failed to start JBoss3.2.2
          cluck Newbie

          I've just stumbled over this problem too. Normally this happens when you are trying to run more than one instance of the server, or if you are running something like Tomcat seperately. However, there are other applications that may be running on your machine that grab ports - in my case a Firewall client. You can try reconfiguring JBoss's services to use other ports - which might work, so long as you happen to know *for certain* which ports are currently free - or you can shut down any processes which might be using this port.

          • 2. Re: Failed to start JBoss3.2.2
            Darran Lofthouse Master

            Try using netstat -an to identify ports that are already being used before starting JBoss.