You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by George Payne <gp...@virginia.edu> on 2008/02/01 02:09:24 UTC

Upgrading to 5.5.25 causes File /javax/servlet/resources/web-app_2_3.dtd not found

I upgraded from 5.5.20-->5.5.25 (RH linux) by copying new jars to 
/common/lib and /server/lib

I then got these errors.  Is this a bug in 5.5.25, or some sort of 
problem with my upgrade method?

I'm now back to 5.5.20 jars and working fine again, but I'd like to upgrade.

Any suggestions?  Where is this dtd supposed to be?

Thanks. 


SEVERE: Servlet.service() for servlet jsp threw exception
org.xml.sax.SAXException: Internal Error: File 
/javax/servlet/resources/web-app_2_3.dtd not found
        at 
org.apache.jasper.xmlparser.MyEntityResolver.resolveEntity(ParserUtils.java:205)
        at 
com.sun.org.apache.xerces.internal.util.EntityResolverWrapper.resolveEntity(EntityResolverWrapper.java:148)
        at 
com.sun.org.apache.xerces.internal.impl.XMLEntityManager.resolveEntity(XMLEntityManager.java:701)
        at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(XMLDocumentScannerImpl.java:1019)
        at 
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:3
68)
        at 
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
        at 
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
        at 
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
        at 
com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:250)
        at 
com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
        at 
org.apache.jasper.xmlparser.ParserUtils.parseXMLDocument(ParserUtils.java:95)
        at 
org.apache.jasper.compiler.JspConfig.processWebDotXml(JspConfig.java:76)
        at org.apache.jasper.compiler.JspConfig.init(JspConfig.java:197)
        at 
org.apache.jasper.compiler.JspConfig.findJspProperty(JspConfig.java:249)
        at 
org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:112)
        at org.apache.jasper.compiler.Compiler.compile(Compiler.java:295)
        at org.apache.jasper.compiler.Compiler.compile(Compiler.java:276)
        at org.apache.jasper.compiler.Compiler.compile(Compiler.java:264)
        at 
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:563)
        at 
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:305)
        at 
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
        at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
        at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
        at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
        at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
        at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
        at 
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524)
        at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
        at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
        at 
org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:392)
        at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
        at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
        at 
org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:199)
        at 
org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282)
        at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767)
        at 
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:697)
        at 
org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:889)
        at 
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
        at java.lang.Thread.run(Thread.java:595)

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: Upgrading to 5.5.25 causes File /javax/servlet/resources/web-app_2_3.dtd not found

Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: Martin Gainty [mailto:mgainty@hotmail.com] 
> Subject: Re: Upgrading to 5.5.25 causes File 
> /javax/servlet/resources/web-app_2_3.dtd not found
> 
> TC 5.5.25 servlet spec jumped to Servlet Spec 2.4/ JSP Spec 2.0

That jump was from 5.0.x to 5.5.x, not 5.5.20 to 5.5.25.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: Upgrading to 5.5.25 causes File /javax/servlet/resources/web-app_2_3.dtd not found

Posted by Martin Gainty <mg...@hotmail.com>.
TC 5.5.25 servlet spec jumped to Servlet Spec 2.4/ JSP Spec 2.0
I dont think you can upgrade by copying in some of the  jars in that way and
would suggest a fresh install

M
----- Original Message -----
From: "George Payne" <gp...@virginia.edu>
To: "Tomcat Users List" <us...@tomcat.apache.org>
Sent: Thursday, January 31, 2008 8:09 PM
Subject: Upgrading to 5.5.25 causes File
/javax/servlet/resources/web-app_2_3.dtd not found


> I upgraded from 5.5.20-->5.5.25 (RH linux) by copying new jars to
> /common/lib and /server/lib
>
> I then got these errors.  Is this a bug in 5.5.25, or some sort of
> problem with my upgrade method?
>
> I'm now back to 5.5.20 jars and working fine again, but I'd like to
upgrade.
>
> Any suggestions?  Where is this dtd supposed to be?
>
> Thanks.
>
>
> SEVERE: Servlet.service() for servlet jsp threw exception
> org.xml.sax.SAXException: Internal Error: File
> /javax/servlet/resources/web-app_2_3.dtd not found
>         at
>
org.apache.jasper.xmlparser.MyEntityResolver.resolveEntity(ParserUtils.java:
205)
>         at
>
com.sun.org.apache.xerces.internal.util.EntityResolverWrapper.resolveEntity(
EntityResolverWrapper.java:148)
>         at
>
com.sun.org.apache.xerces.internal.impl.XMLEntityManager.resolveEntity(XMLEn
tityManager.java:701)
>         at
>
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDispatcher
dispatch(XMLDocumentScannerImpl.java:1019)
>         at
>
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanD
ocument(XMLDocumentFragmentScannerImpl.java:3
> 68)
>         at
>
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Con
figuration.java:834)
>         at
>
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Con
figuration.java:764)
>         at
>
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:14
8)
>         at
>
com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:25
0)
>         at
>
com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBu
ilderImpl.java:292)
>         at
>
org.apache.jasper.xmlparser.ParserUtils.parseXMLDocument(ParserUtils.java:95
)
>         at
> org.apache.jasper.compiler.JspConfig.processWebDotXml(JspConfig.java:76)
>         at org.apache.jasper.compiler.JspConfig.init(JspConfig.java:197)
>         at
> org.apache.jasper.compiler.JspConfig.findJspProperty(JspConfig.java:249)
>         at
> org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:112)
>         at org.apache.jasper.compiler.Compiler.compile(Compiler.java:295)
>         at org.apache.jasper.compiler.Compiler.compile(Compiler.java:276)
>         at org.apache.jasper.compiler.Compiler.compile(Compiler.java:264)
>         at
>
org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:5
63)
>         at
>
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:3
05)
>         at
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
>         at
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>         at
>
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:252)
>         at
>
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:173)
>         at
>
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
va:213)
>         at
>
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
va:178)
>         at
>
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase
java:524)
>         at
>
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126
)
>         at
>
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105
)
>         at
>
org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:392)
>         at
>
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:107)
>         at
>
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
>         at
> org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:199)
>         at
> org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282)
>         at
org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767)
>         at
>
org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:697)
>         at
>
org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java
:889)
>         at
>
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav
a:684)
>         at java.lang.Thread.run(Thread.java:595)
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: Upgrading to 5.5.25 web-app_2_3.dtd not found--thanks to all

Posted by David Smith <dn...@cornell.edu>.
Your method of jar replacement would have worked better if you were 
doing a point upgrade paying attention to the third number, keeping the 
first two the same.  For example, upgrading from 5.5.16 to 5.5.25 is a 
reasonably safe upgrade without significant breaking changes.  At worst, 
such an upgrade may fix an error your webapp was depending on and then 
the webapp breaks -- it's happened before. :-) 

5.0.x to 5.5.25 is a bit more significant with a lot of internal 
refactoring and some breaking changes in how context .xml files and 
resource definitions are handled.  Think of the 5.0.x to 5.5.x migration 
in the same manner you'd think of a 5.x.x upgrade to 6.x.x.

--David

George Payne wrote:

>Just wanted to say thanks very much for all the very helpful replies on
>this.
>
>I now have several avenues to pursue and I assume now that the problem was
>my upgrade method, and not a bug in 5.5.25.
>
>There is a general issue this brings up--not really a question anymore, just
>a point to ponder (for anyone who just likes pondering :)), which is what
>the best way to do security upgrades on tomcat on linux is.
>
>The problem is, for the security conscious, how to practically keep up with
>minor revisions of tomcat which may contain security enhancements we
>shouldn't really be operating without.
>
>This could be cast as a "laziness" problem, but really, for busy admins,
>doing manual point upgrades for lots of apps on lots of machines can be a
>very time-consuming task.  I think most of us maintain sanity by skipping a
>lot of them, which is not the safest route.  Some distros are starting to
>have workable update schemes (EL5 has a good but complex system, though it's
>been a bit buggy for me), but this is at the distro level.  I suspect there
>are general-purpose things already out there--scripts, etc?
>
>
>
>-----Original Message-----
>From: Konstantin Kolinko [mailto:knst.kolinko@gmail.com] 
>Sent: Friday, February 01, 2008 9:11 AM
>To: Tomcat Users List
>Subject: Re: Upgrading to 5.5.25 causes File
>/javax/servlet/resources/web-app_2_3.dtd not found
>
>The file /javax/servlet/resources/web-app_2_3.dtd is in
>servlet-api.jar in common/lib, both in 5.5.25 and 5.5.20.
>
>---------------------------------------------------------------------
>To start a new topic, e-mail: users@tomcat.apache.org
>To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>---------------------------------------------------------------------
>To start a new topic, e-mail: users@tomcat.apache.org
>To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>For additional commands, e-mail: users-help@tomcat.apache.org
>
>  
>


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: Upgrading to 5.5.25 web-app_2_3.dtd not found--thanks to all

Posted by George Payne <gp...@virginia.edu>.
Just wanted to say thanks very much for all the very helpful replies on
this.

I now have several avenues to pursue and I assume now that the problem was
my upgrade method, and not a bug in 5.5.25.

There is a general issue this brings up--not really a question anymore, just
a point to ponder (for anyone who just likes pondering :)), which is what
the best way to do security upgrades on tomcat on linux is.

The problem is, for the security conscious, how to practically keep up with
minor revisions of tomcat which may contain security enhancements we
shouldn't really be operating without.

This could be cast as a "laziness" problem, but really, for busy admins,
doing manual point upgrades for lots of apps on lots of machines can be a
very time-consuming task.  I think most of us maintain sanity by skipping a
lot of them, which is not the safest route.  Some distros are starting to
have workable update schemes (EL5 has a good but complex system, though it's
been a bit buggy for me), but this is at the distro level.  I suspect there
are general-purpose things already out there--scripts, etc?



-----Original Message-----
From: Konstantin Kolinko [mailto:knst.kolinko@gmail.com] 
Sent: Friday, February 01, 2008 9:11 AM
To: Tomcat Users List
Subject: Re: Upgrading to 5.5.25 causes File
/javax/servlet/resources/web-app_2_3.dtd not found

The file /javax/servlet/resources/web-app_2_3.dtd is in
servlet-api.jar in common/lib, both in 5.5.25 and 5.5.20.

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: Upgrading to 5.5.25 causes File /javax/servlet/resources/web-app_2_3.dtd not found

Posted by Konstantin Kolinko <kn...@gmail.com>.
The file /javax/servlet/resources/web-app_2_3.dtd is in
servlet-api.jar in common/lib, both in 5.5.25 and 5.5.20.

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: Upgrading to 5.5.25 causes File /javax/servlet/resources/web-app_2_3.dtd not found

Posted by David Smith <dn...@cornell.edu>.
The jars in server/lib and common/lib aren't the only jars important to 
tomcat.  Also look at the jars in the bin directory and take care to 
remove older jars that have the same classes as the 5.5 release.  It 
might work to upgrade this way if you do a more thorough replacement.  
Also I believe you have to also alter the way resources are defined in 
your webapps when moving from tomcat 5.0 to 5.5.

My personal recommendation would be to do a normal install in a parallel 
directory, copy the config files, altering port numbers so you can test 
before switching over.  When you are ready and everything has been 
tested, reconfigure the port numbers in the new tomcat to match 
production, move webapps over, drop the old production tomcat and start 
the new one.

--David

George Payne wrote:

> I upgraded from 5.5.20-->5.5.25 (RH linux) by copying new jars to 
> /common/lib and /server/lib
>
> I then got these errors.  Is this a bug in 5.5.25, or some sort of 
> problem with my upgrade method?
>
> I'm now back to 5.5.20 jars and working fine again, but I'd like to 
> upgrade.
>
> Any suggestions?  Where is this dtd supposed to be?
>
> Thanks.
>
> SEVERE: Servlet.service() for servlet jsp threw exception
> org.xml.sax.SAXException: Internal Error: File 
> /javax/servlet/resources/web-app_2_3.dtd not found
>        at 
> org.apache.jasper.xmlparser.MyEntityResolver.resolveEntity(ParserUtils.java:205) 
>
>        at 
> com.sun.org.apache.xerces.internal.util.EntityResolverWrapper.resolveEntity(EntityResolverWrapper.java:148) 
>
>        at 
> com.sun.org.apache.xerces.internal.impl.XMLEntityManager.resolveEntity(XMLEntityManager.java:701) 
>
>        at 
> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(XMLDocumentScannerImpl.java:1019) 
>
>        at 
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:3 
>
> 68)
>        at 
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834) 
>
>        at 
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764) 
>
>        at 
> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148) 
>
>        at 
> com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:250) 
>
>        at 
> com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292) 
>
>        at 
> org.apache.jasper.xmlparser.ParserUtils.parseXMLDocument(ParserUtils.java:95) 
>
>        at 
> org.apache.jasper.compiler.JspConfig.processWebDotXml(JspConfig.java:76)
>        at org.apache.jasper.compiler.JspConfig.init(JspConfig.java:197)
>        at 
> org.apache.jasper.compiler.JspConfig.findJspProperty(JspConfig.java:249)
>        at 
> org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:112)
>        at org.apache.jasper.compiler.Compiler.compile(Compiler.java:295)
>        at org.apache.jasper.compiler.Compiler.compile(Compiler.java:276)
>        at org.apache.jasper.compiler.Compiler.compile(Compiler.java:264)
>        at 
> org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:563) 
>
>        at 
> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:305) 
>
>        at 
> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
>        at 
> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
>        at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>        at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) 
>
>        at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) 
>
>        at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) 
>
>        at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) 
>
>        at 
> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:524) 
>
>        at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) 
>
>        at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) 
>
>        at 
> org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:392) 
>
>        at 
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) 
>
>        at 
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) 
>
>        at 
> org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:199)
>        at 
> org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:282)
>        at 
> org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:767)
>        at 
> org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:697) 
>
>        at 
> org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.java:889) 
>
>        at 
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) 
>
>        at java.lang.Thread.run(Thread.java:595)
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


RE: Upgrading to 5.5.25 causes File /javax/servlet/resources/web-app_2_3.dtdnotfound

Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: George Payne [mailto:gpayne@virginia.edu] 
> Subject: Re: Upgrading to 5.5.25 causes File 
> /javax/servlet/resources/web-app_2_3.dtdnotfound
> 
> Well, I guess part of my question is: what does that mean?

We get many questions from people who try to use 3rd-party, repackaged
versions of Tomcat, with varying degrees of failure.  Trying to make
sure you weren't in that category.

> I downloaded the 5.5.25 binary tar and used all the
> latest jar files from it.

That's good, but you run a serious risk of missing jars or other things
that might have changed.

> I assume you mean untarring, symlinking, and copying 
> over webapps and server.xml

The symlinking can be causing some "interesting" behavior if it's not
done carefully and configured where needed in Tomcat.  Copying over
server.xml is certainly not recommended; updating the one that comes
with 5.5.25 for your environment is.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Re: Upgrading to 5.5.25 causes File /javax/servlet/resources/web-app_2_3.dtdnot found

Posted by George Payne <gp...@virginia.edu>.
Well, I guess part of my question is: what does that mean?

I downloaded the 5.5.25 binary tar and used all the latest jar files 
from it.

If no one else has seen this problem, I'll try a "real" install--by 
which I assume you mean untarring, symlinking, and copying over webapps 
and server.xml, but I had assumed this would not be very different from 
what I did.

Caldarale, Charles R wrote:
>> From: George Payne [mailto:gpayne@virginia.edu] 
>> Subject: Upgrading to 5.5.25 causes File 
>> /javax/servlet/resources/web-app_2_3.dtdnot found
>>
>> I upgraded from 5.5.20-->5.5.25 (RH linux) by copying new jars to 
>> /common/lib and /server/lib
>>     
>
> And what happens if you do a real install of a real Tomcat download?
>
>  - Chuck
>
>
> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
> MATERIAL and is thus for use only by the intended recipient. If you
> received this in error, please contact the sender and delete the e-mail
> and its attachments from all computers.
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>   


RE: Upgrading to 5.5.25 causes File /javax/servlet/resources/web-app_2_3.dtdnot found

Posted by "Caldarale, Charles R" <Ch...@unisys.com>.
> From: George Payne [mailto:gpayne@virginia.edu] 
> Subject: Upgrading to 5.5.25 causes File 
> /javax/servlet/resources/web-app_2_3.dtdnot found
> 
> I upgraded from 5.5.20-->5.5.25 (RH linux) by copying new jars to 
> /common/lib and /server/lib

And what happens if you do a real install of a real Tomcat download?

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org