MQSeries.net :: View topic - TCPClient Connection manager not refreshing

vickas · Posted: Thu Mar 25, 2021 4:52 am Post subject:

Hie All ,

I have a flow deployed on production server which is functioning as expected almost all the times but at very rare rare times i see the following issue coming up

flow functionality :
The Flow acts as TCP client which has to pick the data continuously from the server & do the necessary logics keeping connection open all the time.(so on TCP client Input node - close connections - No , time out waiting - 10 secs , records & elements - delimited , input & output stream - leave unchanged , close , out,catch , failure terminals connected )
and when the connection is closed by server , the flow must be able to re-establish the connection & read the data .

issue :
since the timeout wait mentioned on the tcpclient node is 10 secs , when the server doesnt send any data for the time period more than 10 secs , the flow throws the following exception
exception while looking for delimiter timed out wating for data :-7ffb 15 36 3B 54 52 55 45 3B 50 41 52 4B 49 4E 47 3B 0A
& controls comes from the close terminal of TCPIP client input node.
& this happened around 10 times within the span of 2 hours on the same day & all the time , the flow established a fresh connection & was able to read the data as expected , but at the 11th time , the flow WAS NOT able to pick the data untill RESTARTED .
The var/log/messages showed the following only 2 times

[Thread 23943] (Msg 1/1) BIP3585E: Failed to create required connections in connection manager using connection details 'xx.xxx.xxx.xx:11111'

[Thread 23943] (Msg 1/1) BIP3565E: Failed to reach hostname 'xx.xxx.xxx.xx' within the timeout period of '10' seconds.

the same issue happened for the 2nd time in span of 3 months .

surprisingly , netstat showed - ESTABLISHED ( before flow was restarted ) but the flow wasnt able to pick the data untill the flow was restarted

what might be the issue ??
why the flow is able to reconnect & pick the data almost all the times but not at some times ?
Is there something to look at the TCP client connection manager ??
Is TCP client connection manager holding the stale connection ??
Do servers hold connections when client tries to connect ?

Please note that I have the same sort of flow running with almost same functionality but on DIFFERENT EG .
broker version - 9.0.0.2