| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| TCpClientINput Node - waiting for a data record |
« View previous topic :: View next topic » |
| Author |
Message
|
| vickas |
 Posted: Fri Jul 03, 2015 2:37 am Post subject: TCpClientINput Node - waiting for a data record |
 |
|
Centurion
Joined: 18 Aug 2013
Posts: 126
|
Can someone make me understand the basic parameter , waiting for a data record which is on the TCpClientINput Node .
I understand that this is the timeInterval for which the node waits to recieve more data ( after recieving data ) . if suppose if i set to 60 secs & if the node doesnt recieve any data for 60 secs (i.e after recieving the data for a while ) then this will trig to failure terminal when connected.
so, inorder to test this , i have used an open source TCPserver called as Sockettest . using this am able to put data & my flow is able to recieve data but when i stop putting messages for more than 60 secs , the flow isnt being propagated to failure terminal as expected .
is my understanding wrong ? if so , how will the waiting for a data work ? |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Jul 03, 2015 5:02 am Post subject: Re: TCpClientINput Node - waiting for a data record |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| vickas wrote: |
Can someone make me understand the basic parameter , waiting for a data record which is on the TCpClientINput Node .
I understand that this is the timeInterval for which the node waits to recieve more data ( after recieving data ) . if suppose if i set to 60 secs & if the node doesnt recieve any data for 60 secs (i.e after recieving the data for a while ) then this will trig to failure terminal when connected.
is my understanding wrong ? if so , how will the waiting for a data work ? |
What does the infocenter say about this? Not my interpretation. I would expect it to be propagated to the output terminal... or the no data terminal? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| vickas |
| Posted: Fri Jul 03, 2015 5:11 am Post subject: |
|
|
Centurion
Joined: 18 Aug 2013
Posts: 126
|
HI FJB ,
Here is what the infocenter says "
Use the Timeout waiting for a data record (seconds) property to specify how long the node listens on a connection for more data after the first byte of data has arrived. You can specify any length of time in seconds. The default is 60 seconds. When the specified time has been exceeded, all available data is sent to the Failure terminal. "
but this is not happening with the flow when i send a request with opensource TCP server.
I lso do not understand this " all available data " . its only when the node doesnt recieve any data then it is propagated to failure terminal .
now i dont understand where do this "all available data " come from ? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Jul 03, 2015 5:50 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| vickas wrote: |
HI FJB ,
Here is what the infocenter says "
Use the Timeout waiting for a data record (seconds) property to specify how long the node listens on a connection for more data after the first byte of data has arrived. You can specify any length of time in seconds. The default is 60 seconds. When the specified time has been exceeded, all available data is sent to the Failure terminal. "
but this is not happening with the flow when i send a request with opensource TCP server.
I lso do not understand this " all available data " . its only when the node doesnt recieve any data then it is propagated to failure terminal .
now i dont understand where do this "all available data " come from ? |
You did not say what you specified as record detection.
All available data in this context means to me that
- you don't have a record as defined by your input criteria
- you do have some kind of data, either random or partial record.
This data will be propagated to the Failure terminal.
Hope this clarifies it a bit...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| vickas |
| Posted: Fri Jul 03, 2015 1:02 pm Post subject: |
|
|
Centurion
Joined: 18 Aug 2013
Posts: 126
|
Hi fjb ,
Thnx for ua reply.
I have set record detection as delimited - customer delimiter -postfix. . what will the record detection do with the timeout scenrio ? How both are related ??
Apart from this , if at all I get a time out scenrio ( I.E not getting any data until it exceeds timeout - which is set on tcpclientinput node) then I want to disconnect n reconnect the connection to the server. So if I dnt get any data , I can use the trigger whch is default generated n propagtaed by the timeout record to close the connection by connecting to the close terminal of the tcpclientoutput node but how do I reconnect the server ?
Will the tcpclientinput node will be capable of again connecting automatically ?
I want to use only min & max of 1 connection only.
How do I achieve this ?? Any guidance plsss. |
|
| 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
|
|
|
|
