You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Gee Chia (JIRA)" <ji...@apache.org> on 2007/03/08 14:42:24 UTC
[jira] Created: (AXIS2-2301) wsa 04 version problem - AxisFault
Required MessageID in header in Response
wsa 04 version problem - AxisFault Required MessageID in header in Response
---------------------------------------------------------------------------
Key: AXIS2-2301
URL: https://issues.apache.org/jira/browse/AXIS2-2301
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: Addressing
Affects Versions: 1.1.1
Reporter: Gee Chia
A Web service request worked in wsa 1.0 but failed in wsa 04 with
AxisFault: A required message information header, To, MessageID, or Action, is not present. Basically, message ID was not set in MessageContext for a Response was the cause of the AxisFault.
The exception was thrown from the checkForMandatoryHeaders method in the org.apache.axis2.handlers.addressing.AddressingSubmissionInHandler.
As I understood from the code inspection,AbstractInOutSyncMessageReceiver::receive() method invokes
MessageContext outMsgContext = MessageContextBuilder.createOutMessageContext(msgContext);
The messageID is conditionally set in the outMsgContext.
Then later on, it failed with messageID not set fault.
The same transaction/request worked in wsa 1.0. It worked because AddressingFinalInHandler::checkForMandatoryHeaders only checks for Action only.
My code worked in Axis2 1.1, but failed in nightly build. I checked Axis2 1.1.1, I saw AddressingSubmissionInHandler change was introduced in 1.1.1.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Resolved: (AXIS2-2301) wsa 04 version problem - AxisFault
Required MessageID in header in Response
Posted by "Brian DePradine (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian DePradine resolved AXIS2-2301.
------------------------------------
Resolution: Fixed
Fix Version/s: nightly
> wsa 04 version problem - AxisFault Required MessageID in header in Response
> ---------------------------------------------------------------------------
>
> Key: AXIS2-2301
> URL: https://issues.apache.org/jira/browse/AXIS2-2301
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: Addressing
> Affects Versions: 1.1.1
> Reporter: Gee Chia
> Assigned To: Brian DePradine
> Fix For: nightly
>
>
> A Web service request worked in wsa 1.0 but failed in wsa 04 with
> AxisFault: A required message information header, To, MessageID, or Action, is not present. Basically, message ID was not set in MessageContext for a Response was the cause of the AxisFault.
> The exception was thrown from the checkForMandatoryHeaders method in the org.apache.axis2.handlers.addressing.AddressingSubmissionInHandler.
> As I understood from the code inspection,AbstractInOutSyncMessageReceiver::receive() method invokes
> MessageContext outMsgContext = MessageContextBuilder.createOutMessageContext(msgContext);
> The messageID is conditionally set in the outMsgContext.
> Then later on, it failed with messageID not set fault.
> The same transaction/request worked in wsa 1.0. It worked because AddressingFinalInHandler::checkForMandatoryHeaders only checks for Action only.
> My code worked in Axis2 1.1, but failed in nightly build. I checked Axis2 1.1.1, I saw AddressingSubmissionInHandler change was introduced in 1.1.1.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2301) wsa 04 version problem - AxisFault
Required MessageID in header in Response
Posted by "Gee Chia (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479327 ]
Gee Chia commented on AXIS2-2301:
---------------------------------
Hi Brian:
Basically, I have a simple web service, ServiceB with "start" operation. I sent the "start" request using wsa 04, and include here is the TCPMon output of the request and response. See MessageID was not in the response header, and this caused the AxisFault I described.
Please note: To get the Response as included below, I had commented the MessageID check in AdressingSubmissionInHandler::checkForMandatoryHeaders.
Let me know if you need additional information.
Request:
<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"><soapenv:Header><wsa:To>http://localhost:8090/wsmex/services/ServiceB</wsa:To><wsa:ReplyTo><wsa:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Address></wsa:ReplyTo><wsa:MessageID>urn:uuid:D8E5E04CC4F721903D1173365825365</wsa:MessageID><wsa:Action>http://services.example.org/mex/interop/startRequest</wsa:Action></soapenv:Header><soapenv:Body><ex:start xmlns:ex="http://services.example.org/mex/interop">3</ex:start></soapenv:Body></soapenv:Envelope>
Response:
<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"><soapenv:Header><wsa:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To><wsa:ReplyTo><wsa:Address>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Address></wsa:ReplyTo><wsa:Action>http://services.example.org/mex/interop/startResponse</wsa:Action><wsa:RelatesTo>urn:uuid:D8E5E04CC4F721903D1173365825365</wsa:RelatesTo></soapenv:Header><soapenv:Body><wsa:EndpointReference><wsa:Address>http://localhost:8090/wsmex/services/ServiceA</wsa:Address></wsa:EndpointReference></soapenv:Body></soapenv:Envelope>
> wsa 04 version problem - AxisFault Required MessageID in header in Response
> ---------------------------------------------------------------------------
>
> Key: AXIS2-2301
> URL: https://issues.apache.org/jira/browse/AXIS2-2301
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: Addressing
> Affects Versions: 1.1.1
> Reporter: Gee Chia
> Assigned To: Brian DePradine
>
> A Web service request worked in wsa 1.0 but failed in wsa 04 with
> AxisFault: A required message information header, To, MessageID, or Action, is not present. Basically, message ID was not set in MessageContext for a Response was the cause of the AxisFault.
> The exception was thrown from the checkForMandatoryHeaders method in the org.apache.axis2.handlers.addressing.AddressingSubmissionInHandler.
> As I understood from the code inspection,AbstractInOutSyncMessageReceiver::receive() method invokes
> MessageContext outMsgContext = MessageContextBuilder.createOutMessageContext(msgContext);
> The messageID is conditionally set in the outMsgContext.
> Then later on, it failed with messageID not set fault.
> The same transaction/request worked in wsa 1.0. It worked because AddressingFinalInHandler::checkForMandatoryHeaders only checks for Action only.
> My code worked in Axis2 1.1, but failed in nightly build. I checked Axis2 1.1.1, I saw AddressingSubmissionInHandler change was introduced in 1.1.1.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2301) wsa 04 version problem - AxisFault
Required MessageID in header in Response
Posted by "Brian DePradine (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12479320 ]
Brian DePradine commented on AXIS2-2301:
----------------------------------------
Hi Gee,
Can you please provide some more details on the scenario that you are trying to run. Including the TCPMon output of the request and response messages would also be a great help.
> wsa 04 version problem - AxisFault Required MessageID in header in Response
> ---------------------------------------------------------------------------
>
> Key: AXIS2-2301
> URL: https://issues.apache.org/jira/browse/AXIS2-2301
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: Addressing
> Affects Versions: 1.1.1
> Reporter: Gee Chia
> Assigned To: Brian DePradine
>
> A Web service request worked in wsa 1.0 but failed in wsa 04 with
> AxisFault: A required message information header, To, MessageID, or Action, is not present. Basically, message ID was not set in MessageContext for a Response was the cause of the AxisFault.
> The exception was thrown from the checkForMandatoryHeaders method in the org.apache.axis2.handlers.addressing.AddressingSubmissionInHandler.
> As I understood from the code inspection,AbstractInOutSyncMessageReceiver::receive() method invokes
> MessageContext outMsgContext = MessageContextBuilder.createOutMessageContext(msgContext);
> The messageID is conditionally set in the outMsgContext.
> Then later on, it failed with messageID not set fault.
> The same transaction/request worked in wsa 1.0. It worked because AddressingFinalInHandler::checkForMandatoryHeaders only checks for Action only.
> My code worked in Axis2 1.1, but failed in nightly build. I checked Axis2 1.1.1, I saw AddressingSubmissionInHandler change was introduced in 1.1.1.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Assigned: (AXIS2-2301) wsa 04 version problem - AxisFault
Required MessageID in header in Response
Posted by "Brian DePradine (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian DePradine reassigned AXIS2-2301:
--------------------------------------
Assignee: Brian DePradine
> wsa 04 version problem - AxisFault Required MessageID in header in Response
> ---------------------------------------------------------------------------
>
> Key: AXIS2-2301
> URL: https://issues.apache.org/jira/browse/AXIS2-2301
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: Addressing
> Affects Versions: 1.1.1
> Reporter: Gee Chia
> Assigned To: Brian DePradine
>
> A Web service request worked in wsa 1.0 but failed in wsa 04 with
> AxisFault: A required message information header, To, MessageID, or Action, is not present. Basically, message ID was not set in MessageContext for a Response was the cause of the AxisFault.
> The exception was thrown from the checkForMandatoryHeaders method in the org.apache.axis2.handlers.addressing.AddressingSubmissionInHandler.
> As I understood from the code inspection,AbstractInOutSyncMessageReceiver::receive() method invokes
> MessageContext outMsgContext = MessageContextBuilder.createOutMessageContext(msgContext);
> The messageID is conditionally set in the outMsgContext.
> Then later on, it failed with messageID not set fault.
> The same transaction/request worked in wsa 1.0. It worked because AddressingFinalInHandler::checkForMandatoryHeaders only checks for Action only.
> My code worked in Axis2 1.1, but failed in nightly build. I checked Axis2 1.1.1, I saw AddressingSubmissionInHandler change was introduced in 1.1.1.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org