Wednesday, October 17, 2012

WebLogic server starting in ADMIN mode, some doubts

ms1 was restarted and went to ADMIN mode.

I can see several error in the logs, first it can’t create a Connection Pool:

Caused By: weblogic.common.ResourceException: weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: Listener refused the connection with the following error:
ORA-12514, TNS:listener does not currently know of service requested in connect descriptor

then it decides to go in Admin Mode:

#### <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <0000jdahmbme4uk5oz4eyy1gv9za00000h> <1350343196766> brought up in administration state due to failed deployments

but strangely there is still some deployment activity going on:

#### <pippo107> <[ACTIVE] ExecuteThread: '14' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <4cea82998b9a2c15:5c6e1c09:13a66b4d85c: -8000-0000000000000112="-8000-0000000000000112"> <1350343231055> <There was an error while making the initial connection to the JMS resource named ALSB_JMS_SessionPool_1750602009 from within an EJB or a servlet. The server will attempt the connection again later. The error was javax.jms.JMSException: [JMSPool:169803]JNDI lookup of the JMS connection factory failed: weblogic.jndi.internal.AdminModeAccessException: Unable to resolve 'CommonOsbCF'. Resolved ''; remaining name ''>

but, VERY STRANGELY, the server still seems to go in RUNNING mode (even if it doesn’t say “server state changed to RUNNING”):

#### <pippo107> <[ACTIVE] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <4cea82998b9a2c15:5c6e1c09:13a66b4d85c: -8000-0000000000000156="-8000-0000000000000156"> <1350343252905>

and then it goes to ADMIN mode:

#### <pippo107>
<> <> <4cea82998b9a2c15:5c6e1c09:13a66b4d85c: -8000-0000000000002128="-8000-0000000000002128"> <1350343264564>

My main worry is that in this time interval some messages are actually processed, even if most components are not actually set up.


No comments: