MQSeries.net :: View topic - TCP/IP Node-Not able to flush the stream once Timeout Occurs

ican.sbyn · Posted: Wed Nov 03, 2010 7:56 pm Post subject:

The Functionality:We send the request to a TCP/IP server through ESB and get the Response back from that TCP/IP Server in esb

HttpInput Node--->TCPIPClientOutput Node-->TCPIPClientReceive Node-->MQOUTPUT Node

If timeout occurs from the TCPIPClientReceive Node then the error is logged in database.
If we send a request with a Request Id , then the same request Id will be attached in the Response message also. This means, if a request message is sent with a request id 230
then the response message will also contain the request id field with value 230.
Structure of RequestMessage:

<ReqTcp>
<RequestId>230</RequestId>
<Name>ABC</Name>
</ReqTcp>

Structure of ResponseMessage:

<RespTcp>
<RequestId>230</RequestId>
<Department>PQR</Department>
</RespTcp>

Problem Scenario in the event of time out: A Request Message is sent with a Request ID 234. The Time Out Occurred due to some problem. After this problem (Timeout) is over then again a request Message is
sent with a Request id 235.In this case the response is comming for the previous request!!(---That means , in this case the response is comming with request id 234!! Now, if another
request message is sent with a request ID 236, the response is comming with Request id 235 and so on---until the flow is re-deployed).
Any body encountered this probem before...? Any Input will be apprecated.