Posted: Tue Jan 31, 2017 10:18 pm Post subject: TCPIP msg flow changing servers timestamp
Centurion
Joined: 18 Aug 2013 Posts: 126
I witness a wierd , very surprising happening with the TCPIP flow on IIB v9.0.0.2 and WMQ 7.5
We have a msg flow which has TCP client Input & TCP client output nodes to exchange data ( heartbeats , data , Acks ) very frequently .. every 4 secs msgs (Heartbeat msgs ) are to be exchanged & along with this a BAT msg(huge dump of data) to be exchanged ( send data & recieve Acks in one go ) and for this we have changed the default values of configurable service
SO_RCVBUF = 1024 KB ,
SO_SNDBUF = 1024 KB,
TCP_NODELAY = TRUE
CloseWithUnprocessedData = TRUE
while on the OS level the tcp buffer is still 128 KB .
having this flow deployed we observe that the server timestamp is getting effected . we have a script which runs 4 secs to display the servers timestamp and this shows us clearly the time drift . The timestamp value is jumping suddenly .. for eg ,
2017-01-26 13:07:59
2017-01-26 13:08:19
2017-01-26 13:08:20
2017-01-26 13:08:21
2017-01-26 13:08:23
2017-01-26 13:08:27
2017-01-26 13:08:31
if you notice the time suddenly jumps from 13:07:59 to 13:08:19 and gets stuck for 20-30 secs and then comes back to normal time .
This is happening intermittently and happening only after the flow deployment .
The ESB server is in SYNC with the NTP servers .
There is no broker restart or EG crash/restart noticed in broker logs
No signs of server gettting restarted.
what else to be checked ??
changing TCP params can effect servers timestamp ??
is it possible for msg flow with TCP nodes to impact/hold the servers timestamp ??
Do tcp connections hold the server timestamps intermittently?
please help me ..
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