Announcement

Collapse

Mirth Connect 3.12.0 Released!

Mirth Connect 3.12.0 is now available as an appliance update and on our GitHub page. This release includes database performance improvements, improves visual HL7 representation, message pruning, keystore handling, PDF generation, community contributions, and fixes several security vulnerabilities. This release also contains many improvements to commercial extensions. See the release notes for the list of fixes and updates.

Download | See What's New | Upgrade Guide | Release Notes

For discussion on this release, see this thread.
See more
See less

DB very, very busy AFTER a SELECT

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • DB very, very busy AFTER a SELECT

    Hello all,

    I have a channel that reads the database, makes a select with an immence resultset and creates a batch of many HL7-mesages (sort of 500) and sends them to another channel, that sends every single message from the batch to a destination using LLP. The problem is - although the first channel has already done the SELECT and has send the batch of messages to the second one, the database is still very, very busy while the second channel sends the messages.

    I tried result.close() and dbConnection.close() to call the garbage collector but they didn't change anything.

    Does anyone have any advise or idea?

    Thanks for your help!

    The first channel is in the attachment.

    Svetlomir DBReaderAL1_ITB_2008_09_20.xml (15077 bytes)
Working...
X