Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade
severity 300209 serious thanks On Thu, Apr 07, 2005 at 02:37:30AM -0400, Jeff Breidenbach wrote: severity 300209 important stop This package works for me. Therefore at most the severity is important which is defined as a bug which has a major effect on the usability of a package, without rendering it completely unusable to everyone. Right, but missing Depends will make it fail for anyone not having the dependencies by accident anyway, and is defined by the release team to be of RC nature. The general consensus with pkg-java people seems to be that this needs to be fixed for the release too, so that matches. --Jeroen -- Jeroen van Wolffelaar [EMAIL PROTECTED] http://jeroen.A-Eskwadraat.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade
tags 300209 + pending thanks On Fri, Apr 08, 2005 at 07:06:28AM -0400, Barry Hawkins wrote: Thanks for the information. I was afraid it was something of that nature. Since Blackdown 1.3 and IBM 1.4 are what's available for PowerPC right now, I am not able to build this package without altering DBCP. The Tomcat 4 source requires the JDK to have some Sun security classes that IBM does not have. So, if Arnaud or Stefan could build tomcat4 with what I have checked in and sponsor an upload, we will likely have resolved this issue and gotten tomcat4 back into Sarge. The issue is supposed to be fixed in CVS, I succesfully built a new version of the package with it, after having reviewed the diff and found the current CVS to be okay. Barry Hawkins will soonishly test my builds, and when the tests turn out to be succesful, I'll sign upload. --Jeroen -- Jeroen van Wolffelaar [EMAIL PROTECTED] http://jeroen.A-Eskwadraat.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade
Barry Hawkins wrote: [...] Guys, I have committed a debian/control file for the tomcat4 package that imposes both build (tomcat4 source) and runtime(tomcat4 binary) dependencies the following library versions: libcommons-digester-java = 1.5.0.1 libcommons-collections-java = 2.1.1 libcommons-beanutils-java = 1.6.1 libcommons-logging-java = 1.0.4 This ensures that dependencies are satisfied for versions of the upstream libraries that are required by Tomat as well as one another, and ensures that the versions currently in testing are acceptable. If someone could please test this build on x86 and upload it, that would be great. I am out of town this week and it appears my DSL modem has locked up at home, preventing me from accessing my x86 box on which I normally build this. I tried to build with j2sdk1.3-blackdown/xmlParserAPIs.jar/xercesImpl.jar, but I get the commons-dbcp-related error shown at the bottom of this message. The package has built previously with the Sun 1.4 JDK packages generated by java-package without issue. $ debuild -ICVS -us -uc [...] BUILD FAILED /home/barryh/packages/tomcat4/tomcat4-4.1.31/build-tree/jakarta-tomcat-4.1.31-src/build.xml:67: The following error occurred while executing this line: java.lang.UnsupportedClassVersionError: org/apache/commons/dbcp/ConnectionFactory (Unsupported major.minor version 48.0) Hi Barry, this means that libcommons-dbcp-java was build without target=1.3 therefore it is not usable anymore with jdk1.3. Either you build tomcat with a jdk 1.4 or you rebuilt the libcommons-dbcp-java library with target=1.3. Wolfgang -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wolfgang Baer wrote: Barry Hawkins wrote: [...] The following error occurred while executing this line: java.lang.UnsupportedClassVersionError: org/apache/commons/dbcp/ConnectionFactory (Unsupported major.minor version 48.0) Hi Barry, this means that libcommons-dbcp-java was build without target=1.3 therefore it is not usable anymore with jdk1.3. Either you build tomcat with a jdk 1.4 or you rebuilt the libcommons-dbcp-java library with target=1.3. Wolfgang [...] Wolfgang, Thanks for the information. I was afraid it was something of that nature. Since Blackdown 1.3 and IBM 1.4 are what's available for PowerPC right now, I am not able to build this package without altering DBCP. The Tomcat 4 source requires the JDK to have some Sun security classes that IBM does not have. So, if Arnaud or Stefan could build tomcat4 with what I have checked in and sponsor an upload, we will likely have resolved this issue and gotten tomcat4 back into Sarge. 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) iD8DBQFCVmWzHuKcDICy0QoRAjIcAJ9QJlPeRrz0l6JIekpK4Wi9C6T75gCgthst XuBGY+z2TVWNaGDtAgv1O9g= =iGrN -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade
Barry Hawkins [EMAIL PROTECTED] writes: classes that IBM does not have. So, if Arnaud or Stefan could build tomcat4 with what I have checked in and sponsor an upload, we will likely have resolved this issue and gotten tomcat4 back into Sarge. I'm trying to do this but as amd64 port is missing some libraries (why, I have no idea) I'm having a slight difficulty with it. So, if Stefan/Arnaud beat me to it, feel free. Barry's changes looked fine to me and I tagged the HEAD already. -- * Sufficiently advanced magic is indistinguishable from technology (T.P) * * PGP public key available @ http://www.iki.fi/killer *
Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade
Kalle Kivimaa [EMAIL PROTECTED] writes: I'm trying to do this but as amd64 port is missing some libraries (why, I have no idea) I'm having a slight difficulty with it. So, if Stefan/Arnaud beat me to it, feel free. Barry's changes looked fine to me and I tagged the HEAD already. Oh well, I got the libraries installed from the i386 archive but building tomcat fails with the following: JAVA_HOME=/usr/local/jdk1.4.2 PATH=/usr/local/jdk1.4.2/bin:$PATH dpkg-buildpackage -uc -us -d -rfakeroot make[1]: Nothing to be done for `update-config'. make[1]: Leaving directory `/home/killer/src/tomcat4-4.1.31' rm -f debian/patches/*.log You must specify a valid JAVA_HOME or JAVACMD! make: *** [ant-sanity-check] Error 1 I give up. -- * Sufficiently advanced magic is indistinguishable from technology (T.P) * * PGP public key available @ http://www.iki.fi/killer *
Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade
On Thu, Apr 07, 2005 at 01:09:33AM -0400, Jeff Breidenbach wrote: The java packing team just got blindsided by bug #300209, which appears to have knocked tomcat4 out of Sarge. Heads up that you may hear some begging for re-inclusion in the near future. You mean there's no chance that people will actually fix the bug instead so that tomcat4 will get back in without begging? If the bug should actually be downgraded as has recently been suggested, then please downgrade it; the maintainers surely know better than the release team whether this bug has an inflated severity, but the report went three weeks before anyone commented on it -- maintainers need to be more responsive than that to RC bugs, even if it's just to explain why they're not RC. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade
On Wed, Apr 06, 2005 at 10:55:12PM -0400, Barry Hawkins wrote: Could you tell us which version of libcommons-collections-java you have installed on this machine? On my powerpc sid install, I currently have: I took a look into the offending line of source and noticed that a null value is pushed into a Digester. This is an explicit push (Digester.push(null)), not something that just happens to be null at the time. So, I would say that the actual culprit is the either the commons Digester or ArrayStack. -- * Outside of a dog, a book is man's best friend. Inside of a dog, it's * *too dark to read. (Groucho Marx) * * PGP public key available @ http://www.iki.fi/killer * -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade
On Wed, Apr 06, 2005 at 10:55:12PM -0400, Barry Hawkins wrote: Could you tell us which version of libcommons-collections-java you have installed on this machine? On my powerpc sid install, I currently have: Right, this problem is caused by the ArrayStack.java with the Jakarta CVS version 1.9 (and possible earlier). Collections release versions since 2.1 use version 1.10. So, we need a versioned dependency on libcommons-collections-java = 2.1-1. Unless somebody beats me to it, I'll do this some time today and will upload the new version, and also let the release team know that we would like Tomcat4 back in Sarge. -- * Outside of a dog, a book is man's best friend. Inside of a dog, it's * *too dark to read. (Groucho Marx) * * PGP public key available @ http://www.iki.fi/killer * -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade
Wolfgang Baer [EMAIL PROTECTED] writes: IMHO this bug can be closed as it is not related to a testing or unstable installation, nor a woody installation ! If you can end up with the problem using simply apt-get, then it is a real bug and needs to be fixed. I'm going to do it today, so if somebody violently disagrees with this, please give your reasons soon or roll back my change later (I'll just add the versioned dependency). A user _can_ choose to use some packages from the stable and some from the unstable. He can also choose to use some from an older version of stable. -- * Sufficiently advanced magic is indistinguishable from technology (T.P) * * PGP public key available @ http://www.iki.fi/killer *
Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade
Kalle Kivimaa wrote: Wolfgang Baer [EMAIL PROTECTED] writes: IMHO this bug can be closed as it is not related to a testing or unstable installation, nor a woody installation ! If you can end up with the problem using simply apt-get, then it is a real bug and needs to be fixed. I'm going to do it today, so if somebody violently disagrees with this, please give your reasons soon or roll back my change later (I'll just add the versioned dependency). No disagree - but shouldn't we then also add a versioned dependency to libcommons-digester-java (= 1.5.0.1-1). As we know from testing and unstable that these versions will work together ? Not that we end up with another RC bug due to an old libcommons-digester-java library. A user _can_ choose to use some packages from the stable and some from the unstable. He can also choose to use some from an older version of stable. OK ! Wolfgang -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade
Hi all, Wolfgang Baer schrieb: It seems as this is a mixed woody/testing/unstable/experimental installation. According to the System Information its woody 3.0 ! adduser is the woody version. apache-utils is the sarge version So this is not a bug in tomcat4 - just a mixed installation which seems to use a really old libcommons-collections-java version - maybe the old woody 1.0-1 version. As Killer said the problem is caused if the libcommons-collection-java version is 2.1 - but the version in testing and unstable is 2.1.1-3 can't happen also without a versioned dependency. Christoph pleasee send us your libcommons-collections-java version and also report back if you have a mixed woody/sarge environment. Yes, I have a mixed woody/sarge installation. But I tried to get all dependencies for tomcat4 from sarge. Since tomcat4 has no direct dependency on libcommons-collections-java, I did not check this one. I try to check now on my test machine if tomcat4 from unstable runs ok if I have the correct libcommons-collections-java versions. ... Sorry, but tomcat4 is still not running with libcommons-collections-java from testing. I also tried to update all packages with java in their names, but had no success. Here are the stati: ii java-common0.22 Base of all Java packages ii libant1.5-java 1.5.4-4Java based build tool like make ii libant1.6-java 1.6.2-2Java based build tool like make -- library ii libbcel-java 5.1-1 Analyze, create, and manipulate (binary) Jav ii libbsf-java2.3.0+cvs20050 Bean Scripting Framework to support scriptin ii libcommons-bea 1.6.1-4utility for manipulating JavaBeans ii libcommons-col 2.1.1-3A set of abstract data type interfaces and i ii libcommons-dbc 1.2.1-2Database Connection Pooling Services ii libcommons-dig 1.5.0.1-3 Rule based XML Java object mapping tool ii libcommons-fil 1.0-11 File upload capability to your servlets and ii libcommons-log 1.0.4-2The commmon wrapper interface for several lo ii libcommons-mod 1.1-1 A convenience library to use Java Management ii libcommons-poo 1.2-3 A set of objects that implement the pooling ii libjaxp1.2-jav 1.2.01-1 Java XML parser and transformer APIs (DOM, S ii liblog4j1.2-ja 1.2.9-1Logging library for java ii liblogkit-java 1.2.2-2Lightweight and fast designed logging toolki ii libmx4j-java 2.0.1-2An open source implementation of the JMX(TM) ii libregexp-java 1.3-1 regular expression library for Java ii libservlet2.3- 4.0-6 Servlet 2.3 and JSP 1.2 Java classes and doc ii libtomcat4-jav 4.1.31-2 Java Servlet engine -- core libraries ii libxalan-java 1.2.2-2Java version of the Xalan XSLT processor. ii libxalan2-java 2.6.0-1XSL Transformations (XSLT) processor in Java ii libxerces-java 1.4.4-2Validating XML parser for Java ii libxerces2-jav 2.6.2-1Validating XML parser for Java with DOM leve Christoph -- Christoph Martin, EDV der Verwaltung, Uni-Mainz, Germany Internet-Mail: [EMAIL PROTECTED] Telefon: +49-6131-3926337 Fax: +49-6131-3922856 signature.asc Description: OpenPGP digital signature
Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade
Christoph Martin schrieb: Hi. I just tested it on the other machines. After the update it is *working* on two more machines. So, I think this is fix. It is still *not* working on one other machine. I will investigate this special web application and its .jar files in WEB-INF/lib. Especially the file jars.jar looks supspicious for me. Ok. In jars.jar org/apache/commons/collections/ is included. Does someone know how I check the version in a .jar file? -- Christoph Martin, EDV der Verwaltung, Uni-Mainz, Germany Internet-Mail: [EMAIL PROTECTED] Telefon: +49-6131-3926337 Fax: +49-6131-3922856 signature.asc Description: OpenPGP digital signature
Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade
Christoph Martin [EMAIL PROTECTED] writes: Ok. In jars.jar org/apache/commons/collections/ is included. Does someone know how I check the version in a .jar file? That's a bit difficult unless the jar file contains either a well written META-INF file or a version file... I think you need to decompile the .class file and see what is in the method in question (the old version checks if the incoming parameter is null and if so it then throws a NPE - the new ones don't do that). -- * Sufficiently advanced magic is indistinguishable from technology (T.P) * * PGP public key available @ http://www.iki.fi/killer *
Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Steve Langasek wrote: On Thu, Apr 07, 2005 at 01:09:33AM -0400, Jeff Breidenbach wrote: The java packing team just got blindsided by bug #300209, which appears to have knocked tomcat4 out of Sarge. Heads up that you may hear some begging for re-inclusion in the near future. You mean there's no chance that people will actually fix the bug instead so that tomcat4 will get back in without begging? If the bug should actually be downgraded as has recently been suggested, then please downgrade it; the maintainers surely know better than the release team whether this bug has an inflated severity, but the report went three weeks before anyone commented on it -- maintainers need to be more responsive than that to RC bugs, even if it's just to explain why they're not RC. Steve, I apologize for not seeing this bug; I have been trying to pick up the slack on tomcat4 while Stefan and Arnaud have been snowed under with other things. We will indeed impose the appropriate runtime dependencies for the package and include that in the pending release. I started looking in Apache's documentation for the actual runtime version dependencies last night, since I would rather impose the correct versions and not just the ones we currently know that work. 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) iD8DBQFCVRYvHuKcDICy0QoRAqc9AJ9okOTtEVVn6Xc7xipqNDhPCfdihACeLYTQ PlM8hMRyyHk/OivXHR1+514= =DmPj -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade
Kalle Kivimaa schrieb: Christoph Martin [EMAIL PROTECTED] writes: Ok. In jars.jar org/apache/commons/collections/ is included. Does someone know how I check the version in a .jar file? That's a bit difficult unless the jar file contains either a well written META-INF file or a version file... I think you need to decompile the .class file and see what is in the method in question (the old version checks if the incoming parameter is null and if so it then throws a NPE - the new ones don't do that). I removed all the .jar files in the application and tomcat is still crashing. So I don't know what to check now to find the error. Any suggestions? Christoph -- Christoph Martin, EDV der Verwaltung, Uni-Mainz, Germany Internet-Mail: [EMAIL PROTECTED] Telefon: +49-6131-3926337 Fax: +49-6131-3922856 signature.asc Description: OpenPGP digital signature
Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christoph Martin wrote: [...] I removed all the .jar files in the application and tomcat is still crashing. So I don't know what to check now to find the error. Any suggestions? [...] How about: $ dpkg -l libcommons-collections-java That should work unless you have an additional commons-collections somewhere, but you seem to have removed those, right? 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) iD8DBQFCVVYtHuKcDICy0QoRAn3gAKDdHOQv7OonEtkyhI1Ve9EQpm2fBACgq1Mb k0DD0QeCnPbgdClAFIPUcrU= =WwjE -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade
Barry Hawkins schrieb: Christoph Martin wrote: [...] I removed all the .jar files in the application and tomcat is still crashing. So I don't know what to check now to find the error. Any suggestions? [...] How about: $ dpkg -l libcommons-collections-java That should work unless you have an additional commons-collections somewhere, but you seem to have removed those, right? As I already said, I checked that before looking for other locations. It even happens if I remove my webapp. Then it happens in the default context and in webdav etc. BTW.: Which version of java do you use with tomcat4? I use the 1.4 version from blackdown. May this be a problem? Christoph -- Christoph Martin, EDV der Verwaltung, Uni-Mainz, Germany Internet-Mail: [EMAIL PROTECTED] Telefon: +49-6131-3926337 Fax: +49-6131-3922856 signature.asc Description: OpenPGP digital signature
Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christoph Martin wrote: [...] As I already said, I checked that before looking for other locations. It even happens if I remove my webapp. Then it happens in the default context and in webdav etc. BTW.: Which version of java do you use with tomcat4? I use the 1.4 version from blackdown. May this be a problem? [...] I use the IBM JDK packaged by the java-package utility. If you could try the Sun 1.4 JDK package by java-package's make-jpkg utility, that might be a good idea. 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) iD8DBQFCVWmxHuKcDICy0QoRAs80AKDuotxka9Juyio9oLRLsT8XzJjzuACgqsyp VXEnJPAaXDFJV2uaT+oaNM0= =ZEOV -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wolfgang Baer wrote: Kalle Kivimaa wrote: Wolfgang Baer [EMAIL PROTECTED] writes: [...] If you can end up with the problem using simply apt-get, then it is a real bug and needs to be fixed. I'm going to do it today, so if somebody violently disagrees with this, please give your reasons soon or roll back my change later (I'll just add the versioned dependency). No disagree - but shouldn't we then also add a versioned dependency to libcommons-digester-java (= 1.5.0.1-1). As we know from testing and unstable that these versions will work together ? Not that we end up with another RC bug due to an old libcommons-digester-java library. A user _can_ choose to use some packages from the stable and some from the unstable. He can also choose to use some from an older version of stable. [...] Guys, I have committed a debian/control file for the tomcat4 package that imposes both build (tomcat4 source) and runtime(tomcat4 binary) dependencies the following library versions: libcommons-digester-java = 1.5.0.1 libcommons-collections-java = 2.1.1 libcommons-beanutils-java = 1.6.1 libcommons-logging-java = 1.0.4 This ensures that dependencies are satisfied for versions of the upstream libraries that are required by Tomat as well as one another, and ensures that the versions currently in testing are acceptable. If someone could please test this build on x86 and upload it, that would be great. I am out of town this week and it appears my DSL modem has locked up at home, preventing me from accessing my x86 box on which I normally build this. I tried to build with j2sdk1.3-blackdown/xmlParserAPIs.jar/xercesImpl.jar, but I get the commons-dbcp-related error shown at the bottom of this message. The package has built previously with the Sun 1.4 JDK packages generated by java-package without issue. $ debuild -ICVS -us -uc [...] BUILD FAILED /home/barryh/packages/tomcat4/tomcat4-4.1.31/build-tree/jakarta-tomcat-4.1.31-src/build.xml:67: The following error occurred while executing this line: java.lang.UnsupportedClassVersionError: org/apache/commons/dbcp/ConnectionFactory (Unsupported major.minor version 48.0) Thanks, - -- 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) iD8DBQFCVf3FHuKcDICy0QoRAmu2AJ0cUrdBmZvCbLc3BYWb/+Qfpq0YmACguRhc oODDR4wMb8oIzVc3YhDdhLc= =swye -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade
-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 VersionDescription +++-==-==- ii libcommons-col 2.1.1-3A 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- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Barry Hawkins wrote: [...] 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 VersionDescription +++-==-==- ii libcommons-col 2.1.1-3A set of abstract data type interfaces and i [...] One other thought regarding libraries; what libraries are in this particular web application's /WEB-INF/lib folder? Thanks, - -- 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) iD8DBQFCVKaxHuKcDICy0QoRAoiNAKDS+mUuBWEsB8w2JRcRSTaJKAyQbwCdEsZH 6V9aSAWBXTmVDKWAEyAnXns= =amNk -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade
Hi Sarge release team, The java packing team just got blindsided by bug #300209, which appears to have knocked tomcat4 out of Sarge. Heads up that you may hear some begging for re-inclusion in the near future. Jeff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#300209: tomcat4: tomcat dies with Parse error in default web.xml after upgrade
Package: tomcat4 Version: 4.1.31-2 Severity: grave Justification: renders package unusable I tried to update tomcat4 on different servers from 4.1.30 to 4.1.31. Now all my webapps are not running anymore. I get the following error and tomcat dies: 2005-03-18 11:52:46 ContextConfig[/hisqis/qisserver] Parse error in default web.xml java.lang.NullPointerException at org.apache.commons.collections.ArrayStack.push(ArrayStack.java:158) at org.apache.commons.digester.Digester.push(Digester.java:1628) at org.apache.catalina.startup.ContextConfig.defaultConfig(ContextConfig.java:488) and 2005-03-18 11:52:46 ContextConfig[/hisqis/qisserver] Parse error in application web.xml java.lang.NullPointerException at org.apache.commons.collections.ArrayStack.push(ArrayStack.java:158) at org.apache.commons.digester.Digester.push(Digester.java:1628) at org.apache.catalina.startup.ContextConfig.applicationConfig(ContextConfig.java:221) 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 -- System Information: Debian Release: 3.0 APT prefers testing APT policy: (99, 'testing'), (50, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.4.27-2-686-smp Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages tomcat4 depends on: ii adduser 3.47 Add and remove users and groups ii apache-utils 1.3.33-4 utility programs for webservers (t ii apache2-utils [apache-uti 2.0.53-5 utility programs for webservers ii j2re1.4 [java-virtual-mac 1.4.1.99.rc1-1 Blackdown Java(TM) 2 Runtime Envir ii j2sdk1.4 [java-compiler] 1.4.1.99.rc1-1 Blackdown Java(TM) 2 SDK, Standard ii libtomcat4-java 4.1.31-2 Java Servlet engine -- core librar -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
