| Author |
Message
|
| mqlover |
 Posted: Tue Sep 14, 2010 8:55 pm Post subject: SOAP reply identifier is not valid |
 |
|
Disciple
Joined: 25 Jul 2010
Posts: 176
|
Hi,
I am exposing message flow as webservice. I have used SOAP nodes,
SOAPInputnode->SOAPExtractnode->Compute->MQOutputnode.
The reply from the backend is placed on to the queue given in MQInput node.
MQInputNode->Computenode->Envelopnode->SOAPReplynode.
In SOAPEnvelop node i am creating a new envelop and not using the default one i.e $LocalEnvironment/SOAP/Envelop.
But after this SOAPEnvelop node I am getting the exception
"Message does not contain a valid SOAP Reply Identifier" and also
"Error occurred in ImbSOAPReplyHelper::makeSOAPReply()" with error code "3752".
Can any1 please tell me what I am supposed to changed so that message contains a valid SOAP reply identifier.
Thanks |
|
| Back to top |
|
 |
| kimbert |
| Posted: Wed Sep 15, 2010 1:15 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Is the reply flow in the same execution group as the sender flow? |
|
| Back to top |
|
|
| mqlover |
| Posted: Wed Sep 15, 2010 2:22 am Post subject: SOAP reply identifier is not valid |
|
|
Disciple
Joined: 25 Jul 2010
Posts: 176
|
| Ya it is in the same execution group.Rather both the flows i have done in the same message flow itself. |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Sep 15, 2010 5:19 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Anybody else got a suggestion? I'm out of ideas. |
|
| Back to top |
|
|
| WMBDEV1 |
| Posted: Wed Sep 15, 2010 6:55 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
| kimbert wrote: |
| Anybody else got a suggestion? I'm out of ideas. |
I've been out of the game for a while now but i'd be tempted to take a dump of the root and environment before it went to the reply node and then compare that to someones dump that worked to help try and identify any differences. |
|
| Back to top |
|
|
| mgk |
| Posted: Wed Sep 15, 2010 8:17 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
How are you preserving the ReplyIdentifier in the first flow and how are you restoring it in the second flow?
Also there may be no need in this case to use the SOAPEnvelope node in the response flow because the SOAPReply node creates a new envelope for you automatically...
REegards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| mqlover |
| Posted: Thu Sep 16, 2010 12:46 am Post subject: SOAP reply identifier is not valid |
|
|
Disciple
Joined: 25 Jul 2010
Posts: 176
|
Hi,
I have removed the SOAP Envelop node.
After the SOAP input node I am making the HttpInputHeader null.
Should i restore this header when sending the reply.
I am not setting any ReplyIdentifier field in SOAPInput node. But I am not understanding why is it throwing an exception when sending back a reply.
Thanks |
|
| Back to top |
|
|
| mgk |
| Posted: Thu Sep 16, 2010 1:41 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
OK, you need to understand how the SOAPInput node and the SOAPReply node are paired together. If you look at the output from a Trace node after the SOAPInput node you will see in the LocalEnvrionment tree a ReplyIdentifier specified. This is the value that links the two nodes and needs to be preserved between your two flows. You need to save this value in the first flow to a location of your choice (e.g. in the message maybe in an RFH2 or in a DB or on a queue) and in the second flow you need to restore this value to the same location in the LocalEnvrionment that you got it from in the first flow. Then the reply node can get back to the same client that made the call to the Input node in the first place.
Regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
|
|
