org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,322] Message: already reached end document

Spring JIRA | Vladimir Ritz Bossicard | 9 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

    Spring-ws reads the entire message for logging purposes (when logging is set to DEBUG) and Axiom complains that it has nothing else to process: DEBUG org.springframework.ws.soap.server.SoapMessageDispatcher - MessageDispatcher with name 'testing-ws' received request [<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><ns1:echoRequest xmlns:ns1="http://localhost:8080/testing-ws/services/echo">Hello</ns1:echoRequest></soapenv:Body></soapenv:Envelope>] DEBUG org.springframework.ws.soap.server.SoapMessageDispatcher - Endpoint mapping [org.springframework.ws.soap.server.endpoint.mapping.SoapActionEndpointMapping@11415c8] maps request to endpoint [com.testing.system.infrastructure.ws.EchoEndpoint@1a220e6] DEBUG org.springframework.ws.soap.server.SoapMessageDispatcher - Testing endpoint adapter [org.springframework.ws.server.endpoint.adapter.MessageEndpointAdapter@11df164] DEBUG org.springframework.ws.soap.server.SoapMessageDispatcher - Testing endpoint adapter [org.springframework.ws.server.endpoint.adapter.PayloadEndpointAdapter@67c1a6] DEBUG org.springframework.ws.soap.server.SoapMessageDispatcher - Testing endpoint exception resolver [org.springframework.ws.soap.server.endpoint.SimpleSoapExceptionResolver@6279d] WARN org.springframework.ws.soap.server.SoapMessageDispatcher - Endpoint invocation resulted in exception - responding with SOAP Fault org.springframework.ws.soap.axiom.AxiomSoapBodyException: Could not access envelope: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,322] Message: already reached end document; nested exception is org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,322] Message: already reached end document Caused by: org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,322] Message: already reached end document at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:239) at org.apache.axiom.om.impl.llom.OMElementImpl.buildNext(OMElementImpl.java:552) at org.apache.axiom.om.impl.llom.OMElementImpl.getFirstOMChild(OMElementImpl.java:563) at org.apache.axiom.om.impl.llom.OMElementImpl.getFirstElement(OMElementImpl.java:823) Setting the log level to INFO solves the problem but the info is quite hard to find and very unpleasant during development/debugging

    Spring JIRA | 9 years ago | Vladimir Ritz Bossicard
    org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,322] Message: already reached end document
  2. 0

    Spring-ws reads the entire message for logging purposes (when logging is set to DEBUG) and Axiom complains that it has nothing else to process: DEBUG org.springframework.ws.soap.server.SoapMessageDispatcher - MessageDispatcher with name 'testing-ws' received request [<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><ns1:echoRequest xmlns:ns1="http://localhost:8080/testing-ws/services/echo">Hello</ns1:echoRequest></soapenv:Body></soapenv:Envelope>] DEBUG org.springframework.ws.soap.server.SoapMessageDispatcher - Endpoint mapping [org.springframework.ws.soap.server.endpoint.mapping.SoapActionEndpointMapping@11415c8] maps request to endpoint [com.testing.system.infrastructure.ws.EchoEndpoint@1a220e6] DEBUG org.springframework.ws.soap.server.SoapMessageDispatcher - Testing endpoint adapter [org.springframework.ws.server.endpoint.adapter.MessageEndpointAdapter@11df164] DEBUG org.springframework.ws.soap.server.SoapMessageDispatcher - Testing endpoint adapter [org.springframework.ws.server.endpoint.adapter.PayloadEndpointAdapter@67c1a6] DEBUG org.springframework.ws.soap.server.SoapMessageDispatcher - Testing endpoint exception resolver [org.springframework.ws.soap.server.endpoint.SimpleSoapExceptionResolver@6279d] WARN org.springframework.ws.soap.server.SoapMessageDispatcher - Endpoint invocation resulted in exception - responding with SOAP Fault org.springframework.ws.soap.axiom.AxiomSoapBodyException: Could not access envelope: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,322] Message: already reached end document; nested exception is org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,322] Message: already reached end document Caused by: org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,322] Message: already reached end document at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:239) at org.apache.axiom.om.impl.llom.OMElementImpl.buildNext(OMElementImpl.java:552) at org.apache.axiom.om.impl.llom.OMElementImpl.getFirstOMChild(OMElementImpl.java:563) at org.apache.axiom.om.impl.llom.OMElementImpl.getFirstElement(OMElementImpl.java:823) Setting the log level to INFO solves the problem but the info is quite hard to find and very unpleasant during development/debugging

    Spring JIRA | 9 years ago | Vladimir Ritz Bossicard
    org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,322] Message: already reached end document
  3. 0

    [SWS-219] Spring-ws reads the entier stream when logging set to debug - Spring JIRA

    spring.io | 2 years ago
    org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException: ParseError at : Message: already reached end document
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Exception getting while reading OMElement object (Web Services forum at JavaRanch)

    coderanch.com | 2 years ago
    org.apache.axiom.om.OMException: java.lang.RuntimeException: [was class java.io.IOException]
  6. 0

    Axis2 version 1.3 exception org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException: end reached

    Stack Overflow | 4 years ago
    org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException: end reached!

  1. aldrinleal 51 times, last 3 months ago
6 unregistered visitors
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.apache.axiom.om.OMException

    javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,322] Message: already reached end document

    at org.apache.axiom.om.impl.builder.StAXOMBuilder.next()
  2. Axiom API
    StAXOMBuilder.next
    1. org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:239)
    1 frame
  3. Axiom Impl
    OMElementImpl.getFirstElement
    1. org.apache.axiom.om.impl.llom.OMElementImpl.buildNext(OMElementImpl.java:552)
    2. org.apache.axiom.om.impl.llom.OMElementImpl.getFirstOMChild(OMElementImpl.java:563)
    3. org.apache.axiom.om.impl.llom.OMElementImpl.getFirstElement(OMElementImpl.java:823)
    3 frames