You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Luis Miguel De Bello (Jira)" <ji...@apache.org> on 2020/03/20 14:37:00 UTC
[jira] [Commented] (ARTEMIS-2670) Deadlock when running in cluster
mode
[ https://issues.apache.org/jira/browse/ARTEMIS-2670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17063412#comment-17063412 ]
Luis Miguel De Bello commented on ARTEMIS-2670:
-----------------------------------------------
We asked this question in [http://activemq.2283324.n4.nabble.com/Artemis-2-9-0-Deadlock-td4755709.html]
Now we are going to check the suggestion about increasing
auto-delete-queues-delay
Anyway it seems this an issue, I will update the Jira with the result of the suggested change
> Deadlock when running in cluster mode
> -------------------------------------
>
> Key: ARTEMIS-2670
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2670
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.9.0
> Reporter: Luis Miguel De Bello
> Priority: Major
> Attachments: Deadlock1, Deadlock2
>
>
> We are running Artemis 2.9.0 in production (AWS) with 4 instances creating a
> cluster (Jgroup) it usually works ok and was working fine but last week one of the
> instances got unhealthy, when login into the instance we noticed there was a
> deadlock and lot of connection in CLOSE_WAIT state. I am assuming the
> connection in CLOSE_WAIT are generated by this deadlock.
> I was checking the releases note for 2.10.0 - 2.10.1 - 2.11.0 and I read
> about two deadlock fixes but I don't think it is the same case.
> Our clients connect to the broker using Secure Web Socket (Mutual TLS).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)