web stats
ACK timeout reporting - Mirth Community

Go Back   Mirth Community > Mirth Connect > Support

Reply
 
Thread Tools Display Modes
  #1  
Old 11-20-2008, 09:39 AM
sbacon sbacon is offline
What's HL7?
 
Join Date: May 2008
Posts: 5
sbacon
Default ACK timeout reporting

Hello,
I have configured an LLP sender with a 30000 ms ACK timeout (Ignore ACK is off, Process HL7 ACK is on).

On the 'Channel Messages screen I'm seeing the following:

2008-11-20 11:57:12.948 | TEST_LLP | ADT-A01 | Test Hospital | ERROR
2008-11-20 11:57:12.940 | Source | ADT-A01 | Test Hospital | TRANSFORMED

When I click on the top line and then the 'Errors' tab I see:

ERROR-408: MLLP Connector error
ERROR MESSAGE: Timeout waiting for ACK

Now judging by the Date difference between the log messages, it appears as if it's waited only .008 seconds before timeout, even though it is configured to wait up to 30 seconds.

Am I interpreting wrongly? Is this an issue with the logging? Is it indicative of the receiving end closing the channel? Bad setting for ACK timeout?

thanks
Steve
Reply With Quote
  #2  
Old 11-20-2008, 01:38 PM
albertosaez albertosaez is offline
 
Join Date: Sep 2006
Location: Valladolid, Spain
Posts: 842
albertosaez is an unknown quantity at this point
Default Re:ACK timeout reporting

HUMB.

I thinkd TMO ack is fine. Perhpas the logger time mark the moment the message is transformed, not the moment the error is set.
Reply With Quote
  #3  
Old 11-24-2008, 02:58 PM
sbacon sbacon is offline
What's HL7?
 
Join Date: May 2008
Posts: 5
sbacon
Default Re:ACK timeout reporting

HUMB?

The *real* issue I'm dealing with are "fast" timeouts waiting for ACKs.
I've got the timeout set to 5 minutes, and have tried both keeping the connection open and not keeping the connection open. However, the timeout error (ERROR-408) gets posted almost immediately after the message is sent (which is why I was wondering about the time printed in the error).
Any guess as to why it would get a timeout so fast? Is this indicative of the connection getting closed somewhere prematurely?

thanks again,
Steve
Reply With Quote
  #4  
Old 04-22-2009, 12:26 PM
michaelm michaelm is offline
OBX.1 Kenobi
 
Join Date: Dec 2008
Posts: 50
michaelm
Default

I know this thread is months old, but I am experiencing an identical issue to this. We have our ACK timeout set for several minutes, but as soon as I send a message I get an immediate error with the error description that it timed out waiting for ACK. Found this old thread with no resolution and was curious to see if there was any additional input regarding this problem. Thanks.
Reply With Quote
  #5  
Old 04-23-2009, 12:41 PM
dans dans is offline
Mirth Employee
 
Join Date: Apr 2007
Location: Irvine, CA
Posts: 590
dans is an unknown quantity at this point
Default

I have also experienced the "Timeout waiting for ACK" error. Often the error is caused by something other than waiting for ACK. For example, if the connection is dropped by the receiving system before Mirth gets an ACK you would get this error. Modifying the ACK timeout in Mirth will not make a difference in that case. I can't say for sure what you need to do to fix this problem since it is dependent on the receiving system. Try modifying some of the settings such as "Keep connection open" and see if that helps. Also check the specs for the receiving system and see if that provides any clues.
Reply With Quote
  #6  
Old 04-23-2009, 05:14 PM
steven_kehlet steven_kehlet is offline
Mirth Employee
 
Join Date: Jul 2007
Posts: 25
steven_kehlet
Default

I've filed a bug that will help with this issue. Please vote for:

http://www.mirthcorp.com/community/i...wse/MIRTH-1073
Reply With Quote
  #7  
Old 04-27-2009, 12:26 PM
michaelm michaelm is offline
OBX.1 Kenobi
 
Join Date: Dec 2008
Posts: 50
michaelm
Default

In our situation I enabled persistent queuing and this seems to have resolved the problem. As far as what was causing the errors in the first place I'm not sure, though I can confidently say it was not an error due to a timeout waiting on the ACK. I'll report back if the problem resurfaces.
Reply With Quote
  #8  
Old 04-27-2009, 11:00 PM
PhilT PhilT is offline
What's HL7?
 
Join Date: Oct 2008
Posts: 1
PhilT
Default

When you wrote "enabled persistent queuing...resolved the problem" do you mean:

"Changing the LLP Sender's destination parm 'Use Persistent Queues:' radio button from No to Yes resolved the problem"?
Reply With Quote
  #9  
Old 04-29-2009, 07:35 AM
michaelm michaelm is offline
OBX.1 Kenobi
 
Join Date: Dec 2008
Posts: 50
michaelm
Default

Phil, yes that's correct. We previously had the radio button set to No, and after setting it to Yes we see that messages going across the channel may go to queued for a moment, but so far all have sent successfully with zero "Timeout waiting for ACK" errors.
Reply With Quote
  #10  
Old 09-01-2009, 01:23 PM
mdishner mdishner is offline
What's HL7?
 
Join Date: Jun 2009
Location: Nashville TN
Posts: 3
mdishner is on a distinguished road
Default

I had the same issue and changing the channel to "Use Persistent Queues" fixed my problem.
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
FYI-- timeout on this site is too short! fitek General Discussion 5 05-19-2009 02:17 AM
Timeout with 1.8 magikbanana Support 5 02-26-2009 06:23 AM
Catching a timeout error dblodgett Support 0 01-19-2009 11:04 AM
transformer reporting error on wrong line JasonGriffith Support 4 10-17-2008 09:43 AM
Timeout waiting for ACK Alessandro Support 5 12-14-2007 12:12 PM


All times are GMT -8. The time now is 05:08 AM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2019, vBulletin Solutions, Inc.
Mirth Corporation