Tweet
Scratching my head on this one...
I had a bunch (1000+) of messages in persistent queues (Mirth 1.7.0.3191 on Linux) waiting for a receiver. I set up the same Mirth version on a Win2K box, defined a LLP receiver w/file writer out. When the channel was deployed, almost all of the messages went across as expected. However....
Twelve messages seem to be stuck with a QUEUED status on the sending machine. They're in four different channels, all of which have sent other messages w/o problem. Examples: one channel has 72 received, 71 sent, and 1 queued. Another channel has 25 received, 20 sent, and 5 queued.
If I filter down to queued messages in the dashboard, I can hit "reprocess message" on a stalled message, and a copy goes across, but the original stays in place.
In two of the channels, there are five queued messages in each. In each channel, the message with the oldest time stamp shows:
This can be explained due to the fact that while the 1000+ messages were being processed, I stopped and restarted the receiving channel a few times to make a few changes. The other four messages in the channel show no errors.
I've restarted both copies of Mirth - not getting any errors or even indications that it's trying to send these messages. As far as I can tell, they're simply being ignored by the sender.
Any ideas?
Thanks, Mike
I had a bunch (1000+) of messages in persistent queues (Mirth 1.7.0.3191 on Linux) waiting for a receiver. I set up the same Mirth version on a Win2K box, defined a LLP receiver w/file writer out. When the channel was deployed, almost all of the messages went across as expected. However....
Twelve messages seem to be stuck with a QUEUED status on the sending machine. They're in four different channels, all of which have sent other messages w/o problem. Examples: one channel has 72 received, 71 sent, and 1 queued. Another channel has 25 received, 20 sent, and 5 queued.
If I filter down to queued messages in the dashboard, I can hit "reprocess message" on a stalled message, and a copy goes across, but the original stays in place.
In two of the channels, there are five queued messages in each. In each channel, the message with the oldest time stamp shows:
ERROR-408: MLLP Connector error
ERROR MESSAGE: Socket write exception
java.net.ConnectException: Connection refused
ERROR MESSAGE: Socket write exception
java.net.ConnectException: Connection refused
I've restarted both copies of Mirth - not getting any errors or even indications that it's trying to send these messages. As far as I can tell, they're simply being ignored by the sender.
Any ideas?
Thanks, Mike
Comment