My Oracle Support Banner

Not Able To Stop ASAP Server After 30 Min Ideal Time (Doc ID 1616078.1)

Last updated on JUNE 07, 2019

Applies to:

Oracle Communications ASAP - Version 7.2.0 and later
Information in this document applies to any platform.
***Checked for Currency on 05-Aug-2015***

Symptoms

User has an ASAP 7.2.0 IBM server successfully installed in Production. Cartridge is deployed and checked with run_suite command; running successfully. Weblogic installed with VIP hostname.

ASAP is installed on one node with DB RAC and DB string provides scanIP with two common scanIP:1522:SID,scanIP:1522:SIDode. 2 is not available as of now.

User is facing an issue when the ASAP instance shuts down after 30minutes of  idle time on the ASAP server. The System does not have a firewall blocking or port blocking in server. VIP host changes have been done in ASAP.properties and ASAP.cfg file. SARM tables tbl_SRP and TBL_listrener. WebLogic files.


ERROR
-----------------------
stop_asap_sys -d

Stopping ASAP...
Unable to connect to Master Control Server, the server may not be
running or all connections are busy.

 bash-3.2$ stop_asap_sys -d

Stopping ASAP...
Unable to connect to Master Control Server, the server may not be
running or all connections are busy.
Unable to connect to Master Control Server, the server may not be
running or all connections are busy.
Master Control CTRLPROD is not running

 

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.