Bug#300209: tomcat4: tomcat dies with "Parse error in default web.xml" after upgrade

[Barry Hawkins]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Christoph Martin wrote:
[...]
> This is totally independent of the contents of the web.xml file. I
> even exchanged the files with the contents of
> /usr/share/tomcat4/.debian/web.xml but to no avail.
> 
> Something seams to have changed between 4.1.30 and 4.1.31
> totally. This makes the package unusable for most installations.
[...]
Christoph,
    It could be that a version number needs to be added to a particular
dependency.  Given that numerous others including myself have upgraded
to this package without the issue you describe here, filing a bug with a
grave severity is a bit, well, "severe" on your part.
    Could you tell us which version of libcommons-collections-java you
have installed on this machine?  On my powerpc sid install, I currently
have:

$ dpkg -l libcommons-collections-java
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
uppercase=bad)
||/ Name           Version        Description
+++-==============-==============-============================================
ii  libcommons-col 2.1.1-3        A set of abstract data type interfaces
and i

    This parse error seems to be only for the web.xml inside your
application that has the context /hisqis/qisserver. Swapping it out with
the sample web.xml is /usr/share/tomcat4/.debian is not necessarily an
effective test.  Are any of the other web applications the only one
running on the tomcat instance in question?  If not, how does the
web.xml of working applications differ from this one?  Also, if it is
the only one, could you include its contents here, provided that nothing
sensitive is contained within the file?  We really need more information
to pursue the remedy of this bug.
    Also, if anything has changed regarding the status of this bug and
the problem you were experiencing, please update it on the bug report.
This report seems to have knocked tomcat4 out of testing and therefore
has jeopardized whether or not a Tomcat 4 server will be included in the
imminent Sarge release.

Regards,
- --
Barry Hawkins
All Things Computed
site: www.alltc.com
weblog: www.yepthatsme.com

Registered Linux User #368650
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFCVKEQHuKcDICy0QoRAuBLAJ9jSfKUyxl57GFnilO3+K2TsFsSNgCfZ5Gk
ljAjE5FfLd+ctO0zo7JCMIg=
=hxTr
-----END PGP SIGNATURE-----