On Aug 21, 2006, at 23:53, [EMAIL PROTECTED] wrote:
Hi,
<snip />
I gathered what info I could and attempted to stop the Jetty
servlet container in order to restart it. Jetty wouldn’t go down.
I tried kill. Then I tried kill -9 and it still wouldn’t go down!
Finally I had to reboot the linux box on which the web application
runs. Immediately upon reboot and auto-restart of Jetty, the web
app stopped responding as before. Still no indication as to the
problem. A few more kill, kill -9, reboot cycles later and the
system is running wonderfully as it did on Wed. and Thurs.
Has anyone experienced such strangeness after upgrading FOP? This
is perplexing.
No such stories heard so far, I'm afraid, but given the setup, it
sounds like a possible multi-threading issue, maybe a nasty deadlock
somewhere... ?
If you could provide us with more detailed info about what happened,
we might get a clue, but OTOH, it seems strange that FOP by itself
could trigger something as persistent as that.
All you can do FTM is hope it doesn't happen again, but try to
monitor closely --logging output? What was the last thing the threads
were doing right before they blocked? That might give us a hint about
which area of the code needs to be investigated.
Cheers,
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
