#11
|
|||
|
|||
![]()
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. |
#12
|
|||
|
|||
![]()
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
__________________
Nico Vannieuwenhuyze Amaron.be |
#13
|
|||
|
|||
![]() Quote:
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? |
![]() |
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
FYI-- timeout on this site is too short! | fitek | General Discussion | 5 | 05-19-2009 03:17 AM |
Timeout with 1.8 | magikbanana | Support | 5 | 02-26-2009 07:23 AM |
Catching a timeout error | dblodgett | Support | 0 | 01-19-2009 12:04 PM |
transformer reporting error on wrong line | JasonGriffith | Support | 4 | 10-17-2008 10:43 AM |
Timeout waiting for ACK | Alessandro | Support | 5 | 12-14-2007 01:12 PM |