ClusterTimerAuthority Error with NameNotFoundException Thrown when the OSB Managed Server Starts Up (Doc ID 1367468.1)

Last updated on NOVEMBER 03, 2016

Applies to:

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

Symptoms

In a Fusion Middleware 11g domain including SOA and OSB servers, one of the OSB servers throws the following exception while starting up:

<Oct 4, 2011 1:11:24 PM ART> <Error> <ClusterTimer> <BEA-000000> <Cannot contact Admin server. Therefore constructing the Cluster Authority Current time with the time skew 0
java.rmi.RemoteException: ClusterTimerAuthority error; nested exception is:
javax.naming.NameNotFoundException: While trying to lookup 'com.bea.alsb.internal.clusterTimerAuthority' didn't find subcontext 'alsb'. Resolved 'com.bea' [Root exception is javax.naming.NameNotFoundException: While trying to lookup 'com.bea.alsb.internal.clusterTimerAuthority' didn't find subcontext 'alsb'. Resolved 'com.bea']; remaining name 'alsb/internal/clusterTimerAuthority'

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