Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 32695 invoked from network); 19 May 2009 13:02:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 19 May 2009 13:02:19 -0000 Received: (qmail 19110 invoked by uid 500); 19 May 2009 13:02:18 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 19073 invoked by uid 500); 19 May 2009 13:02:18 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 19063 invoked by uid 99); 19 May 2009 13:02:18 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 May 2009 13:02:18 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 May 2009 13:02:08 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1M6Ox1-0002Ry-Nn for users@activemq.apache.org; Tue, 19 May 2009 06:01:47 -0700 Message-ID: <23615938.post@talk.nabble.com> Date: Tue, 19 May 2009 06:01:47 -0700 (PDT) From: dlindquist To: users@activemq.apache.org Subject: Bug Alert: Durable Subscriber Name Length / KAHA Explosions MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: junk@dlindquist.com X-Virus-Checked: Checked by ClamAV on apache.org This is a bug heads-up for anyone who might be running into the same problem. (I'm building a simplified example for bug submission, but in the meantime, to help anyone with similar problems.) If you: * Have 2 or more topics with a durable subscriber * The combination of clientid + subscribername has a length > 99 characters * The broker has 'persistent=true' * You have a reasonable volume of requests coming through Then the 'kaha' store (default, I guess?) will blow up on every single message send with exceptions either like: "could not locate file data-something--1" (note double-dash -- index is '-1') OR: "java.lang.IndexOutOfBoundsException" (Note that the exact number of characters in the limit has not been conclusively proven -- once I finish the bug submission example, I'll know for sure. Additionally, the exact circumstances has not been completely proven, but the list above seems to produce it.) This is an exceptionally nasty one as it only applies to the file-store -- the in-memory handling of stuff seems just fine (no such limits) -- if you say 'persistent=false', there will be no issues. Additionally, there is nothing to tell you WHY things are blowing up, or to reject names that are too long -- it appears that it just makes an assumption on the file-store side. I have NOT yet tested whether this same 99-character limitation applies to topic names, but I am suspicious that it may. Hopefully this prevents someone else from spending unfruitful hours banging their head against a wall ;-) -- View this message in context: http://www.nabble.com/Bug-Alert%3A-Durable-Subscriber-Name-Length---KAHA-Explosions-tp23615938p23615938.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.