SOA 11g: Clustered Managed Servers Fail to Move to a RUNNING State
Last updated on OCTOBER 25, 2016
Applies to:Oracle SOA Platform - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
You've built out a a two node soa cluster (admin server and DB layer on their own nodes) and are unable to bring the soa_server1 and soa_server2 nodes up and into a RUNNING state.
- soa managed servesr are not being started via Node Manager, but via startManagedWeblogic.sh soa_server1 http://adminServer:port on soa node
- your SOA database is running in MTS mode
It is seen that the soa servers never move into RUNNING state and always reports in the console as STARTING.
There are no obvious errrors in managed server startup logs.
You can validate a midtier connection to the backend DB layer via other jdbc tools
The admin server always starts ok.
If you target the soa databsources to the Admin server then those datasources test fine.
If the soa datasources are targeted only to the soa_cluster then you are unable to test them via the Weblogic Console > services > jdbc > datasources > monitoring tab (because the managed servers are not up and therefore the jdbc connections cannot be tested
New installation of Oracle SOA Suite 11g
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms