| Author |
Message
|
| vickas |
 Posted: Wed Sep 07, 2016 10:15 am Post subject: TCPIP Client Connection Manager DEBUGGING |
 |
|
Centurion
Joined: 18 Aug 2013
Posts: 126
|
hie Experts .
Need a suggestion on how to trace the TCP IP connection manager ?
We have a flow which exchange heartbeats and data messages & corresponding Acks over TCP/IP .
We happen to see that daily for 1 or 2 data messages ( xml msg seperated by custom delimeter sent by the server ) Acks werent being sent back by the flow .
when we ran the TCP IP dump ( using wireshark ) , its very clear that those data msgs reached ESB server but we cant find any trace of the messages in the flow logs ( the complete msg is being logged soon after the Client INput Node ) .
TCP Client Input Node Properties
close connection = No
timeout = 60 secs
Input parsing = BLOB
Record and elements = delimited , customer delimeter ( 04 ) , postfix
wondering where can the message be lost ??
Enabling trace at EG level will help us in anyway ??
Can the mqsitrace capture each and everything including the TCP Connection manager connections ??
/var/log ( broker log ) has no clue about it
where else do we need to check ?
how do we troubleshoot this ?
plZ put in your thoughts & share your valueable experiences . |
|
| Back to top |
|
 |
| timber |
| Posted: Thu Sep 08, 2016 12:15 am Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
You have set the delimiter to 'postfix'. So you are declaring that every message will be followed by a delimiter - including the final one.
Is it possible that the final message sometimes does not end with the 0x04 delimiter? |
|
| Back to top |
|
|
| vishnurajnr |
| Posted: Thu Sep 08, 2016 1:19 am Post subject: |
|
|
Centurion
Joined: 08 Aug 2011
Posts: 134
Location: Trivandrum
|
| Audit the messages from out and Failure terminal.. Just for debugging.. |
|
| Back to top |
|
|
| vickas |
| Posted: Sat Sep 17, 2016 11:03 pm Post subject: |
|
|
Centurion
Joined: 18 Aug 2013
Posts: 126
|
Hie Timber ,
In the TCP stream Each and every message will be seperated by 0x04 .
The data flows in continously with connection being opened always so i cannot say about the "last msg".
But how do we have to understand this ?
messages being reached onto ESB layer & not able to trace that msg ,
how do we have to trace it bcz this happens one or two times a day & sometimes there will be no sch occurences ?
I dont think running mqsitrace - debug be helpful in this case because it collects huge amounts of data & cant even write it to the file .
Can you please put your thoughts ? |
|
| Back to top |
|
|
| timber |
| Posted: Sun Sep 18, 2016 11:50 pm Post subject: |
|
|
Grand Master
Joined: 25 Aug 2015
Posts: 1292
|
You could try switching on Activity Trace (http://www.ibm.com/support/knowledgecenter/en/SSMKHH_10.0.0/com.ibm.etools.mft.doc/bj55000_.htm). It might prove whether or not the message was actually seen by the TCPIPClientInput node.
If that doesn't provide any useful info then I think it might be time for a PMR. |
|
| Back to top |
|
|
|
|
