Process Remains Alive after DomainDaemon Stop on AIX (Doc ID 1987904.1)

Last updated on JUNE 09, 2017

Applies to:

Oracle Retail Predictive Application Server - Version 14.1 to 14.1.0.5 [Release 14.1]
Information in this document applies to any platform.

Symptoms

In Oracle Retail Predictive Application Server (RPAS) 14.1.0, running on AIX, the DomainDaemon process still shows as active in the process list (ps) after calling "stop".


Steps to Reproduce:   Note that in this example the port number used is 55105

1.  Start the DomainDaemon. 
     DomainDaemon -port 55105 -start -ssl 3 -loglevel all &

2.  Show process for DomainDaemon port 55105.
     ps -ef | grep -i 55105
     jblog 17825864 10158106   0 06:52:25  pts/3  0:00 DomainDaemon -port 55105 -start -ssl 3 -loglevel all


3.  Stop the DomainDaemon.
     DomainDaemon -port 55105 -stop
     trying to stop daemon on [localhost]:55105
     daemon stopped


4. Ping the DomainDaemon. Note the port is free.
     DomainDaemon -port 55105 -ping
     Pinging daemon caught exception:
     StreamException: Could not connect to the socket (Unix's errno 79; Connection refused)
     DomainDaemon on [localhost]:55105 could not be contacted.


5. Check the process for port 55105.  NOTE: This process should not be alive as the DomainDaemon was stopped.
     ps -ef | grep -i 55105
     jblog 17825864 10158106   0 06:52:25   pts/3  0:00 DomainDaemon -port 55105 -start -ssl 3 -loglevel all


6. Start the DomainDaemon 55105. Since the port is free, it is possible to restart the DomainDaemon.
     DomainDaemon -port 55105 -start -ssl 3 -loglevel all & 

Changes

 

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