![]() ![]() 1rst : lost of messages, 2nd: all destinations too slow (waiting retries on unreachable destination)ĭoes this happen if you keep the queue under 1000? The max queue size in 2.0 defaults to 1000, so generally it will start blocking when it hits 1001. In fact: 2 use cases: First( one destination is not reachable with grants pb on it), Second (the host is not reachable: simple network failure). ![]() More over, with Mirth 2.0.1, in such situation, it becomes very difficult, sometime not possible to stop channel A without disable the channel & restart Mirth server. The same test was conducted with not problem on another Mirth 1.8.2 plateform. => we should obain 3550 messages received on channels B,C & D instead of 1073.Īfter a reset of the message table, clear statistics, deleting the mule queues and restart the server, a second test was conducted with the same result. ![]() (the "Run on update statement" = No (only for this test to simulate the load).Ĭhannel A was manualy stopped after 3550 messages received, with only 1073 queued (the error) and only 1073 distributed to each of the the reachable channels: B,C,D.įor the unreachabled channels: E,F: after a moment the Errored stated reached 1073 and Queued statistics on channel A reached to 0. Use case: (6 Mirth channels: A,B,C,D,E,F: with properties: store message data:yes, state:enabled, synchronize channel:yes)Ĭhannel A: (router) (source: hl7 2.5 jdbc Oracle) routing messages to channels B,C,D,E,F for all of them: destination type: channel Writer, Wait for channel response: no)Ĭhannel B: destination type: channel writer (channel name=none) (here only control channel)Ĭhannels C & D: destination type: MLLP with a host & port reachable.Ĭhannels E & F: destination type: MLLP with a host (temporarily) non reachable (as it is the case after a network failure)įor channels C,D,E,F: keep connection open: no, maximum retry count:6, use persistent queues:no, ACK Timeout: 15s Process HL7 ACK: Yes Send Response to: NoneĬhannel A was feeded (for test) by a 50 messages to read in table, polled every 5 secondes. Error routing messages with Mirth 2.0.1 channels (loss & no delivry for all reachable destinations while - and after that - one of the destinations is unreachable) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |