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

Error: could not prune message database

  • Filter
  • Time
  • Show
Clear All
new posts

  • Error: could not prune message database


    In reading some of the posts that refer to the error message, I elected to replace the derby db as several seem to suggest. I chose MSSQL Express. The installation was fine and getting everything put back after changing the underlying DB couldn't have been much easier.

    But I still get the same warning. Everything seems to be working and most of channels I have hold for 10 days, so it's not obvious yet if it's failing to purge or not - I would guess that would be the symptom.


    As I was writing this I was trying to understand if what I was asking was making sense - it seemed that my error message was different than others I had seen. So I dug a little deeper and actually looked at each channel.

    I discovered a channel that had an empty 'prune after days' field. Not sure how I managed that but adding a number there appears to have resolved my problem.

    The channel xml had
    [ul]<property name="max_message_age"></property>[/ul]

    should be
    [ul]<property name="max_message_age">10</property>[/ul]

    [ul][2008-05-09 13:31:43,302] WARN (com.webreach.mirth.plugins.messagepruner.MessageP runerService:226): could not prune message database
    java.lang.NumberFormatException: For input string: ""
    at java.lang.NumberFormatException.forInputString(Unk nown Source)
    at java.lang.Integer.parseInt(Unknown Source)
    at java.lang.Integer.parseInt(Unknown Source)
    at com.webreach.mirth.plugins.messagepruner.MessagePr unerService.execute(
    at 02)
    at org.quartz.simpl.SimpleThreadPool$ ([/ul]

    This has now become a non-question - but maybe will help someone else.