You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2006/10/02 22:21:41 UTC

DO NOT REPLY [Bug 38898] - Tomcat service fails without error message

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38898>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=38898





------- Additional Comments From shankarunni@netscape.net  2006-10-02 13:21 -------
You could attach hs_err_pid####.log's till you're blue in the face, but nothing
changes the fact that what's wrong here is a *Java Virtual Machine* bug, not a
*Tomcat source* bug.

JVM crashes can happen for as much of a variety of reasons as an OS "blue screen
of death" - Java Virtual Machine internal coding errors, driver bugs, OS bugs,
hardware quirks, ...

First order of business: use the latest Java VM version (1.5.0_08 as of today).
See if this still happens.

Then, take your application to a different machine (different OS, and preferably
different architecture, e.g. Solaris on Sparc), and try to make it crash the
same way using the *exact same inputs*.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org