paktotam process goes to zombie after finishing

[Mark the Ump]

We are experiencing an unusual problem. When we kick off a full server build (with or without client, which succeeds), it copies the spec files to server, the paktotam kicks off and unpacks the spec file, and then rather than starting the unpack on the next spec file, it goes to zombie and another paktotam starts. This goes on for all of the spec files until it reaches the ddtabl spec at which point the build stops and the last paktotam finishes (glbltabl) then it zombies.

The debug log shows no errors, but just stops, and NO jde.log is generated. If anyone has any ideas on this, please let us know. This is a show stopper at this point and JDE Development is slow to respond.

 

[Soumen]

What does the ServerBuild Log on Deployment Server say? Also get the jde.log with the pid of the paktotam kernel.

Will have to check the logs before suggesting anything.

Thanks,
Soumen

 

[altquark]

Mark

Have you restarted JDE Services prior to launching the package build ? Is an update package working (but just a full build) ?

You definitely need to go through the logs to identify why the process is failing. Standard troubleshooting. JDE/Oracle will also require that you send them the logs for the zombie PID.

 

[Mark the Ump]

This is the strange part. There are 10 paktotam processes, and all end up going to zombie (defunct). There are no errors in the jdedebug log or the svrbuild log. The PDF comes up showing all of the spec builds as "PROCESSING". There are no errors anywhere to give us any information.