|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
TCPIP Client Receive Node Timeout Error |
« View previous topic :: View next topic » |
Author |
Message
|
hoanguye |
Posted: Tue Nov 24, 2020 8:41 am Post subject: TCPIP Client Receive Node Timeout Error |
|
|
Newbie
Joined: 24 Nov 2020 Posts: 3
|
Hi all,
IIB version 10
Requirement:
I am using TCP/IP Client Output Node and TCP/IP Client Receive Node to send and receive data over TCP to a remote host. Right now, I am able to send the raw data (which is a BLOB) to the server, and receive back the data from the server through the TCP/IP Client Receive Node.
My current flow:
ESQL (prepareRequest) -> TCPIPClientOutput (sendRequest) -> TCPIPClientReceive (receiveResponse) -> ESQL (produceResponse)
Problem:
But the problem is that the Client Receive Node cannot form a record with the data being sent back. The BLOB hex sent back does not end with any delimiter, and the server does not close the socket connection after sending the data. Right now, the Client Receive Node is going to the 'Failure' route, and giving a BIP3552 error, meaning that Timeout occurred on connection while waiting for all the data required to form a record, though I see that it has received the last few bytes of the hex value of the response.
[img]
https://github.com/ShaneNguyen99/CSE373_Search_Engine/blob/master/Screen%20Shot%202020-11-25%20at%207.14.13%20PM.png
[/img]
Question:
Is there a way that the Client Receive Node not throw the 3552 error, and be able to parse the whole hex BLOB sent back? I am thinking of configuring the Client Receive Node properties.
Last edited by hoanguye on Wed Nov 25, 2020 7:08 pm; edited 2 times in total |
|
Back to top |
|
 |
hoanguye |
Posted: Wed Nov 25, 2020 6:42 pm Post subject: |
|
|
Newbie
Joined: 24 Nov 2020 Posts: 3
|
|
Back to top |
|
 |
hoanguye |
Posted: Wed Nov 25, 2020 6:46 pm Post subject: |
|
|
Newbie
Joined: 24 Nov 2020 Posts: 3
|
|
Back to top |
|
 |
timber |
Posted: Fri Nov 27, 2020 3:29 am Post subject: |
|
|
 Grand Master
Joined: 25 Aug 2015 Posts: 1292
|
Quote: |
Is there a way that the Client Receive Node not throw the 3552 error, and be able to parse the whole hex BLOB sent back? I am thinking of configuring the Client Receive Node properties.
|
In the TCPIPClientReceive node, what value are you using for 'Record detection'? You have not described the format of the response, but it sounds as if you need 'Parsed Record Sequence'.
You may also require a DFDL model to describe the response format, but that depends on the details of the format. |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
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
|
|
|
|