ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » SOAP Inputnode and SOAP Replynode - Handle Reused after repl

Post new topic  Reply to topic
 SOAP Inputnode and SOAP Replynode - Handle Reused after repl « View previous topic :: View next topic » 
Author Message
Harsha_AS
PostPosted: Mon Jun 05, 2017 4:00 pm    Post subject: SOAP Inputnode and SOAP Replynode - Handle Reused after repl Reply with quote

Apprentice

Joined: 04 Dec 2011
Posts: 26
Hello,

I can see that I am getting the control back after sending the reply back from SOAP Reply Node.

Below is the flow.

SOAPInput -> WTX Node -> SOAPReplay Node.

When the WTX Node out terminal is connected to SOAPreply Node it works fine.(Success Scenario)

When the WTX Node Failure terminal is connected to SOAPReply node, the response is sent to Requester but the control comes back to after WTX node and it fails with the below error.

I understand why I am getting the below error. But I am not sure why the control is coming back.

ExceptionList
RecoverableException
File:CHARACTER:F:\build\S1000_slot1\S1000_P\src\DataFlowEngine\MessageServices\ImbDataFlowNode.cpp
Line:INTEGER:1239
Function:CHARACTER:ImbDataFlowNode::createExceptionList
Type:CHARACTER:ComIbmSOAPInputNode
Name:CHARACTER:MF_ProductAvailabillity#FCMComposite_1_1
Label:CHARACTER:MF_ProductAvailabillity.SOAP Input
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:2230
Text:CHARACTER:Node throwing exception
Insert
Type:INTEGER:14
Text:CHARACTER:MF_ProductAvailabillity.SOAP Input
RecoverableException
File:CHARACTER:F:\build\S1000_slot1\S1000_P\src\DataFlowEngine\PluginInterface\ImbJniNode.cpp
Line:INTEGER:1273
Function:CHARACTER:ImbJniNode::evaluate
Type:CHARACTER:ComIbmRouteNode
Name:CHARACTER:MF_ProductAvailabillity#FCMComposite_1_5
Label:CHARACTER:MF_ProductAvailabillity.RouteToSplitData
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:2230
Text:CHARACTER:Caught exception and rethrowing
Insert
Type:INTEGER:14
Text:CHARACTER:MF_ProductAvailabillity.RouteToSplitData
RecoverableException
File:CHARACTER:F:\build\S1000_slot1\S1000_P\src\DataFlowEngine\PluginInterface\ImbJniNode.cpp
Line:INTEGER:1273
Function:CHARACTER:ImbJniNode::evaluate
Type:CHARACTER:ComIbmSOAPExtractNode
Name:CHARACTER:MF_ProductAvailabillity#FCMComposite_1_11.SF_getPriceList#FCMComposite_1_1
Label:CHARACTER:MF_ProductAvailabillity.SF_getPriceList.SOAP Extract
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:2230
Text:CHARACTER:Caught exception and rethrowing
Insert
Type:INTEGER:14
Text:CHARACTER:MF_ProductAvailabillity.SF_getPriceList.SOAP Extract
RecoverableException
File:CHARACTER:F:\build\S1000_slot1\S1000_P\src\DataFlowEngine\PluginInterface\ImbJniNode.cpp
Line:INTEGER:1273
Function:CHARACTER:ImbJniNode::evaluate
Type:CHARACTER:ComIbmJavaComputeNode
Name:CHARACTER:MF_ProductAvailabillity#FCMComposite_1_11.SF_getPriceList#FCMComposite_1_5
Label:CHARACTER:MF_ProductAvailabillity.SF_getPriceList.WTXRequestBuilder
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:2230
Text:CHARACTER:Caught exception and rethrowing
Insert
Type:INTEGER:14
Text:CHARACTER:MF_ProductAvailabillity.SF_getPriceList.WTXRequestBuilder
RecoverableException
File:CHARACTER:F:\build\S1000_slot1\S1000_P\src\DataFlowEngine\PluginInterface\ImbJniNode.cpp
Line:INTEGER:1273
Function:CHARACTER:ImbJniNode::evaluate
Type:CHARACTER:ComIbmJavaComputeNode
Name:CHARACTER:MF_ProductAvailabillity#FCMComposite_1_11.SF_getPriceList#FCMComposite_1_7
Label:CHARACTER:MF_ProductAvailabillity.SF_getPriceList.WTXFailure_GetpriceList1
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:2230
Text:CHARACTER:Caught exception and rethrowing
Insert
Type:INTEGER:14
Text:CHARACTER:MF_ProductAvailabillity.SF_getPriceList.WTXFailure_GetpriceList1
RecoverableException
File:CHARACTER:F:\build\S1000_slot1\S1000_P\src\DataFlowEngine\PluginInterface\ImbJniNode.cpp
Line:INTEGER:1273
Function:CHARACTER:ImbJniNode::evaluate
Type:CHARACTER:ComIbmSOAPEnvelopeNode
Name:CHARACTER:MF_ProductAvailabillity#FCMComposite_1_11.SF_getPriceList#FCMComposite_1_12
Label:CHARACTER:MF_ProductAvailabillity.SF_getPriceList.SOAP Envelope
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:2230
Text:CHARACTER:Caught exception and rethrowing
Insert
Type:INTEGER:14
Text:CHARACTER:MF_ProductAvailabillity.SF_getPriceList.SOAP Envelope
RecoverableException
File:CHARACTER:F:\build\S1000_slot1\S1000_P\src\WebServices\WSLibrary\ImbSOAPReplyNode.cpp
Line:INTEGER:416
Function:CHARACTER:ImbSOAPReplyNode::evaluate
Type:CHARACTER:ComIbmSOAPReplyNode
Name:CHARACTER:MF_ProductAvailabillity#FCMComposite_1_2
Label:CHARACTER:MF_ProductAvailabillity.SOAP Reply
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:3752
Text:CHARACTER:Error occurred in ImbSOAPReplyHelper::makeSOAPReply()
Insert
Type:INTEGER:14
Text:CHARACTER:MF_ProductAvailabillity.SOAP Reply
RecoverableException
File:CHARACTER:F:\build\S1000_slot1\S1000_P\src\WebServices\WSLibrary\ImbSOAPReplyHelper.cpp
Line:INTEGER:300
Function:CHARACTER:ImbSOAPReplyHelper::makeSOAPReply
Type:CHARACTER:
Name:CHARACTER:
Label:CHARACTER:
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:3745
Text:CHARACTER:Message does not contain a valid SOAP Reply Identifier. Invalid Handle
Insert
Type:INTEGER:5
Text:CHARACTER:534f4150000000000100000038bca97a8032000000000000
Insert
Type:INTEGER:5
Text:CHARACTER:MF_ProductAvailabillity#FCMComposite_1_2
Insert
Type:INTEGER:5
Text:CHARACTER:SOAP
Insert
Type:INTEGER:5
Text:CHARACTER:ReplyIdentifier
RecoverableException
File:CHARACTER:F:\build\S1000_slot1\S1000_P\src\WebServices\WSLibrary\ImbSOAPHandleManager.cpp
Line:INTEGER:1430
Function:CHARACTER:ImbInFlightMessageHandle::throwHandleException
Type:CHARACTER:
Name:CHARACTER:
Label:CHARACTER:
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:3742
Text:CHARACTER:ERROR, Handle Reused after reply sent.
Insert
Type:INTEGER:5
Text:CHARACTER:534f4150000000000100000038bca97a8032000000000000
Insert
Type:INTEGER:5
Text:CHARACTER:SOAP
Insert
Type:INTEGER:5
Text:CHARACTER:ReplyIdentifier
Back to top
View user's profile Send private message Send e-mail
fjb_saper
PostPosted: Mon Jun 05, 2017 9:25 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
Looks like you have a construct like this:
Code:

             |--- (error) ----------------------------------
             |                |  (errror)                  |
Soap Input --|---------WTX  --|------------------success ------------------Soap Reply



So Soap Reply gets called twice... once on the error output of WTX then the error being thrown to Soap Input and propagated again to Soap Reply a second time...

Have fun
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » SOAP Inputnode and SOAP Replynode - Handle Reused after repl
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
  
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.