Singleton Service Gets Restarted Permanently In Oracle Weblogic Cluster - BEA-000190 Followed By BEA-000189
(Doc ID 1502786.1)
Last updated on OCTOBER 02, 2020
Applies to:Oracle WebLogic Server - Version 10.3.4 and later
Information in this document applies to any platform.
Checked for currency on 02-Oct-2020
This is regarding an Oracle WebLogic cluster hosting one domain called Domain1 consisting of 5 Managed Server (MS) nodes. Each MS node is running on a separate hardware server. Within the cluster, one Singleton Service called <ServiceName> is defined, which receives JMS messages and invokes EJBs in the Domain1 domain. The following message is repeatedly seen in the ManagedServer2.log:
managedServer2 is defined as the preferred server for hosting the Singleton Service <ServiceName>. The cluster's integrity has already been checked, which looks fine. All nodes are permanently available. The state of the singleton service was also checked in the WebLogic console. The <ServiceName> service is currently running on ManagedServer1, but the trace output is found on ManagedServer2. The DB lease table (singleton_service_db_table.txt) also shows that <ServiceName> is running on ManagedServer2 service.<ServiceName> -123456789/ManagedServer2.
The issue does not cause any major operational problems when it is reported. However, the problem is still present after a complete maintenance start of all Managed Servers. When checking the <ServiceName> Singleton Service, it actually stops and starts again by itself, without showing any exception in the service implementation itself.
Why are these frequent messages occurring?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document