wood burning stoves*
The moose likes Tomcat and the fly likes Tomcat service not staying running Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Products » Tomcat
Bookmark "Tomcat service not staying running" Watch "Tomcat service not staying running" New topic
Author

Tomcat service not staying running

Alex Stancic
Greenhorn

Joined: Jul 03, 2012
Posts: 2
Did any of you encountered this kind of issue? Installed tomcat 6.0 and 7.0 and both won't stay running. As far as I can tell, this is not a port issue...here is the error:

#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ILLEGAL_INSTRUCTION (0xc000001d) at pc=0x000000000123cdae, pid=5868, tid=3904
#
# JRE version: 6.0_20-b02
# Java VM: Java HotSpot(TM) 64-Bit Server VM (16.3-b01 mixed mode windows-amd64 )
# Problematic frame:
# J org.apache.tomcat.util.IntrospectionUtils.setProperty(Ljava/lang/Object;Ljava/lang/String;Ljava/lang/String;Z)Z
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp


I also submitted a bug report for this issue:

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7176268

Any help would be much appreciated.

Thanks,
Alex
Tim Holloway
Saloon Keeper

Joined: Jun 25, 2001
Posts: 15962
    
  19

Welcome to the JavaRanch, Alex!

What you have is a defective JVM. This is not a Tomcat problem.

No Java program should ever crash the JVM. The JVM design does not permit that. Unfortunately, no software is perfect, and certain JVM releases when used in certain ways to trigger their own internal bugs and crash.

The only cure is to obtain a different JVM and use that one to run Tomcat, instead.

It doesn't always have to be a newer JVM version, just a different version, since the bugs usually don't repeat between releases.


Customer surveys are for companies who didn't pay proper attention to begin with.
Alex Stancic
Greenhorn

Joined: Jul 03, 2012
Posts: 2
Tim Holloway wrote:Welcome to the JavaRanch, Alex!

What you have is a defective JVM. This is not a Tomcat problem.

No Java program should ever crash the JVM. The JVM design does not permit that. Unfortunately, no software is perfect, and certain JVM releases when used in certain ways to trigger their own internal bugs and crash.

The only cure is to obtain a different JVM and use that one to run Tomcat, instead.

It doesn't always have to be a newer JVM version, just a different version, since the bugs usually don't repeat between releases.


Hi Tim,

I will try with a different JVM and see how it goes.

Thanks,
Alex
Rob Spoor
Sheriff

Joined: Oct 27, 2005
Posts: 19656
    
  18

Tim Holloway wrote:What you have is a defective JVM. This is not a Tomcat problem.

I'm not so sure.

No Java program should ever crash the JVM. The JVM design does not permit that. Unfortunately, no software is perfect, and certain JVM releases when used in certain ways to trigger their own internal bugs and crash.

Any "NullPointerException" from native code can cause the JVM to crash like this. This native code can be the JVM but it can also be any third party code.


SCJP 1.4 - SCJP 6 - SCWCD 5 - OCEEJBD 6
How To Ask Questions How To Answer Questions
 
jQuery in Action, 2nd edition
 
subject: Tomcat service not staying running
 
Similar Threads
OutOfMemory error but application continues
Tomcat 6.0.14 crash on RedHat linux 5.2 with java 1.6
JVM Crashes while image load using Java Advanced Imaging (JAI) library
Problem running JSP 2.0