[MIRTH-3568] Manually stopping the data pruner while archiving generates a
server log error Created: 09/Jan/15 Updated: 20/Jan/15 Resolved: 14/Jan/15
Status:
Project:
Component/s:
Affects
Version/s:
Fix Version/s:
Closed
Mirth Connect
Server
3.0.0, 3.0.1, 3.0.2, 3.0.3, 3.1.0, 3.1.1
Type:
Reporter:
Resolution:
Labels:
Remaining
Estimate:
Time Spent:
Original
Estimate:
Bug
Brent Moen
Fixed
None
Not Specified
3.2.0
Priority:
Assignee:
Votes:
Minor
Brent Moen
0
Not Specified
Not Specified
Description
The error message states that there are 3 retries remaining, when in fact it has stopped.
Comments
Comment by Brent Moen [ 14/Jan/15 ]
Fixed exception handling in the data pruner so that manually stopping the data pruner no longer
generates an error in the server log. Instead, a "Data Pruner Halted" event will not correctly
appear in the event browser.
Comment by Jaysen Patton [ 20/Jan/15 ]
Verified the error message occurred in affected versions but was fixed in 3.2.
Simply created a channel with a JS Reader returning a simple string. Polling frequency was set
to 1ms. After some time, I pruned messages and stopped the service.
Generated at Tue Feb 09 12:36:55 PST 2016 using JIRA 6.2.7#6265sha1:91604a8de81892a3e362e0afee505432f29579b0.