axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AXIS2-5662) Parse Error: Message: Content is not allowed in prolog.
Date Wed, 30 Jul 2014 19:46:40 GMT

    [ https://issues.apache.org/jira/browse/AXIS2-5662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14079841#comment-14079841
] 

Andreas Veithen commented on AXIS2-5662:
----------------------------------------

In the network trace, the response looks correct.

For the Axis2 version: it is true that the Stackoverflow question was asked in the context
of Maven, but that doesn't matter. Actually the most effective thing to do might be to compute
the MD5 sum of the JAR and do a Google search with it.

Finally, I still want to see the full stack trace.

> Parse Error:  Message: Content is not allowed in prolog.
> --------------------------------------------------------
>
>                 Key: AXIS2-5662
>                 URL: https://issues.apache.org/jira/browse/AXIS2-5662
>             Project: Axis2
>          Issue Type: Bug
>            Reporter: Kyle Thayer
>         Attachments: ProblemCausingXMLshortened, npc_capture_0723_1400_bad.pcapng
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Here is the stack trace that the client is getting:
> INFO   | jvm 1    | 2014/05/07 15:18:26 | Caused by: org.apache.axis2.AxisFault: javax.xml.stream.XMLStreamException:
ParseError at [row,col]:[1,1]
> INFO   | jvm 1    | 2014/05/07 15:18:26 | Message: Content is not allowed in prolog.
> INFO   | jvm 1    | 2014/05/07 15:18:26 |                 at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
> INFO   | jvm 1    | 2014/05/07 15:18:26 |                 at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:123)
> INFO   | jvm 1    | 2014/05/07 15:18:26 |                 at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:67)
> INFO   | jvm 1    | 2014/05/07 15:18:26 |                 at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:354)
> INFO   | jvm 1    | 2014/05/07 15:18:26 |                 at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:417)
> INFO   | jvm 1    | 2014/05/07 15:18:26 |                 at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
> INFO   | jvm 1    | 2014/05/07 15:18:26 |                 at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
> INFO   | jvm 1    | 2014/05/07 15:18:26 |                 at com.netqos.inventory2.client.Inventory2WSStub.requestInventory(Inventory2WSStub.java:732)
> INFO   | jvm 1    | 2014/05/07 15:18:26 |                 at com.ca.netqos.connector.impl.npc.Inventory2WSStubImpl.connectorRequestInventory(Inventory2WSStubImpl.java:272)
> INFO   | jvm 1    | 2014/05/07 15:18:26 |                 at com.ca.netqos.connector.impl.NetQoSMDRImpl.getData(NetQoSMDRImpl.java:148)
> INFO   | jvm 1    | 2014/05/07 15:18:26 |                 at com.ca.netqos.connector.ucf.NetQoSConnector.get(NetQoSConnector.java:300)
> I have attached a copy of the XML causing the problem.  Any help with this issue would
be greatly appreciated.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


Mime
View raw message