Trouble-shooting zombie kernel

What is Zombie Kernel? When the kernel do not respond back to its parent process.
Eg web client exception on E1 application..

The parent process from servers can be JDESNET - Network listener

1. A BSFN runs indefinitely (loops).
2. BSFN has a memory leak due to incorrect pointer handling in the C code.
3. Abrupt termination of the parent process.
4. IPC resource lock, resource corruption or resource conflict.
5. Severe errors from database, like internal errors that the kernel cannot handle.
6. Native errors from the Operating System that generates signals not understandable to the kernel.

      7.User Record Reservations (P00095)

      8. Transaction, Transaction Processing, Commit and Rollback

To identify the exact location of the log in entsvr, pls refer to JobFile parameter in the [DEBUG] section of the Enterprise server JDE.INI.

Also locate logs on the Enterprise server called: JDE_XXXX.LOG (where XXXX is the OS process ID of that kernel). 

It is best to send ALL the JDE_XXXX.LOG files from the Enterprise server zipped into one, so that all kernels on the server can be reviewed.

Logs for all the JDENET_N process (Network Process); again use Server Manager or SAW to extract these.

If the zombie is caused by BSFN ..Then, 

[JDENET_KERNEL_DEF6]

krnlName=CALL OBJECT KERNEL
.......
maxNumberOfProcesses=   ; 1 COK = 17user  too many would cause server less responsive
numberOfAutoStartProcesses=0  -- this should be considered a temporary fix and further investigation of the offending BSFN is required.  Keeping this setting at 0 is not recommended.  

How to solve it ?

Bouncing the Enterprise Server at the end of the day helps to clear zombie and resource issues on the Enterprise Server.

Click Remove zombie button on SMC would reclaim the resources in entsvr...

Kercycle recycling also can clear the zombie...