You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Satish Kumar <sa...@gmail.com> on 2010/12/26 20:44:54 UTC
processing of tlds failed -- application still works -- why?
Hi All,
I am seeing the error below while deploying a web application on Tomcat
6.0.16. Note that the parser used for processing tlds is Crimson -- I expect
Tomcat to use the default Xerces parser to process tlds, but it using
Crimson parser that is in a jar in WEB-INF/lib. It seems this issue is
related to bug 29936 fixed in 6.0.17:
https://issues.apache.org/bugzilla/show_bug.cgi?id=29936 . I don't see this
error on Tomcat 6.0.18.
Question: My application works fine. The custom tags defined in the tld the
parsing failed on still work. Why do the custom tags work when tld parsing
failed? Can this error be ignored? What is the purpose of method
processTlds? (to create tld cache?)
Ref:
http://tomcat.apache.org/tomcat-5.5-doc/config/context.html#Standard_Implementation
What happens if I set processTlds context attribute to false while tlds are
used in the webapp?
ERROR [main] (Digester.java:1555) - Parse Fatal Error at line 1 column -1:
Relative URI "web-jsptaglib_1_1.dtd"; can not be resolved without a base
URI.
org.xml.sax.SAXParseException: Relative URI "web-jsptaglib_1_1.dtd"; can not
be resolved without a base URI.
at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3182)
at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3176)
at org.apache.crimson.parser.Parser2.resolveURI(Parser2.java:2758)
at
org.apache.crimson.parser.Parser2.maybeExternalID(Parser2.java:2730)
at
org.apache.crimson.parser.Parser2.maybeDoctypeDecl(Parser2.java:1129)
at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:489)
at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)
at
org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:442)
at
org.apache.tomcat.util.digester.Digester.parse(Digester.java:1644)
at
org.apache.catalina.startup.TldConfig.tldScanStream(TldConfig.java:518)
at
org.apache.catalina.startup.TldConfig.tldScanTld(TldConfig.java:555)
at org.apache.catalina.startup.TldConfig.execute(TldConfig.java:295)
at
org.apache.catalina.core.StandardContext.processTlds(StandardContext.java:4441)
Thanks!
Satish
Re: processing of tlds failed -- application still works -- why?
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Satish,
On 12/28/2010 9:54 AM, Satish Kumar wrote:
>>> So, you are using an older version of Tomcat which contains a bug which
>>> you acknowledge is now fixed?
>
> I don't know the details but I was told that there were some application
> issues (I guess it is related to cookies) when the app was deployed on newer
> version. Also, for a Tomcat upgrade QA team needs to verify other
> applications deployed on the same Tomcat; this is something our project
> manager doesn't want to add to scope now.
>
> Just for my understanding, could you please tell why tlds are processed at
> start up and if application still works even when the processing fails?
Maybe it was a bug. Just sayin'
- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk0aqPsACgkQ9CaO5/Lv0PCbbQCfUUl92/qEeamgbixXN2XZwSWU
jQAAnA7C9pjSy/0WHl2QGlY3vi3FaAzD
=GCZB
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: processing of tlds failed -- application still works -- why?
Posted by Satish Kumar <sa...@gmail.com>.
>>So, you are using an older version of Tomcat which contains a bug which
>>you acknowledge is now fixed?
I don't know the details but I was told that there were some application
issues (I guess it is related to cookies) when the app was deployed on newer
version. Also, for a Tomcat upgrade QA team needs to verify other
applications deployed on the same Tomcat; this is something our project
manager doesn't want to add to scope now.
Just for my understanding, could you please tell why tlds are processed at
start up and if application still works even when the processing fails?
thanks!
On Tue, Dec 28, 2010 at 8:36 AM, Pid <pi...@pidster.com> wrote:
> On 12/26/10 7:44 PM, Satish Kumar wrote:
> > Hi All,
> >
> > I am seeing the error below while deploying a web application on Tomcat
> > 6.0.16. Note that the parser used for processing tlds is Crimson -- I
> expect
> > Tomcat to use the default Xerces parser to process tlds, but it using
> > Crimson parser that is in a jar in WEB-INF/lib. It seems this issue is
> > related to bug 29936 fixed in 6.0.17:
> > https://issues.apache.org/bugzilla/show_bug.cgi?id=29936 . I don't see
> this
> > error on Tomcat 6.0.18.
>
> So, you are using an older version of Tomcat which contains a bug which
> you acknowledge is now fixed?
>
> Why not upgrade to the latest 6.0.29?
>
>
> p
>
> > Question: My application works fine. The custom tags defined in the tld
> the
> > parsing failed on still work. Why do the custom tags work when tld
> parsing
> > failed? Can this error be ignored? What is the purpose of method
> > processTlds? (to create tld cache?)
> >
> > Ref:
> >
> http://tomcat.apache.org/tomcat-5.5-doc/config/context.html#Standard_Implementation
> > What happens if I set processTlds context attribute to false while tlds
> are
> > used in the webapp?
> >
> >
> > ERROR [main] (Digester.java:1555) - Parse Fatal Error at line 1 column
> -1:
> > Relative URI "web-jsptaglib_1_1.dtd"; can not be resolved without a base
> > URI.
> > org.xml.sax.SAXParseException: Relative URI "web-jsptaglib_1_1.dtd"; can
> not
> > be resolved without a base URI.
> > at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3182)
> > at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3176)
> > at
> org.apache.crimson.parser.Parser2.resolveURI(Parser2.java:2758)
> > at
> > org.apache.crimson.parser.Parser2.maybeExternalID(Parser2.java:2730)
> > at
> > org.apache.crimson.parser.Parser2.maybeDoctypeDecl(Parser2.java:1129)
> > at
> org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:489)
> > at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)
> > at
> > org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:442)
> > at
> > org.apache.tomcat.util.digester.Digester.parse(Digester.java:1644)
> > at
> > org.apache.catalina.startup.TldConfig.tldScanStream(TldConfig.java:518)
> > at
> > org.apache.catalina.startup.TldConfig.tldScanTld(TldConfig.java:555)
> > at
> org.apache.catalina.startup.TldConfig.execute(TldConfig.java:295)
> > at
> >
> org.apache.catalina.core.StandardContext.processTlds(StandardContext.java:4441)
> >
> >
> > Thanks!
> >
> > Satish
> >
>
>
Re: processing of tlds failed -- application still works -- why?
Posted by Pid <pi...@pidster.com>.
On 12/26/10 7:44 PM, Satish Kumar wrote:
> Hi All,
>
> I am seeing the error below while deploying a web application on Tomcat
> 6.0.16. Note that the parser used for processing tlds is Crimson -- I expect
> Tomcat to use the default Xerces parser to process tlds, but it using
> Crimson parser that is in a jar in WEB-INF/lib. It seems this issue is
> related to bug 29936 fixed in 6.0.17:
> https://issues.apache.org/bugzilla/show_bug.cgi?id=29936 . I don't see this
> error on Tomcat 6.0.18.
So, you are using an older version of Tomcat which contains a bug which
you acknowledge is now fixed?
Why not upgrade to the latest 6.0.29?
p
> Question: My application works fine. The custom tags defined in the tld the
> parsing failed on still work. Why do the custom tags work when tld parsing
> failed? Can this error be ignored? What is the purpose of method
> processTlds? (to create tld cache?)
>
> Ref:
> http://tomcat.apache.org/tomcat-5.5-doc/config/context.html#Standard_Implementation
> What happens if I set processTlds context attribute to false while tlds are
> used in the webapp?
>
>
> ERROR [main] (Digester.java:1555) - Parse Fatal Error at line 1 column -1:
> Relative URI "web-jsptaglib_1_1.dtd"; can not be resolved without a base
> URI.
> org.xml.sax.SAXParseException: Relative URI "web-jsptaglib_1_1.dtd"; can not
> be resolved without a base URI.
> at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3182)
> at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3176)
> at org.apache.crimson.parser.Parser2.resolveURI(Parser2.java:2758)
> at
> org.apache.crimson.parser.Parser2.maybeExternalID(Parser2.java:2730)
> at
> org.apache.crimson.parser.Parser2.maybeDoctypeDecl(Parser2.java:1129)
> at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:489)
> at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)
> at
> org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:442)
> at
> org.apache.tomcat.util.digester.Digester.parse(Digester.java:1644)
> at
> org.apache.catalina.startup.TldConfig.tldScanStream(TldConfig.java:518)
> at
> org.apache.catalina.startup.TldConfig.tldScanTld(TldConfig.java:555)
> at org.apache.catalina.startup.TldConfig.execute(TldConfig.java:295)
> at
> org.apache.catalina.core.StandardContext.processTlds(StandardContext.java:4441)
>
>
> Thanks!
>
> Satish
>