Process Shutdown – Signal 0, core dumped

[Jerry Magrann]

Has anyone encountered the error on the attached screen shot –

Topic

[Robert Kersemakers]

Wow…

As you’re using CL5.3, you may consider:

* reducing the number of threads per process.

* avoiding inter-process communication (I can’t really see from this view if that’s the case here)

* upgrading to a newer version of CL.

We have had problems with earlier versions (3.7 or 5.2) where processes stopped when there were too many threads in it. Haven’t seen this recently; hardware can be a factor as well.

Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands

[Jerry Magrann]

Yes it is 5.3 on AIX 5.2. We are moving to CL 5.8 on Redhat 5.4 in the next month.  Some of the other processes do have more threads and inter-process communication, but this one that crashed is one of the lower volume processes.

[Angie Zmich]

I am having the same problem.  Did you ever find a resolution?

[David Barr]

I’d suggest you contact tech support about the problem.

If you want to try to troubleshoot the problem yourself, it’s helpful to look in the process log for errors. You can also try producing a core dump file to try to figure out what the engine was doing when it crashed.

[Ronald Ortiz]

I would also avoid using the process as a way to segregate the message types.  The point of the process is really to do load balancing of threads, depending on their volumes.  I would imagine your ADT process is getting hit pretty heavily as it probably has the highest volumes.  

I would divide it as such:

Site:

   Proc_1

             thread

             thread

   Proc_2

             thread

             thread

   Proc_3

             thread

             thread

-Ron

[Author]

Replies