activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] [Resolved] (AMQ-5125) Broker and clients hang
Date Mon, 07 Jul 2014 21:55:35 GMT


Timothy Bish resolved AMQ-5125.

       Resolution: Fixed
    Fix Version/s: 5.11.0

Reviewed all the mailing list discussion and the threads dumps and the analysis is correct,
the lock cannot be the LevelDBStore object since that can lead to  a lock in the hawtDispatch
serialization thread runner if a task is modifying mutable state and needs to protect data
that also accessible on the public store API. 

Patch applied with thanks. 

> Broker and clients hang
> -----------------------
>                 Key: AMQ-5125
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.9.0, 5.10.0
>         Environment: Windows 7, Linux
> JAVA_HOME=C:\Program Files\Java\jdk1.7.0_07
> ActiveMQ 5.9.0 with LevelDB storage adapter enabled
>            Reporter: Albert Barmettler
>            Priority: Blocker
>             Fix For: 5.11.0
>         Attachments: AMQ-5125_made_synchronization_in_LevelDBStore_use_private_lock.5.9.2.patch,
Broker-threaddump-1396544622970.tdump, Clients-threaddump-1396544622970.tdump, VM.PNG, activemq.xml,
> JMS clients start to hang after a while in calls such as session.createObjectMessage().
Both the broker and the hanging clients can't be easily shut down when this happens - only
forcefully applied kill's do the job.
> I'm using queues and transactional sessions. All clients (producers and consumers) are
in the same Java VM. There is only one JMS connection between the application and the broker.
Each client has its own session, but they all share the same connection.
> Normally, the data directory of the LevelDb contains only a few log files. But in my
case, the number of log files is steadily increasing.
> Furthermore, I was able to track down the issue to following circumstance: The problem
only occurs, when consumers do a rollback instead of a commit when they receive the message.
The rollback / redelivery works as expected - the same message is received again after a previous
> As far as I can tell, the problem does not occur with KahaDb.
> I'll attach a test program that provokes the error. It sets up a few hundred queues,
consumers and producers. The consumers just receive the message and commit the session, but
they also do "random" rollbacks. It can be observed immediately that the number of files starts
increasing in the data directory. After a few minutes, the clients hang - sometimes sooner,
sometimes later. I'll also attach the config file for the broker.
> I am aware, that heavy rollbacking should not happen in normal operation. But from a
long term stability perspective, this is a blocker for us.

This message was sent by Atlassian JIRA

View raw message