ACK timeout reporting

[mmaund]

I have been having this same issue and have voted for the bug MIRTH_1073. I am reluctant to enable Persistent Queues since I dont' know what the affect will be. Questions:

* will new messages just stack up behind the queued message until it goes?
* If the queued message never goes, will all messages stop?
* Will channel synchronization work properly with this setting?

Thanks in advance.

[nicovn]

Just a hint ... you get the "ack timeout" error also when the 3rd party system is closing the socket connection in between two message transfers ...

I would suggest to diagnose the socket data transfer using e.g. Wireshark and verify if/when the acknowledgements arrive.

Best Regards

Nico

[mmaund]

Originally Posted by nicovn

Just a hint ... you get the "ack timeout" error also when the 3rd party system is closing the socket connection in between two message transfers ...

I would suggest to diagnose the socket data transfer using e.g. Wireshark and verify if/when the acknowledgements arrive.

Best Regards

Nico

I just found the following bug report (MIRTH-1442) that describes my exact issue...

http://www.mirthcorp.com/community/i...wse/MIRTH-1442

Sure would like a solution without upgrading to a beta product. Does anyone have any ideas? Is the code fragment that is included in the bug report a workaround for Mirth v1.8.2? or is that a code fragment for v2.0.0?

The other part of the problem though is still a TCP issue but why doesn't mirth actually wait the 5 seconds for the ACK?