[
https://issues.apache.org/jira/browse/ARTEMIS-2415?focusedWorklogId=301059&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-301059
]
ASF GitHub Bot logged work on ARTEMIS-2415:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 26/Aug/19 07:50
Start Date: 26/Aug/19 07:50
Worklog Time Spent: 10m
Work Description: michaelandrepearce commented on issue #2741:
ARTEMIS-2415 JDBCJournal miss pending tasks during shutdown
URL: https://github.com/apache/activemq-artemis/pull/2741#issuecomment-524756384
This is dangerous blocking stop. Also it doesnt solve the problem if the
broker is killed anyhow. As mentioned really the broker should clear up lose
ends on start up. This way it doesnt block stop and also fixes the case if its
killed.
Imagine you have a disk crash event, it would obviously block for a full 30s
until broker actually kills itself allowing failover
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 301059)
Time Spent: 3.5h (was: 3h 20m)
> JDBCJournal miss pending tasks during shutdown
> ----------------------------------------------
>
> Key: ARTEMIS-2415
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2415
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Reporter: Domenico Bruscino
> Priority: Major
> Attachments:
> downstream_run_16.filtered_testRegularMessagePersistenceDelayedConsumer.log
>
> Time Spent: 3.5h
> Remaining Estimate: 0h
>
> If server stops while having pending tasks in OperationContextImpl for
> JDBCJournal, server omits this tasks and prints a bunch of exceptions in the
> log, not exiting cleanly.
> Log of the situation from the test run is attached.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
