4 Replies Latest reply on Nov 7, 2008 11:44 AM by Peter Johnson

    JBoss Server hangs before "[TransactionManagerService]" star

    Peter Steiner Newbie

      When I try to start JBoss AS (EAP) with run.bat then everything seems to be fine at first until it should start "TransactionManagerService". The boot process stops and hangs forever.
      The boot sequence look until this moment:

      ...
      12:36:46,946 INFO [Server] Root Deployment Filename: jboss-service.xml
      12:36:47,212 INFO [ServerInfo] Java version: 1.6.0_07,Sun Microsystems Inc.
      12:36:47,212 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 10.0-b23,Sun Microsystems Inc.
      12:36:47,212 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
      12:36:47,602 INFO [Server] Core system initialized
      12:36:50,196 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/
      12:36:50,212 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
      <now waiting forever>


      When I start (after killing the first EAP JBoss server start process) another, separate JBoss AS installation v4.2.3 on the same (WinXP) system everything is fine.

      So it must be something with the configuration of the first JBoss AS (EAP) server. Especially with the TransactionManagerService.

      What can it be?

      Peter

        • 1. Re: JBoss Server hangs before
          Peter Johnson Master

          Which configuration are you running (that is, what is the run command line you are using)? What changes have you made to the configuration? Is this the first time you brought up EAP?

          Is the java process showing any CPU usage? In other words, does it look like it is looping or does it look like it is waiting on something?

          What are the last dozen or so lines in the server.log?

          • 2. Re: JBoss Server hangs before
            Peter Steiner Newbie

             

            "PeterJ" wrote:
            Which configuration are you running (that is, what is the run command line you are using)? What changes have you made to the configuration? Is this the first time you brought up EAP?

            Is the java process showing any CPU usage? In other words, does it look like it is looping or does it look like it is waiting on something?

            What are the last dozen or so lines in the server.log?


            "production" configuration

            simply "run.bat" with no parameter

            No configuration changes were made

            It is the first time of starting EAP through run.bat. However I started successfully the server already dozend of times through Eclipse.

            Approx 20 second after the last line output CPU usage is observable. Then it turns to zero.

            Last lines in server.log see bottom.

            However some hundreds line above the last server.log line the following exception can be seen:

            2008-11-07 10:03:22,950 DEBUG [org.jboss.system.ServiceController] starting service jboss.messaging:service=PersistenceManager
            2008-11-07 10:03:22,950 DEBUG [org.jboss.messaging.core.jmx.JDBCPersistenceManagerService] Starting jboss.messaging:service=PersistenceManager
            2008-11-07 10:03:22,982 DEBUG [org.jboss.messaging.core.impl.JDBCSupport] Failed to execute: CREATE TABLE JBM_DUAL (DUMMY INTEGER, PRIMARY KEY(DUMMY))
            java.sql.SQLException: Table already exists: JBM_DUAL in statement [CREATE TABLE JBM_DUAL]
            at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
            at org.hsqldb.jdbc.jdbcStatement.fetchResult(Unknown Source)
            at org.hsqldb.jdbc.jdbcStatement.executeUpdate(Unknown Source)
            at org.jboss.resource.adapter.jdbc.WrappedStatement.executeUpdate(WrappedStatement.java:237)
            at org.jboss.messaging.core.impl.JDBCSupport.createSchema(JDBCSupport.java:301)
            at org.jboss.messaging.core.impl.JDBCSupport.start(JDBCSupport.java:167)
            .....
            ......
            approx 1000 lines
            ....
            ....
            2008-11-07 10:03:31,825 DEBUG [org.jboss.deployment.SARDeployer] Deploying SAR, start step: url file:/C:/jbdev1.1.0/jboss-eap/jboss-as/server/production/farm/cluster-examples-service.xml
            2008-11-07 10:03:31,825 DEBUG [org.jboss.deployment.MainDeployer] End deployment start on package: cluster-examples-service.xml
            2008-11-07 10:03:31,825 DEBUG [org.jboss.deployment.MainDeployer] Deployed package: file:/C:/jbdev1.1.0/jboss-eap/jboss-as/server/production/farm/cluster-examples-service.xml
            2008-11-07 10:03:31,825 DEBUG [org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread] Notified that enabled: true
            2008-11-07 10:03:31,825 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss:service=FarmMember,partition=DefaultPartition dependent components: []
            2008-11-07 10:03:31,841 DEBUG [org.jboss.deployment.MainDeployer] End deployment start on package: farm-service.xml
            2008-11-07 10:03:31,841 DEBUG [org.jboss.deployment.MainDeployer] End deployment start on package: deploy.last
            2008-11-07 10:03:31,841 DEBUG [org.jboss.deployment.MainDeployer] Deployed package: file:/C:/jbdev1.1.0/jboss-eap/jboss-as/server/production/deploy/deploy.last/
            2008-11-07 10:03:31,841 DEBUG [org.jboss.deployment.scanner.URLDeploymentScanner] Watch URL for: file:/C:/jbdev1.1.0/jboss-eap/jboss-as/server/production/deploy/deploy.last/ -> file:/C:/jbdev1.1.0/jboss-eap/jboss-as/server/production/deploy/deploy.last/
            2008-11-07 10:03:31,841 DEBUG [org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread] Notified that enabled: true
            2008-11-07 10:03:31,841 DEBUG [org.jboss.deployment.scanner.URLDeploymentScanner] Started jboss.deployment:type=DeploymentScanner,flavor=URL
            2008-11-07 10:03:31,841 DEBUG [org.jboss.system.ServiceController] Starting dependent components for: jboss.deployment:type=DeploymentScanner,flavor=URL dependent components: []
            2008-11-07 10:03:31,872 DEBUG [org.jboss.deployment.MainDeployer] End deployment start on package: jboss-service.xml
            2008-11-07 10:03:31,872 DEBUG [org.jboss.deployment.MainDeployer] Deployed package: file:/C:/jbdev1.1.0/jboss-eap/jboss-as/server/production/conf/jboss-service.xml
            2008-11-07 10:03:31,935 INFO [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.3.0.GA_CP01 (build: SVNTag=JBPAPP_4_3_0_GA_CP01 date=200804211657)] Started in 33s:860ms




            • 3. Re: JBoss Server hangs before
              Peter Steiner Newbie

               

              "pxstein "production" configuration [/quote wrote:


              As I just saw Eclipse is starting EAP with "default" configuration.

              When I start EAP with

              run.bat -c default

              then everything is fine.

              However the problem persists: Why is it NOT possible to start the "production" configuration?


              • 4. Re: JBoss Server hangs before
                Peter Johnson Master

                According to the log output, the app server started without problems. See this line:

                2008-11-07 10:03:31,935 INFO [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.3.0.GA_CP01 (build: SVNTag=JBPAPP_4_3_0_GA_CP01 date=200804211657)] Started in 33s:860ms

                My guess would be that the CONSOLE log is turned off, in which case only the bootstrap logging goes to the console. Looking at the jboss-log4j.xml file in the production configuration, I see that the console log is indeed turned off. Therefore, this is not a problem.