Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 45280 invoked from network); 27 Jan 2010 18:41:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 27 Jan 2010 18:41:56 -0000 Received: (qmail 37359 invoked by uid 500); 27 Jan 2010 18:41:56 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 37314 invoked by uid 500); 27 Jan 2010 18:41:56 -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 37304 invoked by uid 99); 27 Jan 2010 18:41:56 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Jan 2010 18:41:56 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Jan 2010 18:41:53 +0000 Received: from brutus.apache.org (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id BB4B0234C495 for ; Wed, 27 Jan 2010 10:41:32 -0800 (PST) Message-ID: <761570189.3151264617692765.JavaMail.jira@brutus.apache.org> Date: Wed, 27 Jan 2010 18:41:32 +0000 (UTC) From: "Gary Tully (JIRA)" To: dev@activemq.apache.org Subject: [jira] Commented: (AMQ-2567) Zero Prefetch not working In-Reply-To: <136920154.1641263479203425.JavaMail.jira@brutus.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: ae95407df07c98740808b2ef9da0087c X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/activemq/browse/AMQ-2567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=57177#action_57177 ] Gary Tully commented on AMQ-2567: --------------------------------- most of the artifacts are there but the release full tar or zip files still have not been updated for the 5.4-SNAPSHOT - need to check why hudson has not done it, it may be pending a full clean build. Some test failures were resolved today so it should be real soon. > Zero Prefetch not working > ------------------------- > > Key: AMQ-2567 > URL: https://issues.apache.org/activemq/browse/AMQ-2567 > Project: ActiveMQ > Issue Type: Bug > Components: Broker > Affects Versions: 5.3.0 > Environment: Unix/Windows, Java 1.6 > Reporter: Rudolf Janz > Assignee: Gary Tully > Fix For: 5.3.1, 5.4.0 > > Attachments: PrefetchSubscription.java, ZeroPrefetchConsumerTest.java, ZeroPrefetchConsumerTest.java > > > I have problems using the zero prefetch. The consumer starts prefetching messages after some receives. > > Our use case is, that we have a large computation which is split into smaller sub jobs. These jobs are sent via ActiveMQ to some processing nodes on different machines. The duration of jobs differs very much (10s to some minutes). The jobs are sent by decreasing estimated computation time. If one of the consumers which receives a large job prefetches some other jobs, these will be processed later. In the meantime the remaining consumers are idle, and the total computation time is much longer than necessary. > > I have modified the existing ZeroPrefetchConsumerTest to test for the problem (I have removed the other test methods). > > Two consumers (C1 and C2) are instantiated. These messages are sent: > 1,2,3,4,5,6,7,8,9 > > C1 reads 4 times, receives 1,2,3,4 -> this is correct > > now C2 reads, it receives 8 not 5, which is the next message in the queue. The reason is, that C1 prefetched 5, 6, 7, that should not have happened.(sometimes C1 only prefetches 5,6) > > The problem can be seen in the JMX Console as well, after a while, the first consumer has more than one dispatched message and the queue has an InflightCount of 3, although there are only two consumers! > > The last version that we used was 4.1.1, that worked. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.