[jira] [Created] (AMQ-5342) Deadlock in network of brokers simple architecture

["Claudio Santana (JIRA)" <ji...@apache.org>]

Claudio Santana created AMQ-5342:
------------------------------------

             Summary: Deadlock in network of brokers simple architecture
                 Key: AMQ-5342
                 URL: https://issues.apache.org/jira/browse/AMQ-5342
             Project: ActiveMQ
          Issue Type: Bug
          Components: Transport
    Affects Versions: 5.10.0, 5.9.1
         Environment: Ubuntu 12.04.5 LTS 

java version "1.7.0_60"
Java(TM) SE Runtime Environment (build 1.7.0_60-b19)
Java HotSpot(TM) 64-Bit Server VM (build 24.60-b09, mixed mode)

            Reporter: Claudio Santana
            Priority: Critical


With the following topology:

producer (1+ threads) --> broker1 <====>broker2 <--- consumer (2+ threads)

The producer has to be started up 1st and allow to enqueue a few messages, then the consumer threads are started.

The consumer shows messages to have received only one or two messages while the producer keeps on enqueueing messages normally. The scenario doesn't happen when the consumer threads are started 1st then the producers but if the consumers are disconnected and then reconnected the issue is visible again. I'm using the swiss army open wire example clients.

Consumer starting command line:

ant consumer -Durl=tcp://localhost:61627 -Dtopic=false -Dmax=200 -DparallelThreads=2 -DsleepTime=100

Producer starting command line:

ant producer -Durl=tcp://localhost:61626 -Dtopic=false -Dmax=400 -DparallelThreads=1 -DsleepTime=100 -DmessageSize=1000

Taking a thread dump I can see a deadlock. look at the attached file for details. I also attached the brokers configurations.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)