[
https://issues.apache.org/jira/browse/AMQ-6307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15308544#comment-15308544
]
Timothy Bish commented on AMQ-6307:
-----------------------------------
Would be good to test against the latest release, and if the issue persists
then provide a test case to reproduce the problem.
> ActiveMQ broker shuts down shortly after losing lease
> -----------------------------------------------------
>
> Key: AMQ-6307
> URL: https://issues.apache.org/jira/browse/AMQ-6307
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.12.1
> Reporter: Brett Geer
>
> When using LeaseDatabaseLocker, the master releases it's lease as configured
> but when it tries to get it back and fails, it promptly shuts down. See below
> 2016-05-30 12:10:39,422 | INFO | xx Lease held by xx till Mon May 30
> 12:10:48 SAST 2016 | org.apache.activemq.store.jdbc.LeaseDatabaseLocker |
> ActiveMQ JDBC PA Scheduled Task
> 2016-05-30 12:10:39,423 | ERROR | localhost, no longer able to keep the
> exclusive lock so giving up being a master |
> org.apache.activemq.broker.LockableServiceSupport | ActiveMQ JDBC PA
> Scheduled Task
> 2016-05-30 12:10:39,427 | INFO | Apache ActiveMQ 5.12.1 (localhost,
> ID:xx160818-1464599650782-1:1) is shutting down |
> org.apache.activemq.broker.BrokerService | ActiveMQ JDBC PA Scheduled Task
> 2016-05-30 12:10:39,429 | INFO | socketQueue interuppted - stopping |
> org.apache.activemq.transport.tcp.TcpTransportServer | ActiveMQ Transport
> Server Thread Handler:
> tcp://0.0.0.0:61616?maximumConnections=10000&wireFormat.maxFrameSize=104857600&connectionTimeout=30000
> 2016-05-30 12:10:39,430 | ERROR | Could not accept connection :
> java.lang.InterruptedException |
> org.apache.activemq.broker.TransportConnector | ActiveMQ Transport Server
> Thread Handler:
> tcp://0.0.0.0:61616?maximumConnections=10000&wireFormat.maxFrameSize=104857600&connectionTimeout=30000
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
