tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 18626] New: - Digester errors on startup should report filename
Date Wed, 02 Apr 2003 20:37:04 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18626>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18626

Digester errors on startup should report filename

           Summary: Digester errors on startup should report filename
           Product: Tomcat 4
           Version: 4.1.24
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: alex@apache.org


At startup, catalina.out can report Digester errors involving XML parsing. Unfortunately,

these errors do not tell which file contained the errors! This makes tracking down the 
error very difficult, especially on a system containing many webapps.

For example, I recently got the following:

Mar 30, 2003 3:03:39 PM org.apache.commons.modeler.Registry loadRegistry
INFO: Loading registry information
Mar 30, 2003 3:03:44 PM org.apache.commons.modeler.Registry getRegistry
INFO: Creating new Registry instance
Mar 30, 2003 3:04:08 PM org.apache.commons.modeler.Registry getServer
INFO: Creating MBeanServer
Mar 30, 2003 3:04:39 PM org.apache.commons.digester.Digester fatalError
SEVERE: Parse Fatal Error at line 220 column -1: Next character must be ">" terminating

comment .
org.xml.sax.SAXParseException: Next character must be ">" terminating comment .
        at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3182)
        at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3176)
[...]
        at org.apache.commons.digester.Digester.parse(Digester.java:1543)
        at org.apache.catalina.startup.Catalina.start(Catalina.java:449)
        at org.apache.catalina.startup.Catalina.execute(Catalina.java:400)
        at org.apache.catalina.startup.Catalina.process(Catalina.java:180)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
25)
        at java.lang.reflect.Method.invoke(Method.java:324)
        at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203)
Catalina.start: org.xml.sax.SAXParseException: Next character must be ">" terminating 
comment .
org.xml.sax.SAXParseException: Next character must be ">" terminating comment .
        at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3182)
        at org.apache.crimson.parser.Parser2.fatal(Parser2.java:3176)
[...]

I haven't tracked it down yet, but there's obviously a syntax error in an XML file 
somewhere, possibly a web.xml file that is no longer valid (but was parsed OK by an 
earlier, less stringent version of Digester or of the XML parser now used by Tomcat 
4.1.24).

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message