I have had two clients on 3.0.3.7171 in the last two weeks experience the following issue:
During normal steady-state operation, messages in a channel stop processing through some of the destinations (2 destinations in each case, but not always the same destination ids). So before I see:
Source
Destination 1
Destination 2
Destination 3
Destination 4
And once this starts occuring I see:
Source
Destination 3
Destination 4
The missing destinations are just that - missing. These are channel writer and file writer in one of my cases, both channel writers in the other. The message was not sent to the destination channel or file system.
Redeploying the channel and then reprocessing the message then shows all destinations correctly.
I cannot find any entry related within mirth.log at the time the issue began.
Both of these were on Windows servers with a MS SQL database. Both channels are for inbound ADT, processing > 50k transactions per day.
Has anyone else seen something like this?
During normal steady-state operation, messages in a channel stop processing through some of the destinations (2 destinations in each case, but not always the same destination ids). So before I see:
Source
Destination 1
Destination 2
Destination 3
Destination 4
And once this starts occuring I see:
Source
Destination 3
Destination 4
The missing destinations are just that - missing. These are channel writer and file writer in one of my cases, both channel writers in the other. The message was not sent to the destination channel or file system.
Redeploying the channel and then reprocessing the message then shows all destinations correctly.
I cannot find any entry related within mirth.log at the time the issue began.
Both of these were on Windows servers with a MS SQL database. Both channels are for inbound ADT, processing > 50k transactions per day.
Has anyone else seen something like this?
Possible bug in 3.0.3.7171 - missing destinations
0 commentaires:
Enregistrer un commentaire