Unable to Start a New Managed Server in OSB (Oracle Service Bus) Cluster (Doc ID 889158.1)

Last updated on APRIL 01, 2013

Applies to:

Oracle Service Bus - Version 2.1 and later
Information in this document applies to any platform.

Symptoms

Oracle Service Bus (OSB) Product Information Center  > Index Master Note for Oracle Service Bus > Master Note for Troubleshooting Oracle Service Bus Clustered Production Systems > Note 889158.1


Cluster configuration issue, unable to start a new Managed Server in a Oracle Service Bus (OSB) cluster, if the managed server is on a different machine than managed server 1.

ERROR:
Cluster deployment fails with the following error message:

Connectivity with the ManagedServer_2 at the JMX Service URL of
service:jmx:t3://xxx.xx.xx.xx:8052/jndi/weblogic.management.mbeanservers.runtime.>
####<Sep 13, 2009 6:51:32 PM PDT> <Info> <JMX>
<vdoraiswamy.sv2.corp.equinix.com> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <>
<1252893092520> <BEA-149507> <JMX Connectivity has been discontinued with the managed server ManagedServer_2.>
####<Sep 13, 2009 6:51:32 PM PDT> <Info> <Server>
<vdoraiswamy.sv2.corp.equinix.com> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <>
<1252893092520> <BEA-002634> <The server "ManagedServer_2" disconnected from this server.>


  



Cause

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