web stats
turning on persistent queue on http destination causes messages to fail - Mirth Community

Go Back   Mirth Community > Mirth Connect > Support

Reply
 
Thread Tools Display Modes
  #1  
Old 09-27-2011, 05:26 AM
satyam satyam is offline
Mirth Newb
 
Join Date: Oct 2010
Location: Hyderabad,India
Posts: 24
satyam is on a distinguished road
Default turning on persistent queue on http destination causes messages to fail

Hi,

We are using mirth 1.8.2 on linux environment.

We are processing lab orders and results ,the requirement is to process messages in order. We have a DB reader as source which picks up 10 messages at a time and then the destination is a http sender.

To maintain the order of messages we made the channel synchronized, but that did not guarantee order of messages at the destination. We read about using persistent queues to solve this problem.

we enabled the persistent queue for http sender. But the messages started failing, we had to turn the option off immediately.

Please let me know why messages stated failing when we turned on the persistent queue and what is the solution to it.

Any insight will be appreciated.
Reply With Quote
  #2  
Old 09-27-2011, 05:33 AM
Bostad Bostad is offline
Level 85 Channel Wizard
 
Join Date: Mar 2009
Location: Stratford Ontario
Posts: 712
Bostad is an unknown quantity at this point
Default

What error message are you getting when you turn queuing on?
__________________
I can be reached through gmail and Google Talk using davidrothbauer at gmail dot com
http://www.linkedin.com/pub/david-rothbauer/5/923/518
codeismydrug.wordpress.com
hl7coders.wordpress.com

Test all my code suggestions prior to implementation
Reply With Quote
  #3  
Old 09-27-2011, 07:07 AM
satyam satyam is offline
Mirth Newb
 
Join Date: Oct 2010
Location: Hyderabad,India
Posts: 24
satyam is on a distinguished road
Default

Quote:
Originally Posted by Bostad View Post
What error message are you getting when you turn queuing on?
I dont see any error in the mirth. The response map returns "QUEUED: Message is queued" message. not the actual response
Reply With Quote
  #4  
Old 09-27-2011, 07:19 AM
Bostad Bostad is offline
Level 85 Channel Wizard
 
Join Date: Mar 2009
Location: Stratford Ontario
Posts: 712
Bostad is an unknown quantity at this point
Default

Problem is either in your set up or on your receiving end.

If the "Test Connection" button fails, try pinging the destination.

If everything looks good on your end, then you need to check your route to the receiving host or the receiver itself.
__________________
I can be reached through gmail and Google Talk using davidrothbauer at gmail dot com
http://www.linkedin.com/pub/david-rothbauer/5/923/518
codeismydrug.wordpress.com
hl7coders.wordpress.com

Test all my code suggestions prior to implementation
Reply With Quote
  #5  
Old 09-27-2011, 08:42 AM
satyam satyam is offline
Mirth Newb
 
Join Date: Oct 2010
Location: Hyderabad,India
Posts: 24
satyam is on a distinguished road
Default

I drilled down more and found something which might help.

when I double click on the channel on dashboard , I get to see the channel messages screen. once I click on the http destination , I see a valid response under the mapping tab.

This means that Response is getting persisted in Response Map. but when I do responseMap.get('http destination1') I get "QUEUED: Message is queued".
Reply With Quote
  #6  
Old 09-28-2011, 12:13 AM
albertosaez albertosaez is offline
 
Join Date: Sep 2006
Location: Valladolid, Spain
Posts: 842
albertosaez is an unknown quantity at this point
Default

When you set a destination as queued, you can't use its response from the next destination, as you'll allways get the "QUEUED" status. (messages are queued per destination, not for all the endopint.

If you want to recover the response from the HTTP endpoint you need to route the response to another channel (using the "Send Response To" )
Reply With Quote
  #7  
Old 09-29-2011, 09:31 PM
satyam satyam is offline
Mirth Newb
 
Join Date: Oct 2010
Location: Hyderabad,India
Posts: 24
satyam is on a distinguished road
Default

Quote:
Originally Posted by albertosaez View Post
When you set a destination as queued, you can't use its response from the next destination, as you'll allways get the "QUEUED" status. (messages are queued per destination, not for all the endopint.

If you want to recover the response from the HTTP endpoint you need to route the response to another channel (using the "Send Response To" )
Thanks,

This answer helps.
Reply With Quote
Reply

Tags
http sender, order, persistent queue

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


All times are GMT -8. The time now is 12:13 PM.


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