BugRat Report # 679

Project: Tomcat Release: 3.2.1
Category: Bug Report SubCategory: New Bug Report
Class: swbug State: received
Priority: medium Severity: critical
Confidence: public

Submitter: _Anonymous ( anonymous-bug@cortexity.com )
Date Submitted: Dec 31 2000, 07:34:09 CST
Responsible: Z_Tomcat Alias ( tomcat-bugs@cortexity.com )

Synopsis:
SIGSEGV 11 on launch of Tomcat 3.2.1 with JDK 1.3
Environment: (jvm, os, osrel, platform)
1.3, linuxppc, 2000, mac

Additional Environment Description:

Report Description:
Tomcat 3.2.1 with jdk 1.3 seg faults on startup. Tomcat 3.2b7 and jdk 1.3 work fine on this machine. Tomcat 3.2.1 and jdk 1.2.2 work fine on this machine. Tomcat 3.2b7 and jdk 1.2.2 work fine on this machine. Only the combination of Tomcat 3.2.1 and jdk 1.3 cause the seg fault. The priority is set to medium on this report because I can run with jdk 1.2.2. If you feel the priority should be higher or lower please feel free to adjust. Below is a dump of the error report. I don't have enough experience in this environment to suggest the source of the problem, but would be happy to try scenarios to help track this down. The directory /usr/local/jsdk is sym linked to which ever jdk version I want to run, and the same for the /usr/local/jakarta-tomcat directory. Let me know if there is anything else I can do to help, Frank ---------------------------------------------------------- [root@iNetServer jakarta-tomcat]# bin/startup.sh Guessing TOMCAT_HOME from tomcat.sh to bin/.. Setting TOMCAT_HOME to bin/.. Using classpath: bin/../lib/ant.jar:bin/../lib/jasper.jar:bin/../lib/jaxp.jar:bi n/../lib/parser.jar:bin/../lib/servlet.jar:bin/../lib/test:bin/../lib/webserver. jar:/usr/local/jsdk/bin/../lib/tools.jar [root@iNetServer jakarta-tomcat]# SIGSEGV 11* segmentation violation si_signo [0]: no signal si_errno [0]: Success si_code [268548760]: unknown siginfo stackpointer=0x7fffcff8 Full thread dump Classic VM (Blackdown-1.3.0-FCS, native threads): "Thread-0" (TID:0x30cd9f20, sys_thread_t:0x101ecec0, state:CW, native ID:0x1 005) prio=5 at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:420) at org.apache.tomcat.util.Queue.pull(Queue.java:89) at org.apache.tomcat.logging.LogDaemon$1.run(TomcatLogger.java:238) at org.apache.tomcat.logging.LogDaemon.run(TomcatLogger.java:254) "Finalizer" (TID:0x30cc0528, sys_thread_t:0x10060318, state:CW, native ID:0x c04) prio=8 at java.lang.Object.wait(Native Method) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:108) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:123) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:162) "Reference Handler" (TID:0x30cc0300, sys_thread_t:0x1005a208, state:CW, nati ve ID:0x803) prio=10 at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:420) at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:110) "Signal Dispatcher" (TID:0x30cc0330, sys_thread_t:0x10056818, state:CW, nati ve ID:0x402) prio=5 "main" (TID:0x30cc01a0, sys_thread_t:0x1001bb18, state:R, native ID:0x400) p rio=5 at java.lang.reflect.Method.copy(Method.java:280) at java.lang.reflect.Method.getParameterTypes(Method.java:90) at org.apache.tomcat.util.xml.SetProperties.setProperty(XmlMapper.java:6 31) at org.apache.tomcat.util.xml.SetProperties.start(XmlMapper.java:611) at org.apache.tomcat.util.xml.XmlMapper.matchStart(XmlMapper.java:384) at org.apache.tomcat.util.xml.XmlMapper.startElement(XmlMapper.java:81) at com.sun.xml.parser.Parser.maybeElement(Parser.java:1391) at com.sun.xml.parser.Parser.content(Parser.java:1499) at com.sun.xml.parser.Parser.maybeElement(Parser.java:1400) at com.sun.xml.parser.Parser.content(Parser.java:1499) at com.sun.xml.parser.Parser.maybeElement(Parser.java:1400)

How To Reproduce:
null

Workaround:
null

View this report online...