OSB / ALSB Managed-Servers go Into Admin-State When Updating a Project in the Service-Bus-Console
(Doc ID 1160284.1)
Last updated on APRIL 23, 2019
Applies to:Oracle Service Bus - Version 2.6 to 10.3.1 [Release Aqualogic Service Bus to AS10gR3]
Information in this document applies to any platform.
The scenario here is that there is a Oracle Service Bus Cluster with multiple managed servers. After making changes to the OSB deployments in a session, activating this session in the OSB console causes all of the managed servers to go into an Admin-State, before forcing shutting down shortly afterwards.
Logs show the following errors:
<[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1279626089573> <BEA-000365> <Server state changed to SUSPENDING>
When the servers are restarted, they do so without issue.
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