ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <>
Subject [jira] [Updated] (AXIOM-439) Reporting unexpected END OF DOCUMENT
Date Sun, 23 Sep 2012 12:17:07 GMT


Andreas Veithen updated AXIOM-439:

    Attachment: request.xml

With the above change, your sample code is able to successfully send a request (see attached
file). I don't get any exception from Axiom. Note however that I did the test with the trunk
versions (1.7.0-SNAPSHOT) of Axis2 and Rampart.
> Reporting unexpected END OF DOCUMENT
> ------------------------------------
>                 Key: AXIOM-439
>                 URL:
>             Project: Axiom
>          Issue Type: Bug
>          Components: API
>    Affects Versions: 1.2.13
>         Environment: Axis2 Rampart running in Tomcat
>            Reporter: Brian Reinhold
>            Assignee: Andreas Veithen
>             Fix For: 1.2.14
>         Attachments:, request.xml, sendToWan.xml
> Handling an XML SOAP document on the client that worked with Axis2 version 1.5.2, Axiom
1.2.9, Rampart 1.5.1 now throws an OMException "Unexpected END_DOCUMENT event" when Axis2
and Rampart is updated to 1.6.2 and Axiom is updated to all of the versions above. The 1.2.14
version is especially important due to a fix for Rampart on the server side.
> The stack trace is as follows. Attached is the SOAP document as picked up on the wire
using Wireshark when using the working versions of the above libraries. The source code is
otherwise unchanged between the the usages of the various libraries. I have replaced the SOAP
body with the simple text string "Hi" to make sure it was not something ugly in the PCD-01
body and the error still occurs. The SAML token is generated by the Rampart STS service and
is generated identically in both the 1.6.2 and 1.5.1 versions.
> Unexpected END_DOCUMENT event
> 	at
> 	at
> 	at
> 	at
> 	at
> 	at
> 	at
> 	at
> 	at org.apache.rampart.util.RampartUtil.appendChildToSecHeader(
> 	at org.apache.rampart.util.RampartUtil.insertSiblingAfter(
> 	at org.apache.rampart.builder.BindingBuilder.handleSupportingTokens(
> 	at
> 	at
> 	at org.apache.rampart.handler.RampartSender.invoke(
> 	at org.apache.axis2.engine.Phase.invokeHandler(
> 	at org.apache.axis2.engine.Phase.invoke(
> 	at org.apache.axis2.engine.AxisEngine.invoke(
> 	at org.apache.axis2.engine.AxisEngine.send(
> 	at org.apache.axis2.description.OutInAxisOperationClient.send(
> 	at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(
> 	at org.apache.axis2.client.OperationClient.execute(
> 	at com.lampreynetworks.ahd.wan.sender.axis2.SecureAxis2WanSender.sendDocument(
> 	at BaseManagerWan_SecureAxis2Send$3.documentClosed(
> 	at com.lampreynetworks.ahd.pcd.document.PanToPcdTranslator.documentFinished(
> 	at com.lampreynetworks.ahd.pcd.document.PanToPcdTranslator.notifyStateChange(
> 	at com.lampreynetworks.ahd.oxp.manager.FiniteStateMachine.setState(
> 	at com.lampreynetworks.ahd.oxp.manager.FiniteStateMachine.access$4(
> 	at com.lampreynetworks.ahd.oxp.manager.FiniteStateMachine$ApduFilter.receive(
> 	at com.lampreynetworks.ahd.oxp.manager.FiniteStateMachine$ApduFilter.receive(
> 	at com.lampreynetworks.ahd.oxp.Asn$RlrqApdu.dispatch(
> 	at com.lampreynetworks.ahd.oxp.manager.FiniteStateMachine.filterApdu(
> 	at com.lampreynetworks.ahd.oxp.manager.FiniteStateMachine.receiveApdu(
> 	at sockettcp.SocketTcpNexus$

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message