Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 77DCAE1F6 for ; Tue, 18 Dec 2012 13:20:16 +0000 (UTC) Received: (qmail 86304 invoked by uid 500); 18 Dec 2012 13:20:14 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 86130 invoked by uid 500); 18 Dec 2012 13:20:13 -0000 Mailing-List: contact dev-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 dev@activemq.apache.org Received: (qmail 86090 invoked by uid 99); 18 Dec 2012 13:20:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Dec 2012 13:20:13 +0000 Date: Tue, 18 Dec 2012 13:20:13 +0000 (UTC) From: =?utf-8?Q?Tom=C3=A1=C5=A1_Martinec_=28JIRA=29?= To: dev@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (AMQ-4231) RWLock in queue does not used properly - performance improvement MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Tom=C3=A1=C5=A1 Martinec created AMQ-4231: ----------------------------------- Summary: RWLock in queue does not used properly - performance = improvement Key: AMQ-4231 URL: https://issues.apache.org/jira/browse/AMQ-4231 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.7.0, 5.4.2 Environment: fedora15; ubuntu 12.10; debian; probably independent Reporter: Tom=C3=A1=C5=A1 Martinec Priority: Minor The full story is in the user forum under title: Activemq 5.4.2 hangs when the temp disk usage is used The advantage of RW locks in Queue class is not used much. The cursors obje= cts are synchronized, so the readers cannot access the queued messages conc= urrently. The fixing effort of this issue may not be worth it, but you may consider t= his issue during fixing related issues. =20 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs For more information on JIRA, see: http://www.atlassian.com/software/jira