[
https://issues.apache.org/jira/browse/AMQ-7473?focusedWorklogId=432627&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-432627
]
ASF GitHub Bot logged work on AMQ-7473:
---------------------------------------
Author: ASF GitHub Bot
Created on: 11/May/20 04:49
Start Date: 11/May/20 04:49
Worklog Time Spent: 10m
Work Description: jbonofre commented on pull request #525:
URL: https://github.com/apache/activemq/pull/525#issuecomment-626467310
I need to interrupt the threads in the Jetty QueueThreadPool to shutdown the
http transport connector as fast as possible.
----------------------------------------------------------------
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: 432627)
Time Spent: 0.5h (was: 20m)
> Add stopOnError on lease database lock
> --------------------------------------
>
> Key: AMQ-7473
> URL: https://issues.apache.org/jira/browse/AMQ-7473
> Project: ActiveMQ
> Issue Type: Improvement
> Components: JDBC
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: 5.16.0, 5.15.13
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently, if the master broker loose the database connection (for instance,
> in case of network outage), it doesn't stop.
> Some users would prefer to stop the broker to avoid "dual" master (even for a
> short period of time).
> I propose to introduce {{stopOnError}} on the database lock to stop the
> broker as soon as the lease database can't be updated.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
