Sharon Lucas wrote:
> It does appear that it is possible in certain cases (especially if a
> STAX job is terminated with running stafcmds and/or processes) that a
> STAX Job's STAFQueueMonitor thread is not terminating. Instead, it gets
> stuck in a forever loop (using up a lot of CPU) submitting a local QUEUE
> GET WAIT request which fails immediately with RC 5 and with the result
> shown below because the STAX job's handle has already been unregistered
> in another thread so it never receives the STAX job termination message
> on its queue (which normally causes the STAFQueueMonitor thread to stop
> RC: 5 (Handle Does Not Exist)
> Result: HandleManager::updateTimestamp() failed to update handle nn"
> This appears to be exactly what your strace showed for these threads.
> Thanks for providing the thorough debug information.
> This should be easy to fix. Once I have the fix, I can provide you with
> a private STAX.jar file to verify the fix. And this fix will go into
> the next release of STAX (V3.4.1) planned by be released at the end of
> March 2010 (next week).
please let me know if I need to provide more context from the email thread.