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

JBoss Issue Tracker | David Lloyd | 8 years ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    XML character does not support on JBOSS server

    Stack Overflow | 2 years ago | Priya
    java.io.IOException: org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x1c) was found in the element content of the document.

    Root Cause Analysis

    1. java.io.IOException

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

      at org.jboss.wsf.common.DOMUtils.parse()
    2. org.jboss.wsf
      DOMUtils.parse
      1. org.jboss.wsf.common.DOMUtils.parse(DOMUtils.java:195)
      1 frame
    3. JBoss Web Services - Native Server
      RequestHandlerImpl.handleHttpRequest
      1. org.jboss.ws.core.soap.EnvelopeBuilderDOM.build(EnvelopeBuilderDOM.java:84)
      2. org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:294)
      3. org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:193)
      4. org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:454)
      5. org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:294)
      6. org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:204)
      7. org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:130)
      7 frames
    4. org.jboss.wsf
      AbstractEndpointServlet.service
      1. org.jboss.wsf.common.servlet.AbstractEndpointServlet.service(AbstractEndpointServlet.java:87)
      1 frame