• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Tomcat service not staying running

 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • 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
 
Saloon Keeper
Posts: 27762
196
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • 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
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • 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
 
Sheriff
Posts: 22783
131
Eclipse IDE Spring VI Editor Chrome Java Windows
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • 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.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic