Oracle Exalytics and EPM 220.127.116.11 stop.sh Script Does Not Always Stop All the Java Web Applications
Last updated on AUGUST 09, 2016
Applies to:Hyperion Essbase - Version 18.104.22.168.500 and later
Oracle Exalytics Software - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
Checked for currency 09-AUG-2016.
When using the stop.sh script in Enterprise Performance Management (EPM) 126.96.36.199 and Financial Reporting on Exalytics, not all the processes are stopped.
For example, the script may be run successfully, but if a ps -ef grep command is issued, it will show that there are still running java processes:
$ ps - ef | grep oracle
oracle 20148 20006 11 May29 pts/0 02:47:49 /u01/app/oracle/Middleware/jrockit_160_37/bin/java -jrockit -Xms8192m -Xmx32768m -Dweblogic.Name=FinancialReporting0 -Djava.security.policy=/u01/app/oracle/Middleware/EPMSystem11R1
The problem is not unique to any particular process and the ones that have failed to stop at different times are EAS, Calc Manager, Planning and Financial Reporting.
This problem has also been seen on EPM servers running on standalone (non-Exalytics) servers - i.e. Linux and Windows based hosts.
If a script is run to stop the specific application that did not stop, it returns with a message saying the application is not running:
In such cases, the only way to stop the running process is to kill the process (kill - pid#).
Is there some other method that is recommended to more cleanly, and completely stop all processes?
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