[jira] [Closed] (AMQ-3399) Dead lock in the create connection with producerFlowControl true

["Timothy Bish (Closed) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMQ-3399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish closed AMQ-3399.
-----------------------------

    Resolution: Cannot Reproduce

I created a unit test to attempt to reproduce this using the 5.6 trunk code.  I could not reproduce any deadlocks.  If you can reproduce this using some version of the unit test please reopen and attach the updated testcase. 
                
> Dead lock in the create connection with producerFlowControl true
> ----------------------------------------------------------------
>
>                 Key: AMQ-3399
>                 URL: https://issues.apache.org/jira/browse/AMQ-3399
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Connector
>    Affects Versions: 5.5.0
>         Environment: JDK 1.6
> Spring 3.0.5
>            Reporter: Julien Gagnet
>         Attachments: AMQ3399Test.java, activemq-deadlock.zip, deadlock-thread.dump
>
>
> We are running a scenerio were we used Active MQ to decouple an Audit logging. We don't want to affect performance of the main application for audit purpose so we send audit event to a JMS queue. We would prefer stay up and lose message if we cannot process them fast enough. So our config got: 
> a memoryUsage set quite high (200mb)
> a sendFailIfNoSpace set to true
> and a producerFlowControl set to true
> Under those configuration and when the queue is full we get into a dead lock situation.
> We've manage to reproduce the problem in a small application to demonstrate the problem - how do we attach example?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira