-
Notifications
You must be signed in to change notification settings - Fork 275
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setting to allow message pruning to prune ERRORED messages #3030
Comments
[http://www.mirthcorp.com/community/forums/showthread.php?t=14220] Imported Comment. Original Details: |
This is a serious issue for my shop as we have 8 boxes with perhaps 1000 channels and I really don't want to have to manually prune the old error messages. Has anyone come up with a workaround? Perhaps a SQL query that can get to the DB directly? Imported Comment. Original Details: |
We created a channel that goes through the MirthDB and sets the status from ERROR to SENT after a configurable interval; Then the regular Mirth Pruner picks them up to be deleted. Imported Comment. Original Details: |
Can you post that channel? Imported Comment. Original Details: |
I can't post the entire channel because we have other proprietary items present but below is the important part. Update the DB connection info and set the 'PurgeDays' Put this into a Javascript reader and schedule it to run nightly. var dbConn = DatabaseConnectionFactory.createDatabaseConnection(dbDriver, dbDatabase, dbUser, dbPassword); while (result.next())
} result.close(); Imported Comment. Original Details: |
I would recommend the priority on this issue be raised to high. Anyone with multiple Mirth instances or many channels would find management very difficult without this being fixed. Thank You Imported Comment. Original Details: |
Five years out and this is still should be a high priority issue. Brad come up with a good workaround, but what is the user need for an endless, perpetual accumulation of error log entries? Imported Comment. Original Details: |
Introduced in Mirth 3.0, MIRTH-2235 changes the message pruner behavior so that it no longer prunes ERRORED messages.
We would like to have the ability to toggle, per channel, whether or not pruning will delete ERRORED messages instead of leaving them in the database.
Imported Issue. Original Details:
Jira Issue Key: MIRTH-3116
Reporter: daigoba66
Created: 2014-01-16T04:34:02.000-0800
The text was updated successfully, but these errors were encountered: