Repeated Error Appears In Log File - ClusterManager: detected 1 failed or restarted instances (Doc ID 739623.1)

Last updated on JUNE 24, 2016

Applies to:

BI Publisher (formerly XML Publisher) - Version 10.1.3.2.0 to 10.1.3.4.1 [Release 10.1]
Information in this document applies to any platform.
***Checked for relevance on 29-Sep-2013***

Symptoms

Oracle BI Publisher has been deployed on a clustered application server architecture. As a result of that, the application log repeatedly shows errors in specific to the ClusterManager like:

...
- Job execution threads will use class loader of thread: OC4J Launcher
- Quartz Scheduler v.1.5.1 created.
- Using db table-based data access locking (synchronization).
- JobStoreTX initialized.
- Quartz scheduler 'BIPublisherScheduler' initialized from the specified file : '/oracle/oas/j2eemid1013/j2ee/BI_Publisher/applications/xmlpserver/xmlpserver/xdo/cache/xmlp61975252.tmp'
- Quartz scheduler version: 1.5.1
- Scheduler BIPublisherScheduler_$_pbreugel.be.oracle.com1206987906749 started.
08/03/31 20:25:07 Oracle Containers for J2EE 10g (10.1.3.3.0)  initialized
- ClusterManager: detected 1 failed or restarted instances.
- ClusterManager: Scanning for instance "pbreugel.be.oracle.com1206987906749"'s failed in-progress jobs.
- ClusterManager: detected 1 failed or restarted instances.
- ClusterManager: Scanning for instance "pbreugel.be.oracle.com1206987906749"'s failed in-progress jobs.
- ClusterManager: detected 1 failed or restarted instances.
- ClusterManager: Scanning for instance "pbreugel.be.oracle.com1206987906749"'s failed in-progress jobs.
- ClusterManager: detected 1 failed or restarted instances.
...

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