We're trying to get a hand on queuing as we thought we had our setting correct on a Web Service Sender connector but when the system is unavailable we end up with messages in an ERROR state. We currently have Queue Messages = Always, Rotate = checked, Retry Count Before Queue/Error = 1 (default but is dithered when Always is checked so should not be applicable), Retry Interval = 6000 and Queue Threads = 20.
I haven't been able to find anything solid as far as documentation goes but my understanding is that if you have a destination set to Never and the receiving destination is unavailable and you had the retry count set to 0 the current message would process over and over again dependant on the retry interval (while messages backed up behind it) If, during that time, the server suffered a hard failure and rebooted that message is "lost" as well as all messages behind it. Otherwise there would be no point to the queuing (aside from having multiple destinations and allowing processing to continue). Is this statement true?
We are on MirthConnect 3.1.1.7461 and the channel is attached.
I haven't been able to find anything solid as far as documentation goes but my understanding is that if you have a destination set to Never and the receiving destination is unavailable and you had the retry count set to 0 the current message would process over and over again dependant on the retry interval (while messages backed up behind it) If, during that time, the server suffered a hard failure and rebooted that message is "lost" as well as all messages behind it. Otherwise there would be no point to the queuing (aside from having multiple destinations and allowing processing to continue). Is this statement true?
We are on MirthConnect 3.1.1.7461 and the channel is attached.
Message Reliability and Queuing
0 commentaires:
Enregistrer un commentaire