Weblogic Admin Server Stuck during Startup

We had Oracle Service Bus 12.1.3 cluster. Admin server happened to restart for some reason. But admin server startup process used to stuck and not move at all. Logs when admin server was stuck listed below:

AdminServer.log
####<May 22, 2017 4:23:10 AM PDT> <Info> <Deployer> <serverabc.xyz> <AdminServer> <[STANDBY] ExecuteThread: ‘3’ for queue: ‘weblogic.kernel.Default (self-tuning)’> <<WLS Kernel>> <> <0d1240df-6563-4d52-be74-200ed896969e-00000004> <1495452190002> <BEA-149060> <Module /httpTransport of application Service Bus Kernel successfully transitioned from STATE_PREPARED to STATE_ADMIN on server AdminServer.>
####<May 22, 2017 4:23:14 AM PDT> <Info> <Server> <serverabc.xyz> <AdminServer> <[ACTIVE] ExecuteThread: ‘1’ for queue: ‘weblogic.kernel.Default (self-tuning)’> <<WLS Kernel>> <> <> <1495452194569> <BEA-002635> <The server “osb_server1” connected to this server.>
####<May 22, 2017 4:23:14 AM PDT> <Info> <JMX> <serverabc.xyz> <AdminServer> <[ACTIVE] ExecuteThread: ‘1’ for queue: ‘weblogic.kernel.Default (self-tuning)’> <<WLS Kernel>> <> <> <1495452194614> <BEA-149506> <Established JMX Connectivity with osb_server1 at the JMX Service URL of service:jmx:t3://10.1.1.1:8007/jndi/weblogic.management.mbeanservers.runtime.>
####<May 22, 2017 4:23:24 AM PDT> <Info> <Health> <serverabc.xyz> <AdminServer> <weblogic.GCMonitor> <<anonymous>> <> <> <1495452204485> <BEA-310002> <48% of the total memory in the server is free.>
AdminServer.out

<May 22, 2017 4:22:24 AM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY.>
<May 22, 2017 4:22:24 AM PDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING.>
<May 22, 2017 4:22:24 AM PDT> <Notice> <Log Management> <BEA-170032> <The Server has detected ODL configuration for java.util.logging. The PlatformLoggerLevels attribute configuration on the LogMBean will be ignored.>
<May 22, 2017 4:23:02 AM PDT> <Warning> <HTTP> <BEA-101384> <WLServlet annotation is deprecated, please use servlet 3.0 annotation instead. App:service-bus@servicebus, Class:oracle.adfinternal.view.faces.activedata.AdsServlet>
<May 22, 2017 4:23:04 AM PDT> <Warning> <HTTP> <BEA-101384><WLServlet annotation is deprecated, please use servlet 3.0 annotation instead. App:em@em, Class:oracle.adfinternal.view.faces.activedata.AdsServlet><May 22, 2017 4:23:05 AM PDT> <Warning> <J2EE> <BEA-160140> <Unresolved optional package references (in META-INF/MANIFEST.MF): [Extension-Name: oracle.bpm.runtime, referenced from: /orasoa/app/oracle/middleware/user_projects/domains/mydev_domain/servers/AdminServer/tmp/_WL_user/oracle.bpm.management.webapp/fccywl], [Extension-Name: oracle.bpm.client, referenced from: /orasoa/app/oracle/middleware/user_projects/domains/mydev_domain/servers/AdminServer/tmp/_WL_user/oracle.bpm.management.webapp/fccywl], [Extension-Name: oracle.bpm.projectlib, referenced from: /orasoa/app/oracle/middleware/user_projects/domains/mydev_domain/servers/AdminServer/tmp/_WL_user/oracle.bpm.management.webapp/fccywl], [Extension-Name: oracle.bpm.webapp.common, referenced from: /orasoa/app/oracle/middleware/user_projects/domains/mydev_domain/servers/AdminServer/tmp/_WL_user/oracle.bpm.management.webapp/fccywl]. Ensure that the referenced optional package has been deployed as a library.>

Analysis: Looks like Admin server stuck while trying to communicate with osb managed server. From logs, after 04:23 AM there was no activity in the logs but adminsever became active again after 04:29 that was after killing osb servers.

Resolution: After killing osb servers, admin server became active and state changed to RUNNING. It is not clear what really caused the issue but this behavior is not observed in later versions.

Update: This issue occurred again in 12.2.1.4.0 as well. This time we were able to prove our hypothesis. Please refer to this post.

Comments

Post a Comment

Popular posts from this blog

HOW WE REDUCED SOA OSB PROVISIONING FROM 4 DAYS TO 4 HOURS

 In our organization, we’ve undertaken the task of upgrading both SOA and OSB from version 12.2.1.3 to 12.2.1.4. This involves an out-of-place migration approach, wherein we create a new environment and switch traffic during the cutover. As you know, this process typically requires several days we opt for manual provisioing. A very significant amount of automation work was previously accomplished for 12.2.1.3 by our predecessors. Despite these efforts, the process still used to take lot of time due to following factors: Bugs in existing automation. For example, SOA composite deployments is not stable which warrants lot of manual work Import of 10s of TLS Certificates into KSS Manual retiring and shutting down of services Monitoring setup Miscellaneous: Increasing Log file count, enabling GC logging, changing heap parameters, bash profile changes While our current automation initiatives have yielded substantial savings, we aimed to capitalize on this upgrade activity to enable end-t...
Read more

NOT ABLE TO START RABBITMQ CLUSTER: CANNOT DECLARE A QUEUE ‘~S’ ON NODE ‘~S’: ~255P

We have 7 node rabbitmq cluster and we are using sharding queues. We have shutdown all non prod rabbitmq nodes as part of VM patching. As it was non prod, we thought of shutting down all together instead of rolling patching. We couldn’t start the any of the rabbitmq post patching. All of nodes were failing to start with the below error: 2022-06-23 05:13:10.104845-07:00 [error] <0.647.0> “Cannot declare a queue ‘~s’ on node ‘~s’: ~255p”, 2022-06-23 05:13:10.104845-07:00 [error] <0.647.0> [“queue ‘sharding: shard.my.queue – rabbit@rabbit1’ in vhost ‘my_vhost'” This is a known issue in some old versions of rabbitmq. rabbitmq node fails to come up with above error. Work around for this is to disable sharding policy for the problematic sharding queue. It can be done either from command line or from rabbitmq admin page. It requires to connect a running node. But as all the nodes were down, we could not disable sharding policy. Luckily, rabbitmq allows disabling sharding pulgi...
Read more

SOA SUITE 12.2.1.4 INSTALLATION: GOT EXCEPTION WHEN AUTO CONFIGURING THE SCHEMA COMPONENT(S) WITH DATA OBTAINED FROM SHADOW TABLE

  We planned to do out of place upgrade from soa suite 12.2.1.3 to 12.2.1.4. As part of this, we planned to automate end to end provisioning. While executing domain configuration using ansible and python scripts, we got following error in domain creation step. Got exception when auto configuring the schema component(s) with data obtained from shadow table. Failed to build JDBC Connection object: com.oracle.cie.domain.script.jython.CommandExceptionHandler. exception. Quick internet search gave few solutions like deleting domain-registry.xml file, verifying dehydration store password supplied to script etc. But none of them helped. After trying several options, I thought I might have done some stupid error prior to domain creation step. To track down the issue, though of checking what getDatabaseDefaults actually doing. I tried to grep for the getDatabaseDefaults function call inside oracle home. But couldn’t find the source code for the python function. As a final resort, thought of...
Read more