We had a Tomcat crash on a customer box, a few hours ago (a simple restart got them back up and running), and it produced a whole bunch of errors in the general vein of
*** Invalid JIT return address 00000006E2E2E400 in 00000001A83C5210

before finally failing with a null pointer exception, and producing a Java dump, a Snap dump, and a JIT dump, all over the course of a couple of seconds.

Prior to that, our webapp was having a great deal of trouble accessing Office365.

Other than that it's almost certainly our webapp, rather than Tomcat itself, that caused the "Invalid JIT return address" messages, does anybody here have any insights? I've literally never seen messages of this type before.

--
JHHL

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to