org.xml.sax.SAXException: FWK005 parse may not be called while parsing.

GitHub | miszobi | 2 months ago
  1. 0

    Trying to concurrently verify multiple responses might fail

    GitHub | 2 months ago | miszobi
    org.xml.sax.SAXException: FWK005 parse may not be called while parsing.
  2. 0

    When a flow which contains a camel-validation endpoint is started, the XSD schemas are not loaded until the first request comes in and the camel-validation endpoint is first hit. If two requests come in simultaneously, the initialization will be performed twice, at the same time. It seems that SchemaFactory is not thread-safe, so this results in the following exception: 10:38:20,860 | ERROR - org.apache.camel.processor.DeadLetterChannel - org.apache.camel.processor.Logger - Failed delivery for exchangeId: ID-ATOS-B624 E47AF0/3211-1240562892751/0-11. On delivery attempt: 0 caught: org.xml.sax.SAXException: FWK005 parse may not be called while parsing. org.xml.sax.SAXException: FWK005 parse may not be called while parsing. at com.sun.org.apache.xerces.internal.jaxp.validation.Util.toSAXException(Util.java:62) at com.sun.org.apache.xerces.internal.jaxp.validation.XMLSchemaFactory.newSchema(XMLSchemaFactory.java:214) at javax.xml.validation.SchemaFactory.newSchema(SchemaFactory.java:594) at org.apache.camel.processor.validation.ValidatingProcessor.createSchema(ValidatingProcessor.java:204) at org.apache.camel.processor.validation.ValidatingProcessor.getSchema(ValidatingProcessor.java:118) at org.apache.camel.processor.validation.ValidatingProcessor.process(ValidatingProcessor.java:54) at org.apache.camel.impl.ProcessorEndpoint.onExchange(ProcessorEndpoint.java:92) at org.apache.camel.impl.ProcessorEndpoint$1.process(ProcessorEndpoint.java:66) at org.apache.camel.impl.converter.AsyncProcessorTypeConverter$ProcessorToAsyncProcessorBridge.process(AsyncProcessorTypeConverter.java:43) ..... For more info: http://www.nabble.com/Concurrency-Issue-with-camel-validation-td23213294.html Is it possible to backport the fix to 1.4?

    Apache's JIRA Issue Tracker | 8 years ago | Raúl Kripalani
    org.xml.sax.SAXException: FWK005 parse may not be called while parsing.
  3. 0

    Internet2

    internet2.edu | 7 months ago
    org.opensaml.ws.message.decoder.MessageDecodingException: Encountered error parsing message into its DOM representation
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    SAXException: FWK005 parse may not be called while parsing

    Stack Overflow | 2 years ago | bez
    org.xml.sax.SAXException: FWK005 parse may not be called while parsing.
  6. 0

    Concurrency Issue with Twitterati

    Google Groups | 8 years ago | Twitterati
    twitter4j.TwitterException: Twitter returned a non-XML response:<?xml version="1.0" encoding="UTF-8"?> <statuses type="array"> <status> .... <!-- removed for brevity --> </status> </statuses>

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. org.xml.sax.SAXException

      FWK005 parse may not be called while parsing.

      at com.sun.org.apache.xerces.internal.jaxp.validation.Util.toSAXException()
    2. Java RT
      SchemaFactory.newSchema
      1. com.sun.org.apache.xerces.internal.jaxp.validation.Util.toSAXException(Util.java:65)[na:1.7.0_71]
      2. com.sun.org.apache.xerces.internal.jaxp.validation.XMLSchemaFactory.newSchema(XMLSchemaFactory.java:256)[na:1.7.0_71]
      3. javax.xml.validation.SchemaFactory.newSchema(SchemaFactory.java:627)[na:1.7.0_71]
      4. javax.xml.validation.SchemaFactory.newSchema(SchemaFactory.java:659)[na:1.7.0_71]
      4 frames
    3. com.onelogin.saml2
      Util.validateXML
      1. com.onelogin.saml2.util.SchemaFactory.loadFromUrl(SchemaFactory.java:25)[classes/:na]
      2. com.onelogin.saml2.util.Util.validateXML(Util.java:215)[classes/:na]
      2 frames