Magnolia

getting SAXParserException during bootsrap

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 2.1 Final
  • Component/s: None
  • Security Level: Public
  • Labels:
  • Description:
    Hide

    INFO info.magnolia.cms.beans.config.ConfigLoader ConfigLoader.java(bootstrapRepositories:269) 04.05.2005 23:33:10 Trying to import content from 1 files...
    ERROR info.magnolia.cms.beans.config.ConfigLoader ConfigLoader.java(bootstrapRepositories:293) 04.05.2005 23:33:10 Unable to load content from website.features.xml due to a org.xml.sax.SAXParseException Exception: can't declare any more prefixes in this context. Will try to continue.
    java.lang.IllegalStateException: can't declare any more prefixes in this context
    at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:691)
    at org.apache.crimson.parser.Parser2.parse(Parser2.java:337)
    at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448)
    at org.xml.sax.helpers.XMLFilterImpl.parse(Unknown Source)
    at info.magnolia.cms.beans.config.ConfigLoader.filterVersionsFormStream(ConfigLoader.java:350)
    at info.magnolia.cms.beans.config.ConfigLoader.bootstrapRepositories(ConfigLoader.java:287)
    at info.magnolia.cms.beans.config.ConfigLoader.load(ConfigLoader.java:131)
    at info.magnolia.cms.beans.config.ConfigLoader.<init>(ConfigLoader.java:91)
    at info.magnolia.cms.servlets.Initializer.init(Initializer.java:54)

    Show
    INFO info.magnolia.cms.beans.config.ConfigLoader ConfigLoader.java(bootstrapRepositories:269) 04.05.2005 23:33:10 Trying to import content from 1 files... ERROR info.magnolia.cms.beans.config.ConfigLoader ConfigLoader.java(bootstrapRepositories:293) 04.05.2005 23:33:10 Unable to load content from website.features.xml due to a org.xml.sax.SAXParseException Exception: can't declare any more prefixes in this context. Will try to continue. java.lang.IllegalStateException: can't declare any more prefixes in this context at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:691) at org.apache.crimson.parser.Parser2.parse(Parser2.java:337) at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448) at org.xml.sax.helpers.XMLFilterImpl.parse(Unknown Source) at info.magnolia.cms.beans.config.ConfigLoader.filterVersionsFormStream(ConfigLoader.java:350) at info.magnolia.cms.beans.config.ConfigLoader.bootstrapRepositories(ConfigLoader.java:287) at info.magnolia.cms.beans.config.ConfigLoader.load(ConfigLoader.java:131) at info.magnolia.cms.beans.config.ConfigLoader.<init>(ConfigLoader.java:91) at info.magnolia.cms.servlets.Initializer.init(Initializer.java:54)

Activity

Hide
Fabrizio Giustina added a comment - 05/May/05 5:29 PM

Hi Philipp, are you getting this errors with the xml actually on svn or with a new export? Does the BootStrapTest junit log the same error?

Show
Fabrizio Giustina added a comment - 05/May/05 5:29 PM Hi Philipp, are you getting this errors with the xml actually on svn or with a new export? Does the BootStrapTest junit log the same error?
Hide
Philipp Bracher [old account - now Philipp Bärfuss] added a comment - 06/May/05 8:52 AM

I get no error during testing (maven), but i get them during loading the server (i tested it also with magnolia.war).

I have updated my svn workdir and not generated new export files (i use those from svn).

But i got this problem on two different maschines (mac osx and suse linux).

The question is: what is the difference between junit and runtime bootstraping?

Show
Philipp Bracher [old account - now Philipp Bärfuss] added a comment - 06/May/05 8:52 AM I get no error during testing (maven), but i get them during loading the server (i tested it also with magnolia.war). I have updated my svn workdir and not generated new export files (i use those from svn). But i got this problem on two different maschines (mac osx and suse linux). The question is: what is the difference between junit and runtime bootstraping?
Hide
Fabrizio Giustina added a comment - 06/May/05 9:19 AM

this seems to be a conflict when different xml parsers (xerces/crimson) are in the classpath. I see you appserver is using crimson, I will try to force the use of xerces and see if it could help...

Here you can find the result of testing different parsers posted by someone who has the same problem in tomcat (bottom of the page):
http://www.forum4designers.com/message217680.html

Show
Fabrizio Giustina added a comment - 06/May/05 9:19 AM this seems to be a conflict when different xml parsers (xerces/crimson) are in the classpath. I see you appserver is using crimson, I will try to force the use of xerces and see if it could help... Here you can find the result of testing different parsers posted by someone who has the same problem in tomcat (bottom of the page): http://www.forum4designers.com/message217680.html
Hide
Fabrizio Giustina added a comment - 06/May/05 9:26 AM

done, please give it a try and see if it works

Show
Fabrizio Giustina added a comment - 06/May/05 9:26 AM done, please give it a try and see if it works
Hide
Philipp Bracher [old account - now Philipp Bärfuss] added a comment - 06/May/05 9:42 AM

org.apache.xerces.parsers.SAXParser is working!

Thanks

Show
Philipp Bracher [old account - now Philipp Bärfuss] added a comment - 06/May/05 9:42 AM org.apache.xerces.parsers.SAXParser is working! Thanks

People

Dates

  • Created:
    04/May/05 11:37 PM
    Updated:
    17/Mar/09 7:49 PM
    Resolved:
    06/May/05 9:42 AM