You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2014/03/19 17:51:44 UTC
[jira] [Commented] (AMQ-5109) "Soft deadlock" in
TransportConnection causes degraded performance in certain situations
[ https://issues.apache.org/jira/browse/AMQ-5109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13940659#comment-13940659 ]
Gary Tully commented on AMQ-5109:
---------------------------------
do you have any unit test that can easily demo the problem?
> "Soft deadlock" in TransportConnection causes degraded performance in certain situations
> ----------------------------------------------------------------------------------------
>
> Key: AMQ-5109
> URL: https://issues.apache.org/jira/browse/AMQ-5109
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.9.0
> Environment: HP-UX 11.31, RHEL 5/6. HP JDK 6/7, Oracle JDK 6/7
> Reporter: Nikolay Martynov
> Priority: Minor
> Labels: patch
> Attachments: TransportConnection.java.patch
>
>
> "Soft" deadlock occurres due to async stopping in case of starting/stopping lots of client connections (using jms template with standard connection factory, for example). ActiveMQ BrokerService gets frozen for 1 second trying to acquire the lock. As a result, already poor performance in case of unpooled connection factory further degrades by around 50%.
--
This message was sent by Atlassian JIRA
(v6.2#6252)