Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Subject: tomcat 5.5.4 does not start when a single webapp fails
From: Martin Grotzke <martin.grotzke@javakaffee.de>
To: tomcat-dev@jakarta.apache.org
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature"; boundary="=-9BOSMvh0BppBOGo7h+pw"
Message-Id: <1099303350.3688.39.camel@localhost>
Mime-Version: 1.0
Date: Mon, 01 Nov 2004 11:02:30 +0100

--=-9BOSMvh0BppBOGo7h+pw
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

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:

----------------
> 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 registe=
rValve
> INFO: Can't register valve ErrorReportValve[localhost]
> javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.j=
axp.DocumentBuilderFactoryImpl could not be instantiated: java.lang.NullPoi=
nterException
>         at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentB=
uilderFactory.java:104)
>         at org.apache.commons.modeler.util.DomUtil.readXml(DomUtil.java:2=
84)
>         at org.apache.commons.modeler.modules.MbeansDescriptorsDOMSource.=
execute(MbeansDescriptorsDOMSource.java:130)
>         at org.apache.commons.modeler.modules.MbeansDescriptorsDOMSource.=
loadDescriptors(MbeansDescriptorsDOMSource.java:120)
----------------

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, sharin=
g):
>=20
> "DestroyJavaVM" prio=3D1 tid=3D0x0805bff0 nid=3D0x1ff7 waiting on conditi=
on [0x00000000..0xfeffd040]
>=20
> "Thread-2" prio=3D1 tid=3D0x082b5910 nid=3D0x2007 waiting on condition [0=
x0570c000..0x0570c480]
>         at java.lang.Thread.sleep(Native Method)
>         at com.freiheit.vps.schnittstellen.urllogin.LoginFilter$1.run(Log=
inFilter.java:83)
>         at java.lang.Thread.run(Thread.java:595)
>=20
> "Thread-1" daemon prio=3D1 tid=3D0x085e9d18 nid=3D0x2006 waiting on condi=
tion [0x063cc000..0x063cc800]
>         at java.lang.Thread.sleep(Native Method)
>         at org.apache.log4j.helpers.FileWatchdog.run(FileWatchdog.java:95=
)
>=20
> "Low Memory Detector" daemon prio=3D1 tid=3D0x080a0de8 nid=3D0x2002 runna=
ble [0x00000000..0x00000000]
>=20
> "CompilerThread0" daemon prio=3D1 tid=3D0x0809f898 nid=3D0x2001 waiting o=
n condition [0x00000000..0x02f34068]
>=20
> "Signal Dispatcher" daemon prio=3D1 tid=3D0x0809e9c0 nid=3D0x2000 runnabl=
e [0x00000000..0x00000000]
>=20
> "Finalizer" daemon prio=3D1 tid=3D0x08099c60 nid=3D0x1fff 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=
)
>=20
> "Reference Handler" daemon prio=3D1 tid=3D0x08098f70 nid=3D0x1ffe in Obje=
ct.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:11=
6)
>         - locked <0xb73c6958> (a java.lang.ref.Reference$Lock)
>=20
> "VM Thread" prio=3D1 tid=3D0x080964a0 nid=3D0x1ffd runnable
>=20
> "VM Periodic Task Thread" prio=3D1 tid=3D0x080a2278 nid=3D0x2003 waiting =
on condition
-----------------

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.

thanx for your help,
martin


--=-9BOSMvh0BppBOGo7h+pw
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBBhgm17FvOl7Te+pYRAsCUAJ0Z3HKMzX2jTvUknf88PnhxbKIJCQCdF4sX
53GATlBgMgyT2NRTSI6tZ/8=
=eIla
-----END PGP SIGNATURE-----

--=-9BOSMvh0BppBOGo7h+pw--