9 Replies Latest reply on Jul 27, 2010 3:19 AM by rsprasad

    JBoss Server Startup is Stuck !!

    saswatamandal

      Dear Experts,

       

             My server instance startup is stuck :-

       

       

      ===============================================================================

        JBoss Bootstrap Environment

        JBOSS_HOME: C:\jboss-4.2.0.GA

        JAVA: C:\Program Files\Java\jdk1.5.0_22\\bin\java

        JAVA_OPTS:  -Dprogram.name=runnode2.bat -server -Xms1472m -Xmx1472m -Dsun.rmi.
      dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000

        CLASSPATH: C:\Program Files\Java\jdk1.5.0_22\\lib\tools.jar;C:\jboss-4.2.0.GA\
      bin\run.jar

      ===============================================================================

      08:22:22,715 INFO  [Server] Starting JBoss (MX MicroKernel)...
      08:22:22,715 INFO  [Server] Release ID: JBoss [Trinity] 4.2.0.GA (build: SVNTag=
      JBoss_4_2_0_GA date=200705111440)
      08:22:22,715 INFO  [Server] Home Dir: C:\jboss-4.2.0.GA
      08:22:22,715 INFO  [Server] Home URL: file:/C:/jboss-4.2.0.GA/
      08:22:22,731 INFO  [Server] Patch URL: null
      08:22:22,731 INFO  [Server] Server Name: node2
      08:22:22,731 INFO  [Server] Server Home Dir: C:\jboss-4.2.0.GA\server\node2
      08:22:22,731 INFO  [Server] Server Home URL: file:/C:/jboss-4.2.0.GA/server/node
      2/
      08:22:22,731 INFO  [Server] Server Log Dir: C:\jboss-4.2.0.GA\server\node2\log
      08:22:22,731 INFO  [Server] Server Temp Dir: C:\jboss-4.2.0.GA\server\node2\tmp
      08:22:22,731 INFO  [Server] Root Deployment Filename: jboss-service.xml
      08:22:22,981 INFO  [ServerInfo] Java version: 1.5.0_22,Sun Microsystems Inc.
      08:22:22,981 INFO  [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_22-b03
      ,Sun Microsystems Inc.
      08:22:22,981 INFO  [ServerInfo] OS-System: Windows 2003 5.2,x86
      08:22:23,512 INFO  [Server] Core system initialized
      08:22:25,621 INFO  [WebService] Using RMI server codebase: http://123.186.166.31:
      8891/
      08:22:25,621 INFO  [Log4jService$URLWatchTimerTask] Configuring from URL: resour
      ce:jboss-log4j.xml

       

       

      NOTHING HAPPENS AFTER THIS AND ITS STUCK !!!!!

       

      Please help me to solve this issue.

       

      Thanks & Regards

      Saswata Mandal.

        • 1. Re: JBoss Server Startup is Stuck !!
          rsprasad

          Just check your JAVA_HOME environment variable.

          From the server log , third line,

          JAVA: C:\Program Files\Java\jdk1.5.0_22\\bin\java

          there are two '\\' backslashes.

           

          It is supposed to be or could be:

          JAVA: C:\Program Files\Java\jdk1.5.0_22\bin\java

          • 2. Re: JBoss Server Startup is Stuck !!
            saswatamandal

            But my other nodes are running fine , with the same config !!

             

             

            Thanks & Regards

            saswata mandal.

            • 3. Re: JBoss Server Startup is Stuck !!
              peterj

              What are the logging settings in server/node2/jboss-log4j.xml? It looks to me like the CONSOLE logger is not turned on. Check the server/node2/log/server.log and see if the "started in xxx seconds" message is in there. In other words, I doubt that JBoss AS is stuck.

              • 4. Re: JBoss Server Startup is Stuck !!
                saswatamandal

                The boot.log :- is stuck at that point .

                 

                The server.log :-

                 

                2010-07-09 15:24:36,412 INFO  [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.2.0.GA (build: SVNTag=JBoss_4_2_0_GA date=200705111440)] Started in 1m:4s:643ms

                 

                The Jboss-Log4j.xml :- attached with post.

                 

                 

                I think the server instance has started at background !!

                • 5. Re: JBoss Server Startup is Stuck !!
                  peterj

                  The boot log is not stuck - it only goes that far. The console log that you posted and the boot.log file are output by the bootstrap process. Then when the main app server runs, it writes to the server.log. According the the log4j.xml file, the CONSOLE log was turned off. And the app server is not running in the background - if you CTRL-C the app server will react to that and shut down properly.

                  • 6. Re: JBoss Server Startup is Stuck !!
                    peterj

                    I guess what I really meant by the last senetnce is that just because there is no console output does not mean that the app server is "running in the background". Nor does it mean that the app server is "hung". The app server is still running, it is just not logging anything to the console. That is not a bad thing.

                    1 of 1 people found this helpful
                    • 7. Re: JBoss Server Startup is Stuck !!
                      saswatamandal

                      Hi Peter,

                       

                           As you mentioned ,the console log is turned off in the log4j.xml that I have posted in the previous post.

                       

                      How can I turn it on , so that the " Started in 1m23s23ms" is displayed in the console.

                       

                       

                      Thanks & REgards

                      saswata mandal.

                      • 8. Re: JBoss Server Startup is Stuck !!
                        peterj

                        Go to the ASYNC appender and uncomment the CONSOLE appender-ref.

                         

                        P.S. I am not sure if there are any issues with using the AsyncAppender with the ConsoleAppender, and unfortunately I don't have my Log4J book handy to consult regarding that.

                        • 9. Re: JBoss Server Startup is Stuck !!
                          rsprasad

                          Try adding :

                           

                          <root>
                               <priority value="ERROR"/>
                               <appender-ref ref="CONSOLE"/>
                               <appender-ref ref="FILE"/>
                          </root>

                          and uncommenting appender definition for CONSOLE.