web stats
Channel takes a long time to deploy after changes - Mirth Community

Go Back   Mirth Community > Mirth Connect > Support

Reply
 
Thread Tools Display Modes
  #1  
Old 11-30-2018, 03:24 PM
mpatterson mpatterson is offline
Mirth Newb
 
Join Date: Dec 2008
Posts: 9
mpatterson
Default Channel takes a long time to deploy after changes

Mirth Connect 3.4.2.8129

I have a channel with quite a lot (30+) destinations. There's a filter on each destination that check msg['PV1']['PV1.3']['PV1.3.1'].toString() to see if it matches. Most messages only match one of the destinations. All of the destinations are Channel Writers.

Whenever I make changes to this channel (usually to add a new destination), it takes 10 or more minutes for the channel to redeploy.

Even after it has redeployed, once I start sending messages to that channel again (there's usually a backload of 100+ messages) it takes 30 minutes to one hour to completely catch back up.

Once it's caught up it seems to work fine, but any time I make changes I'm looking at around an hour where I'm not able to send HL7 messages quickly.

The Server Log doesn't show any errors on the channel or any of the destination channels during this time.
Reply With Quote
  #2  
Old 12-02-2018, 04:54 AM
agermano agermano is offline
Mirth Guru
 
Join Date: Apr 2017
Location: Indiana, USA
Posts: 561
agermano is on a distinguished road
Default

Does the channel get stuck in the stopping or starting state?
Reply With Quote
  #3  
Old 12-02-2018, 11:47 AM
ricber ricber is offline
Mirth Guru
 
Join Date: Jun 2007
Location: Barcelona, Spain
Posts: 179
ricber
Default

Did you tried purging that channel?. Sometimes if channel holds a large amount of processed messages initial load becomes too much large.

Hope this helps,

RB
Reply With Quote
  #4  
Old 12-03-2018, 10:36 AM
mpatterson mpatterson is offline
Mirth Newb
 
Join Date: Dec 2008
Posts: 9
mpatterson
Default

Quote:
Originally Posted by agermano View Post
Does the channel get stuck in the stopping or starting state?
Both. Stopping takes around 5 minutes and starting takes around 5 minutes.

I do make sure that the source device is no longer connected to the TCP Listener of the Channel before re-deploying.
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


All times are GMT -8. The time now is 04:23 AM.


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