DO NOT REPLY [Bug 9603] New: - damaged systemid string given to entity resolver

[bu...@apache.org]

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=9603>.
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=9603

damaged systemid string given to entity resolver

           Summary: damaged systemid string given to entity resolver
           Product: Xerces-J
           Version: 1.4.3
          Platform: Sun
        OS/Version: Solaris
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Core
        AssignedTo: xerces-j-dev@xml.apache.org
        ReportedBy: apel-apache@tivano.de


xerces 1.4.3
jdk 1.3.1_01

we are using xerces as part of a webapp.
works fine most of the time ( 6 months online )
but sometimes ( happened only about 3 times )
our custom entity resolver gets a damaged systemid 
from xerces, while this was parsing the doctype decl. 
of an xml-file.

before this happens, the same xml got parsed correctly.

by restarting the application, this behaviour vanishes.

things happen, while we are in DOMParser parser.parse()
(maybe this should belong to component DOM instead of Core)

thats the start of an xml file:

<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE config SYSTEM "modules.dtd">

if that bug occurs, this is what our custom 
entity resolver logs, then immediately, the error,
which happens because the resolver can't resolve
the damaged systemid and so xerces can't find the 
dtd-file:

<2002-06-03 14:48:17,427> <1117362628> <Server  WebApp> [DEBUG] <Import> 
    tivanoEntityResolver.resolveEntity() invoked for 
         publicId: null
         systemId:  "modules.d
<2002-06-03 14:48:17,428> <1117362629> <Server  WebApp> [ERROR] <Import>  SAX
Parsing 
Fatal Error: 
    Line: 0 in URI: file:////tivano/import/config/modules.xml
    Message: File " "modules.d" not found.

in a similar case, the damaged system id is "M "fitforfun"
the first two lines of the corresponding xml file being
   
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!DOCTYPE content SYSTEM "fitforfun.dtd">

( watch the M of SYSTEM )

last time that happened, we modified the xml file:

<?xml version="1.0" encoding="UTF-8" ?><!DOCTYPE config SYSTEM "modules.dtd">

this resulted in a different error

java.lang.RuntimeException: addSymbolToCache
        at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1094)
        at org.apache.xerces.framework.XMLParser.parse(XMLParser.java:1122)
        at de.tivano.ImportConfig.getDoc(ImportConfig.java:500)
...

while the app was still running, both kind of errors were
reproducible, after a restart the bug dissappeared again

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org