This discussion is archived
5 Replies Latest reply: May 20, 2013 6:03 AM by 978925 RSS

Weblogic managed server goes to ADMIN state

657004 Newbie
Currently Being Moderated
Hi,

I've got a domain of Weblogic 10.0 MP1 with a cluster and I found that from time to time the managed servers from the cluster goes to admin state any interaction. Just by themselves. A server log just contains a message that server state changed to suspending and so on. Here goes the fragment:

####<Jan 9, 2009 3:30:58 PM CET> <Notice> <WebLogicServer> <mvno-test-ali-1> <diameter1> <Main Thread> <<WLS Kernel>> <> <> <1231511458618> <BEA-000365> <Server state changed to ADMIN>
####<Jan 9, 2009 3:30:58 PM CET> <Info> <WorkManager> <mvno-test-ali-1> <diameter1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1231511458619> <BEA-002903> <Creating WorkManager from "weblogic.wsee.mdb.DispatchPolicy" WorkManagerMBean for application "bea_wls9_async_response">
####<Jan 9, 2009 3:30:58 PM CET> <Notice> <WebLogicServer> <mvno-test-ali-1> <diameter1> <Main Thread> <<WLS Kernel>> <> <> <1231511458619> <BEA-000365> <Server state changed to RESUMING>
####<Jan 9, 2009 3:30:59 PM CET> <Info> <Deployer> <mvno-test-ali-1> <diameter1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1231511459253> <BEA-149059> <Module DiameterAdapterEjb-0.1.3.0-SNAPSHOT.jar of application GG Enterprise Application with only DIAMETER modules is transitioning from STATE_ADMIN to STATE_ACTIVE on server diameter1.>
####<Jan 9, 2009 3:30:59 PM CET> <Info> <Deployer> <mvno-test-ali-1> <diameter1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1231511459253> <BEA-149060> <Module DiameterAdapterEjb-0.1.3.0-SNAPSHOT.jar of application GG Enterprise Application with only DIAMETER modules successfully transitioned from STATE_ADMIN to STATE_ACTIVE on server diameter1.>
####<Jan 9, 2009 3:30:59 PM CET> <Info> <Server> <mvno-test-ali-1> <diameter1> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1231511459714> <BEA-002610> <Dynamic Listener Service initialized.>
####<Jan 9, 2009 3:30:59 PM CET> <Notice> <Server> <mvno-test-ali-1> <diameter1> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1231511459784> <BEA-002613> <Channel "Default" is now listening on 10.1.67.63:7851 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
####<Jan 9, 2009 3:30:59 PM CET> <Notice> <WebLogicServer> <mvno-test-ali-1> <diameter1> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1231511459790> <BEA-000332> <Started WebLogic Managed Server "diameter1" for domain "gg" running in Development Mode>
####<Jan 9, 2009 3:30:59 PM CET> <Info> <Server> <mvno-test-ali-1> <diameter1> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1231511459817> <BEA-002635> <The server "AdminServer"connected to this server.>
####<Jan 9, 2009 3:30:59 PM CET> <Notice> <Log Management> <mvno-test-ali-1> <diameter1> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1231511459832> <BEA-170027> <The server initialized the domain log broadcaster successfully. Log messages will now be broadcasted to the domain log.>
####<Jan 9, 2009 3:31:00 PM CET> <Info> <J2EE> <mvno-test-ali-1> <diameter1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1231511460291> <BEA-160151> <Registered library Extension-Name: bea_wls_async_response (JAR).>
####<Jan 9, 2009 3:31:00 PM CET> <Info> <WorkManager> <mvno-test-ali-1> <diameter1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1231511460293> <BEA-002903> <Creating WorkManagerfrom "weblogic.wsee.mdb.DispatchPolicy" WorkManagerMBean for application "bea_wls_diagnostics">
####<Jan 9, 2009 3:31:00 PM CET> <Info> <Server> <mvno-test-ali-1> <diameter1> <DynamicListenThread[Default]> <<WLS Kernel>> <> <> <1231511460305> <BEA-002605> <Adding address: 10.1.67.63 to licensed client list>
####<Jan 9, 2009 3:31:00 PM CET> <Info> <WorkManager> <mvno-test-ali-1> <diameter1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1231511460378> <BEA-002903> <Creating WorkManagerfrom "weblogic.wsee.mdb.DispatchPolicy" WorkManagerMBean for application "uddi">
####<Jan 9, 2009 3:31:00 PM CET> <Info> <JMX> <mvno-test-ali-1> <diameter1> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1231511460415> <BEA-149511> <Established JMX Connectivity with the Adminstration Server AdminServer at service:jmx:t3://10.1.67.63:7801/jndi/weblogic.management.mbeanservers.domainruntime.>
####<Jan 9, 2009 3:31:00 PM CET> <Info> <WorkManager> <mvno-test-ali-1> <diameter1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1231511460520> <BEA-002903> <Creating WorkManagerfrom "weblogic.wsee.mdb.DispatchPolicy" WorkManagerMBean for application "uddiexplorer">
####<Jan 9, 2009 3:31:00 PM CET> <Notice> <Cluster> <mvno-test-ali-1> <diameter1> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1231511460707> <BEA-000102> <Joining cluster diametertest on 239.192.0.0:7882>
####<Jan 9, 2009 3:31:00 PM CET> <Notice> <WebLogicServer> <mvno-test-ali-1> <diameter1> <Main Thread> <<WLS Kernel>> <> <> <1231511460762> <BEA-000365> <Server state changed to RUNNING>
####<Jan 9, 2009 3:31:00 PM CET> <Notice> <WebLogicServer> <mvno-test-ali-1> <diameter1> <Main Thread> <<WLS Kernel>> <> <> <1231511460766> <BEA-000360> <Server started in RUNNING mode>
####<Jan 9, 2009 3:31:02 PM CET> <Info> <EJB> <mvno-test-ali-1> <diameter1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1231511462256> <BEA-010008> <EJB Deploying file: uuid-4366c314e828566b-393be1a0-11ebbcd980e--7fff_dynamic_internal>
####<Jan 9, 2009 3:31:02 PM CET> <Info> <EJB> <mvno-test-ali-1> <diameter1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1231511462462> <BEA-010223> <EJB Deployed Message Driven Bean: uuid-4366c314e828566b-393be1a0-11ebbcd980e--7ffe>
####<Jan 9, 2009 3:31:02 PM CET> <Info> <EJB> <mvno-test-ali-1> <diameter1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1231511462559> <BEA-010008> <EJB Deploying file: uuid-4366c314e828566b-393be1a0-11ebbcd980e--7ffd_dynamic_internal>
####<Jan 9, 2009 3:31:02 PM CET> <Info> <EJB> <mvno-test-ali-1> <diameter1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1231511462620> <BEA-010223> <EJB Deployed Message Driven Bean: uuid-4366c314e828566b-393be1a0-11ebbcd980e--7ffc>
####<Jan 9, 2009 3:31:02 PM CET> <Info> <EJB> <mvno-test-ali-1> <diameter1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1231511462623> <BEA-010008> <EJB Deploying file: uuid-4366c314e828566b-393be1a0-11ebbcd980e--7ffb_dynamic_internal>
####<Jan 9, 2009 3:31:02 PM CET> <Info> <EJB> <mvno-test-ali-1> <diameter1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1231511462684> <BEA-010223> <EJB Deployed Message Driven Bean: uuid-4366c314e828566b-393be1a0-11ebbcd980e--7ffa>
####<Jan 9, 2009 3:31:02 PM CET> <Info> <EJB> <mvno-test-ali-1> <diameter1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1231511462689> <BEA-010008> <EJB Deploying file: uuid-4366c314e828566b-393be1a0-11ebbcd980e--7ff9_dynamic_internal>
####<Jan 9, 2009 3:31:02 PM CET> <Info> <EJB> <mvno-test-ali-1> <diameter1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1231511462742> <BEA-010223> <EJB Deployed Message Driven Bean: uuid-4366c314e828566b-393be1a0-11ebbcd980e--7ff8>
####<Jan 9, 2009 3:31:02 PM CET> <Info> <EJB> <mvno-test-ali-1> <diameter1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1231511462753> <BEA-010008> <EJB Deploying file: uuid-4366c314e828566b-393be1a0-11ebbcd980e--7ff7_dynamic_internal>
####<Jan 9, 2009 3:31:02 PM CET> <Info> <EJB> <mvno-test-ali-1> <diameter1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1231511462953> <BEA-010223> <EJB Deployed Message Driven Bean: uuid-4366c314e828566b-393be1a0-11ebbcd980e--7ff6>
####<Jan 9, 2009 3:31:02 PM CET> <Info> <EJB> <mvno-test-ali-1> <diameter1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1231511462956> <BEA-010008> <EJB Deploying file: uuid-4366c314e828566b-393be1a0-11ebbcd980e--7ff5_dynamic_internal>
####<Jan 9, 2009 3:31:03 PM CET> <Info> <EJB> <mvno-test-ali-1> <diameter1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1231511463020> <BEA-010223> <EJB Deployed Message Driven Bean: uuid-4366c314e828566b-393be1a0-11ebbcd980e--7ff4>
####<Jan 9, 2009 3:32:55 PM CET> <Alert> <WebLogicServer> <mvno-test-ali-1> <diameter1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1231511575216> <BEA-000396> <Server lock has been requested by <WLS Kernel>>
####<Jan 9, 2009 3:32:55 PM CET> <Notice> <WebLogicServer> <mvno-test-ali-1> <diameter1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1231511575219> <BEA-000365> <Server state changed to SUSPENDING>
####<Jan 9, 2009 3:32:55 PM CET> <Notice> <HTTP> <mvno-test-ali-1> <diameter1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1231511575231> <BEA-101278> <There are no active sessions. The Web service is ready to suspend.>
####<Jan 9, 2009 3:32:55 PM CET> <Info> <Cluster> <mvno-test-ali-1> <diameter1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1231511575244> <BEA-000158> <Server has stopped sending cluster heartbeats and announcements. It is still receiving heartbeats and announcements from other cluster members.>
####<Jan 9, 2009 3:32:55 PM CET> <Info> <Deployer> <mvno-test-ali-1> <diameter1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1231511575263> <BEA-149059> <Module DiameterAdapterEjb-0.1.3.0-SNAPSHOT.jar of application GG Enterprise Application with only DIAMETER modules is transitioning from STATE_ACTIVE to STATE_ADMIN on server diameter1.>
####<Jan 9, 2009 3:32:55 PM CET> <Info> <Deployer> <mvno-test-ali-1> <diameter1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1231511575263> <BEA-149060> <Module DiameterAdapterEjb-0.1.3.0-SNAPSHOT.jar of application GG Enterprise Application with only DIAMETER modules successfully transitioned from STATE_ACTIVE to STATE_ADMIN on server diameter1.>
####<Jan 9, 2009 3:32:55 PM CET> <Notice> <WebLogicServer> <mvno-test-ali-1> <diameter1> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1231511575405> <BEA-000365> <Server state changed to ADMIN>


What could be the reason? What else can I check?

Best regards,
Przemek

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points