3 Replies Latest reply: Feb 14, 2011 2:35 PM by PHCharbonneau RSS

    Unable to start Weblogic Admin server

    hrushi
      Hi,
      I am not able to start weblogic server by issuing the command:
      cns006a031 muidev $cd /opt/software/wls_domains/muidev/bin
      cns006a031 muidev $./startWebLogic.sh


      Logs doesnot show any error either: Copy of the log file is below:

      /opt/software/wls_domains/muidev/lib/log4j-1.2.8.jar:/opt/software/wls_domains/muidev/lib/mbeantypes/XL10SecurityProviders.jar:/opt/software/wls_domains/muidev/lib/nexaweb-common.jar>
      <14-Feb-2011 13:33:43 o'clock GMT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 11.0-b15 from Sun Microsystems Inc.>
      <14-Feb-2011 13:33:45 o'clock GMT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.2.0 Tue Oct 20 12:16:15 PDT 2009 1267925 >
      <14-Feb-2011 13:34:11 o'clock GMT> <Info> <Management> <BEA-141227> <Making a backup copy of the configuration at /opt/software/wls_domains/muidev/config-original.jar.>
      <14-Feb-2011 13:34:12 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
      <14-Feb-2011 13:34:12 o'clock GMT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
      <14-Feb-2011 14:03:31 o'clock GMT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to the end of the classpath:
      /opt/software/wls_domains/muidev/lib/log4j-1.2.8.jar:/opt/software/wls_domains/muidev/lib/mbeantypes/XL10SecurityProviders.jar:/opt/software/wls_domains/muidev/lib/nexaweb-common.jar>
      <14-Feb-2011 14:03:34 o'clock GMT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 11.0-b15 from Sun Microsystems Inc.>
      <14-Feb-2011 14:03:37 o'clock GMT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.2.0 Tue Oct 20 12:16:15 PDT 2009 1267925 >
      <14-Feb-2011 14:04:02 o'clock GMT> <Info> <Management> <BEA-141227> <Making a backup copy of the configuration at /opt/software/wls_domains/muidev/config-original.jar.>
      <14-Feb-2011 14:04:03 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
      <14-Feb-2011 14:04:03 o'clock GMT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>


      I have waited for half-an-hour after this comes up... but the server change doesnt change to RUNNING and am not able to login to console which is obvious!


      Any pointers on this please ???
        • 1. Re: Unable to start Weblogic Admin server
          PHCharbonneau
          Hi hrushi,

          Try to logon to your server console, get the PID of the hanging Admin java process and generate a JVM Therad Dump. The Thread Dump will actually show you where the Admin server start-up Thread is hanging.

          You can then provide an update this post with the Thread Stack Trace of the hanging start-up Thread.

          Regards,
          P-H
          http://javaeesupportpatterns.blogspot.com/
          • 2. Re: Unable to start Weblogic Admin server
            hrushi
            Hi PH,
            Thank you for your reply.

            With the process being hanged as shown in the logs posted above, I am not able to login to weblogic admin console. I am able to open the login page of console, but after submitting credentials, it takes lot of time and finally ends up with "Internet Explorer cannot load the page".

            Please let me know if there is any other way of finding the PID thats hanging?
            Not sure if you are talking about the process of the admin server in solaris which can be found with ps command. If yes I can get PID, but how to generate thread JVM Thread Dump ?
            • 3. Re: Unable to start Weblogic Admin server
              PHCharbonneau
              Hi hrushi,

              i'm not refering to the Weblogic console but your physical server console. You already did most of the tasks.

              Please do the steps below:

              1) Logon to your server Solaris console
              2) Get the PID of your Admin server Java process ex: ps -ef | grep java
              3) Execute the following command: kill -3 <pid>
              4) This will generate a Thread Dump within your Admin server startup log (normally nohup.out)
              5) Extract the Thread Dump and look at the Thread Stack Trace of the Weblogic start-up Thread
              6) The thread name you are looking or is: "Main Thread"
              7) Update this post with Stack Trace of the "Main Thread"

              Regards,
              P-H