Martin Grotzke wrote:
dear tomcat-developers,
i installed the latest tomcat-5.5.4.
when i try to start a webapp that runs without problems
on tomcat 5.5.3, i get the following error:
It works for me. I d/led the distribution, as packaging problems are
always a possibility.
----------------
INFO: Starting Servlet Engine: Apache Tomcat/5.5.4
Nov 1, 2004 10:24:46 AM org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
- Initializing log4j with '/path/to/webapp/WEB-INF/log/log4j.mescalin.xml'.
Nov 1, 2004 10:24:50 AM org.apache.catalina.core.StandardPipeline registerValve
INFO: Can't register valve ErrorReportValve[localhost]
javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.DocumentBuilderFactoryImpl could not be instantiated: java.lang.NullPointerException
at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:104)
at org.apache.commons.modeler.util.DomUtil.readXml(DomUtil.java:284)
at org.apache.commons.modeler.modules.MbeansDescriptorsDOMSource.execute(MbeansDescriptorsDOMSource.java:130)
at org.apache.commons.modeler.modules.MbeansDescriptorsDOMSource.loadDescriptors(MbeansDescriptorsDOMSource.java:120)
For some reason modeler tries to use Xerces without the right Java 5
package name. Your system configuration seems bad.
----------------
starting tomcat stops with this error, and tomcat will not
respond to any request, neither for the context that caused
the error, nor for other contexts like the default one.
the start procedure stops with the stack trace, there's no message
like "INFO: Server startup in .... ms"...
nmap shows the port 8080 to be open, but netstat does not
list the request made from the browser
kill -3 shows the following output:
-----------------
Full thread dump Java HotSpot(TM) Client VM (1.5.0-b64 mixed mode, sharing):
"DestroyJavaVM" prio=1 tid=0x0805bff0 nid=0x1ff7 waiting on condition
[0x00000000..0xfeffd040]
"Thread-2" prio=1 tid=0x082b5910 nid=0x2007 waiting on condition
[0x0570c000..0x0570c480]
at java.lang.Thread.sleep(Native Method)
at
com.freiheit.vps.schnittstellen.urllogin.LoginFilter$1.run(LoginFilter.java:83)
at java.lang.Thread.run(Thread.java:595)
"Thread-1" daemon prio=1 tid=0x085e9d18 nid=0x2006 waiting on condition
[0x063cc000..0x063cc800]
at java.lang.Thread.sleep(Native Method)
at org.apache.log4j.helpers.FileWatchdog.run(FileWatchdog.java:95)
"Low Memory Detector" daemon prio=1 tid=0x080a0de8 nid=0x2002 runnable
[0x00000000..0x00000000]
"CompilerThread0" daemon prio=1 tid=0x0809f898 nid=0x2001 waiting on condition
[0x00000000..0x02f34068]
"Signal Dispatcher" daemon prio=1 tid=0x0809e9c0 nid=0x2000 runnable
[0x00000000..0x00000000]
"Finalizer" daemon prio=1 tid=0x08099c60 nid=0x1fff in Object.wait()
[0x02eb3000..0x02eb3580]
at java.lang.Object.wait(Native Method)
- waiting on <0xb73c68d8> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:116)
- locked <0xb73c68d8> (a java.lang.ref.ReferenceQueue$Lock)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:132)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)
"Reference Handler" daemon prio=1 tid=0x08098f70 nid=0x1ffe in Object.wait()
[0x076d5000..0x076d5500]
at java.lang.Object.wait(Native Method)
- waiting on <0xb73c6958> (a java.lang.ref.Reference$Lock)
at java.lang.Object.wait(Object.java:474)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116)
- locked <0xb73c6958> (a java.lang.ref.Reference$Lock)
"VM Thread" prio=1 tid=0x080964a0 nid=0x1ffd runnable
"VM Periodic Task Thread" prio=1 tid=0x080a2278 nid=0x2003 waiting on condition
-----------------
I'd like to understand why you think a thread dump is useful to debug a
JAXP configuration issue. Funny :)
one note about the LoginFilter u see in this list:
- when i remove the filter mapping, this filter get's started,
and the error is the same as described above
- when i remove both filter mapping and filter definition,
i get the stack trace as described above, but the tomcat
process terminates with the error (the filter's not loaded).
i don't know if this are different problems, or if there's some
relation.
one problem is that the webapp does not start, but another problem
is that tomcat fails to start if one context is not starting correctly.
my system:
fedora core 2
sun jdk 1.5 (jpackage.org)
tomcat 5.5.4 alpha
log4j 1.2.7 (the same with 1.2.8)
do you need some more information?
for now, i'll step back to tomcat 5.5.3.
Your report is bogus, so step back all you want, but there won't be any fix.
Rémy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
