GSMServiceController and FNDLIBR Processes Remain Running after adstpall.sh
(Doc ID 1589321.1)
Last updated on APRIL 15, 2024
Applies to:
Oracle Applications DBA - Version 12.2 to 12.2.2 [Release 12.2Cloud]Oracle Concurrent Processing - Version 12.2.11 to 12.2.11 [Release 12.2]
Information in this document applies to any platform.
Symptoms
After running adstpall.sh some Concurrent Manager / Processing related processes do not stop.
Some processes remain running on the application server, as for example:
FNDLIBR
PALIBR
/fs1/FMW_Home/jrockit32/bin/java -DCLIENT_PROCESSID=4 -Dhttp.proxyHost= -Dhttp.proxyPort= -Dhttp.nonProxyHosts= -Djava.awt.headless=true -server -Xmx384m -Doracle.apps.fnd.common.Pool.leak.mode=stderr:off -verbose:gc -mx1024m -Ddbcfile=<FND_TOP>/secure/PROD.dbc -Dcpid=8 -Dconc_queue_id=6 -Dqueue_appl_id=0 -Dlogfile=<log file location> -DLONG_RUNNING_JVM=true -DOVERRIDE_DBC=true -DFND_JDBC_BUFFER_MIN=1 -DFND_JDBC_BUFFER_MAX=2 oracle.apps.fnd.cp.gsf.GSMServiceController
PALIBR
/fs1/FMW_Home/jrockit32/bin/java -DCLIENT_PROCESSID=4 -Dhttp.proxyHost= -Dhttp.proxyPort= -Dhttp.nonProxyHosts= -Djava.awt.headless=true -server -Xmx384m -Doracle.apps.fnd.common.Pool.leak.mode=stderr:off -verbose:gc -mx1024m -Ddbcfile=<FND_TOP>/secure/PROD.dbc -Dcpid=8 -Dconc_queue_id=6 -Dqueue_appl_id=0 -Dlogfile=<log file location> -DLONG_RUNNING_JVM=true -DOVERRIDE_DBC=true -DFND_JDBC_BUFFER_MIN=1 -DFND_JDBC_BUFFER_MAX=2 oracle.apps.fnd.cp.gsf.GSMServiceController
The only choice is to wait for the processes to die naturally after some time or use 'kill -9' making sure first that the managers are not actively running concurrent manager jobs.
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 |