Limiting database size

[miguelsom]

I have Mirth configured with three channels:

Channel A

Source: LLP listener
Destination: Channel Writer (to Channel B )
Destination: Channel Writer (to Channel C)

Channel B

Source: Channel Reader
Destination: LLP sender (to REMOTESERVER1)

Channel C

Source: Channel Reader
Destination: LLP sender (to REMOTESERVER2)

The messages flow through Mirth just fine, but if REMOTESERVER1 or REMOTESERVER2 goes offline I want Mirth to queue all the messages that come in through Channel A so when the remote server comes back online it gets everything it missed. What is the best way to do this that uses the smallest amount of disk space necessary?

Thanks so much.

Post edited by: miguelsom, at: 09/19/2007 14:25

[albertosaez]

Re:Limiting database size

Active queues.

Messages are saved in the .mule dir

This is the only way in Mirth.

[miguelsom]

Re:Limiting database size

Is it possible to change the location of the .mule directory without reinstalling Mirth? I want the .mule directory to be on its own partition, not the system partition, to prevent the system partition from filling up.

It doesn't appear to be in the mule-boot.xml or mule-config.xml files.

Thanks.

[jbartels]

Re:Limiting database size

Could you just turn it into a symlink?

[albertosaez]

Re:Limiting database size

In conf/mirth.properties there is a property (mule.queue) with the location of the dir.

# mule
mule.config=mule-config.xml
mule.boot=mule-boot.xml
mule.queue=${mirthHomeDir}/.mule

[miguelsom]

Re:Limiting database size

Thank you very much. For Windows systems, would the syntax be:

mule.queue=F:/.mule

Thanks.

Post edited by: miguelsom, at: 09/26/2007 14:47

[rholmes]

Re:Limiting database size

Excuse me if this is a dumb question, but what is an "active queue"?

I want to set up a channel with an LLP source and HTTP destination, and I want Mirth to queue messages if the HTTP destination is unavailable and retry later. Would I use an active queue for that or...?

[albertosaez]

Re:Limiting database size

Sorry, but the queue is only avaiable for LLP sender.

I think They will avaiable for all destinations for 1.7

[chrisl]

Re:Limiting database size

Queuing across all destinations won't be in 1.7, but definitely in 2.0. We're going to try to post some alternatives to queuing to prevent message failures and guarantee delivery.