I'll go through my logs again and check that I'm not barking up the
wrong tree - or find the correct block point and reformulate my
question.
Just to decrease information entropy in the universe..
I was barking up the wrong tree. As it happens, a colleague's
watchdog/launcher wrapper program neglected to handle stderr, and
apparently the location I pinpointed in the Batik code was the most
common source of stderr output in this case - we usually use log4j.
Basically, the JVM's stderr buffer got full and blocked for the rest
of eternity.
The things you learn...
//ebu
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
