cma dump log

[Michael Murphy_2]

Folks,

I have a soon-to-be retired application that keeps locking up and generating a cma_dump.log (10.20). From the log it seems that all of the threads for the process are blocked - getting "no available vp". Read several forum discussions about signals handling and threads - this is apparently caused by all threads busy and signal coming in. Was thinking of trying a few things - wondering if any others had resolved this by:

-using bourn shell to start process and "trap" all signals so that this doesn't occur

-spawning a greater number of threads so that that they don't all appear to be busy when a signal comes through.

Thanks...