Too Many Time to Start or Stop Concurrent Managers [ID 726098.1]

Too Many Time to Start or Stop Concurrent Managers [ID 726098.1]
		Modified 07-FEB-2011 Type PROBLEM Status MODERATED

In this Document
Symptoms
Cause
Solution

---

Platforms: 1-914CU;

This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.

Applies to:

Oracle Application Object Library - Version: 11.5.10.0 to 11.5.10.2 - Release: 11.5.10 to 11.5.10
Information in this document applies to any platform.
***Checked for relevance on 07-Feb-2011***

Symptoms

Start the concurrent managers employs too much time (over 15 minutes).
After this time, when the concurrent managers are started, all works fine.
Same time to stop the concurrent managers.

This is a single-node e-business suite 11.5.10.2 on 2 cluster nodes.

Cause

In the FNDSMxxxxxx.mgr log file, the following error occurs :

The call to function PingProcess in cartridge CMDCART has failed

In the FNDCPGSC889911.txt log file you found the following :

Jul 31, 2008 5:46:37 PM CEST]:1214927197327:Thread[main,5,main]:0:-1:sid:x.x.x.x:-1: 1:ERROR:[SVC-GSM-WFMLRSVC-889911 :
oracle.apps.fnd.cp.gsc.SvcComponentContainer.startBusinessEventListener()]:BES system
could not establish connection to the control queue after 180 seconds.

Solution

In the start/stop shell script ($OAD_TOP/comn/admin/scripts/_), there was references to the real hostname.

Replace the reference of the real hostname with the logical hostname and concurrent managers starts up in 3 minutes.

---

Related Products Oracle E-Business Suite > Applications Technology > Application Object Library > Oracle Application Object Library Keywords CCMGR; CMDCART; STOP CONCURRENT MANAGER; THREADS; FAIL; CARTRIDGE; START CONCURRENT MANAGER

Back to top