activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-6589) Broker hangs by shutdown after loosing exclusive lock
Date Wed, 31 May 2017 12:10:04 GMT

    [ https://issues.apache.org/jira/browse/AMQ-6589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031062#comment-16031062
] 

Gary Tully commented on AMQ-6589:
---------------------------------

Please attach a thread dump of the broker in this "cannot shutdown" state. It should be possible
to see what operations are pending on those connections that are preventing the stop from
completing.

> Broker hangs by shutdown after loosing exclusive lock
> -----------------------------------------------------
>
>                 Key: AMQ-6589
>                 URL: https://issues.apache.org/jira/browse/AMQ-6589
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.13.4
>         Environment: Linux
>            Reporter: Andrei Shakirin
>         Attachments: activemq-old-master-anonymized.log, activemq.xml
>
>
> 1) Configuration: ActiveMQ brokers are configured with shared store (NFS) and shared
file locker with configured lockAcquireSleepInterval:
> {code:xml}
> 	<persistenceAdapter>
> 		<mKahaDB directory="amq-share/" lockKeepAlivePeriod="10000">
>                 <locker>
>                      <shared-file-locker lockAcquireSleepInterval="15000"/>
>                 </locker>
> 		<filteredPersistenceAdapters>
> 			<filteredKahaDB perDestination="true">
> 				<persistenceAdapter>
> 					<kahaDB checkForCorruptJournalFiles="true" checksumJournalFiles="true" />
> 				</persistenceAdapter>
> 			</filteredKahaDB>
> 		</filteredPersistenceAdapters>
> 		</mKahaDB>
> 	</persistenceAdapter>
> {code}
> 2) Workflow
> The master broker looses exclusive lock and tries to shutdown, it is reported in the
log file:
> {code}
> 2017-01-31 16:30:45,921 | INFO  | Lock file /CE/activemq/lock, locked at Thu Jan 05 01:14:11
CET 2017, has been modified at Tue Jan 31 16:30:45 CET 2017 | org.apache.activemq.util.LockFile
| ActiveMQ Lock KeepAlive Timer
> 2017-01-31 16:30:45,921 | ERROR | hostXXX, no longer able to keep the exclusive lock
so giving up being a master | org.apache.activemq.broker.LockableServiceSupport | ActiveMQ
Lock KeepAlive Timer
> 2017-01-31 16:30:45,924 | INFO  | Apache ActiveMQ 5.13.4 (hostXXX, ID:xxx-36540-1483575278364-0:1)
is shutting down | org.apache.activemq.broker.BrokerService | ActiveMQ Lock KeepAlive Timer
> {code}
> 3) Problem
> Broker hangs during shutdown, I see a lot of messages like:
> {code}
> The connection to 'tcp://xxx:55057' is taking a long time to shutdown.
> {code}
> The problem happens only in case of shutdown after loosing exclusive log, normal shutdown
works fine.
> I see some other defects with this problem: AMQ-3435, AMQ-3293, AMQ-4073, but all of
them have to be fixed in AMQ 5.13.4.
> What can be the reason of this problem?
> Note: the connections were created from "old" AMQ clients (5.7.0). Could the problem
related with that?
> Complete log file and configuration are attached.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message