WebLogic Server: 10.3.5.0 - Managed stuck in STARTING

Question

Hi all. I have a managed stuck in STARTING for like 2 hours, the logs are these:
####<Sep 25, 2013 1:40:42 PM CEST> <Info> <JMS> <XXXXXXXXXXXXX> <ofi-spss-01> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <6737003733c3b0fc:-2e9de822:14154e52035:-7ffd-0000000000000002> <1380109242585> <BEA-040321> <JMSServer "JMSServer-SPSS-1" is resuming.>
####<Sep 25, 2013 1:44:56 PM CEST> <Info> <Messaging> <XXXXXXXXXXXXX> <ofi-spss-01> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <6737003733c3b0fc:-2e9de822:14154e52035:-7ffd-0000000000000002> <1380109496786> <BEA-282003> <The messaging kernel JMSServer-SPSS-1 will use up to 536,870,912 bytes of memory before paging begins>
####<Sep 25, 2013 1:44:56 PM CEST> <Info> <Messaging> <XXXXXXXXXXXXX> <ofi-spss-01> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <6737003733c3b0fc:-2e9de822:14154e52035:-7ffd-0000000000000002> <1380109496795> <BEA-282001> <The messaging kernel JMSServer-SPSS-1 is beginning recovery of its persistent state>
It's creating a log ot .TMP files under the managed tmp. There is a way to speed up or elude this "recover"? Please note that I'm quite noob with Weblogic.
Thanks!

Answer 1

Hi,
Add -Dweblogic.StdoutDebugEnabled flag while starting the managed server and then post the verbose error message in your next post
For setting the flag follow the below steps
If your using Linux box and not using node manager to start the managed server,add the below line startManagedWebLogic.sh file
JAVA_OPTIONS="-Dweblogic.StdoutDebugEnabled=true ${JAVA_OPTIONS}"
echo "JAVA_OPTIONS=${JAVA_OPTIONS}"
If your using Windows box and not using node manager to start the managed server,add the below line startManagedWebLogic.cmd file
set JAVA_OPTIONS=-Dweblogic.StdoutDebugEnabled=true %JAVA_OPTIONS%
echo JAVA_OPTIONS=%JAVA_OPTIONS%
If you are starting the Managed server through the node manager then use these flags From Admin console : servers >>>. MS1 >>>> server start >>>> Arguments :-Dweblogic.StdoutDebugEnabled=true
Regards,
Fabian