What Sent SIGQUIT to a Messaging Server Process? (Doc ID 1380132.1)

Goal

Messaging Server was restarted automatically because the watcher process detected that an imsconnutil process had "exited abnormally":

In the default log file:

Core dump analysis showed the process exited because it received a signal 3, SIGQUIT.  This is not a signal Messaging Server processes should have to deal with.  Nothing should be sending this signal to any Messaging Server processes and it is not a signal that would be automatically generated by anything else.

However, kill -3 is something done to Java JVM processes to cause them to dump a thread stack trace.  It is most likely that a sysadmin did that either accidentally on the Messaging Server process or perhaps ran a script intended to gather diagnostic information from Java processes, not realizing it would have negative effects on non-Java processes.

So the question is: how to tell what process sent SIGQUIT to this process?

Solution