Java client fails to start due to <defunct> Apache processes

Products

• CA Automic Applications Manager (AM)

Issue/Introduction

Error Message :
Unable to launch the Application

When trying to open the Applications Manager client from a saved Client.jnlp file, it fails to start up at all or error "Unable to launch the Application" is seen. Visiting the Java client Intro.html page results in a 404 error or Unable to connect error.

Investigation
Running a "ps -ef | grep defunct" command shows the apache process as <defunct> similar to the example below:

apache   13469 13466  0 12:58 ?        00:00:00 apache <defunct>
 

On Unix and Unix-like computer operating systems, a defunct process or zombie process is a process that has completed execution (via the exit system call) but still has an entry in the process table. It is a process in the "Terminated state".

 

Environment

Release: AAMOS499000-8.0-Automic Applications Manager-OS400 Agent
Component:

Cause

Cause type:
Configuration
Root Cause: Apache processes are .

Resolution

To fix processes that are <defunct>:

1. Send SIGCHLD signal to the parent process:

kill -s SIGCHLD <parent pid>

2. Kill the parent process:

kill -9 <parent pid>

3. Restart the server

Fix Status: No Fix

Fix Version(s):
N/A

Additional Information

Workaround :
N/A