This week's book giveaway is in the Clojure forum.
We're giving away four copies of Clojure in Action and have Amit Rathore and Francis Avila on-line!
See this thread for details.
Win a copy of Clojure in Action this week in the Clojure forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Tomcat service not staying running

 
Alex Stancic
Greenhorn
Posts: 2
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
Pie
Posts: 17626
39
Android Eclipse IDE Linux
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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.
 
Alex Stancic
Greenhorn
Posts: 2
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
Pie
Posts: 20381
46
Chrome Eclipse IDE Java Windows
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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.
 
I agree. Here's the link: http://aspose.com/file-tools
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic