Return-Path: X-Original-To: apmail-activemq-issues-archive@minotaur.apache.org Delivered-To: apmail-activemq-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 96B1318689 for ; Tue, 17 Nov 2015 16:21:12 +0000 (UTC) Received: (qmail 38432 invoked by uid 500); 17 Nov 2015 16:21:12 -0000 Delivered-To: apmail-activemq-issues-archive@activemq.apache.org Received: (qmail 38373 invoked by uid 500); 17 Nov 2015 16:21:12 -0000 Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list issues@activemq.apache.org Received: (qmail 38340 invoked by uid 99); 17 Nov 2015 16:21:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Nov 2015 16:21:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id DAC522C14FB for ; Tue, 17 Nov 2015 16:21:11 +0000 (UTC) Date: Tue, 17 Nov 2015 16:21:11 +0000 (UTC) From: "ASF subversion and git services (JIRA)" To: issues@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMQ-6046) Concurrent access to a Transport from WebSocket client can deadlock MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMQ-6046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15008945#comment-15008945 ] ASF subversion and git services commented on AMQ-6046: ------------------------------------------------------ Commit caa6b8e2539132999045c3fbbd627a2dc6d0885c in activemq's branch refs/heads/master from [~tabish121] [ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=caa6b8e ] https://issues.apache.org/jira/browse/AMQ-6046 Prevent concurrent access to protocol handlers which can lead to transport level deadlocks. > Concurrent access to a Transport from WebSocket client can deadlock > ------------------------------------------------------------------- > > Key: AMQ-6046 > URL: https://issues.apache.org/jira/browse/AMQ-6046 > Project: ActiveMQ > Issue Type: Bug > Components: MQTT, stomp, Transport > Affects Versions: 5.12.0, 5.12.1, 5.11.3 > Reporter: Timothy Bish > Assignee: Timothy Bish > Fix For: 5.13.0 > > > WebSocket connections can encounter a deadlock when the Jetty side allows for concurrent access to the Transport instance that forwards commands onto the broker core. This seems to happen mostly in cases where a message or other action is incoming at the same time as Jetty is closing the connection due to idle timeout or some other cause. -- This message was sent by Atlassian JIRA (v6.3.4#6332)