web stats
Mirth Community - View Single Post - Database Reader Thread Count
View Single Post
Old 04-21-2017, 08:42 AM
collinsmj collinsmj is offline
OBX.1 Kenobi
Join Date: Jun 2014
Location: Southern USA
Posts: 27
collinsmj is on a distinguished road

I have taken your advice and checked the query from the SQL server directly. They query returns up to 10k records before a second can pass. The speed of the DB server isn't an issue. Blasting the channel doesn't seem to cause issue either. I have altered the query and interval polling though.

DB reader is now polling every 10 seconds.
The Queue Buffer Size is limited to 2500
The fetch size for the cursor is 1000 records
I limited the query to TOP 1000.

The MLLP destination now has a retry interval of 2 seconds instead of 10.
I regenerate the template. I have taken a guess that the network/end point may be the issue. I limited the destination to 5 threads so they would not be fighting over the network connections to the end point server.
The Queue buffer size is 1k.

I now see messages queue up to 2400 in the source queue. So, yay?

I now only see 4 or 5 messages queued in the destination side.

In the message view I am seeing entries for messages like the following.

Connector -- Status ---- Received Date ---------- Response Date
Source - Transformed - 2017-04-21 10:31:16:254 --
Dest 1 - SENT - 2017-04-21 11:02:76:148 -- 2017-04-21 11:02:76:748

There is 30 minutes difference between when the source received the message and when the destination received it. I assume this is due to the size of the source queue and how quickly the destinations can process the message over the network.

I am receiving a number of timeout waiting for response errors on messages even though I lowered the total number of destination queues. Should I select ignore response and/or increase the timeout? It is set to 5 seconds.
Reply With Quote