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 1EB1A9E53 for ; Sun, 5 Feb 2012 15:18:19 +0000 (UTC) Received: (qmail 10728 invoked by uid 500); 5 Feb 2012 15:18:18 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 10595 invoked by uid 500); 5 Feb 2012 15:18:17 -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 10587 invoked by uid 99); 5 Feb 2012 15:18:17 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 05 Feb 2012 15:18:16 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 05 Feb 2012 15:18:15 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id F0E571A4939 for ; Sun, 5 Feb 2012 15:17:53 +0000 (UTC) Date: Sun, 5 Feb 2012 15:17:53 +0000 (UTC) From: "William (Created) (JIRA)" To: dev@activemq.apache.org Message-ID: <1063665997.13073.1328455073988.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Created] (AMQ-3697) Messages not delivered to connecter consumer MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org Messages not delivered to connecter consumer -------------------------------------------- Key: AMQ-3697 URL: https://issues.apache.org/jira/browse/AMQ-3697 Project: ActiveMQ Issue Type: Bug Components: Broker Affects Versions: 5.5.1 Environment: SunOS 5.10 Generic_142909-17 sun4v sparc SUNW,T5140 Reporter: William Priority: Critical I am using ActiveMQ 5.5.1 and sometimes messages are not dispatched to connected consumers. A single broker is used. No transaction and no persistence is used for message delivery. Message consumers are spring template made for topic consuption. Optimize acknowledge is enabled and acknowledgment is auto. By Looking at JMX Topic MBean I can see that messages are received but not dispatched (and of course non depueued). I noticed that disptatched count was 100 more than dequeue count. >From JMX : * Received count : 4502 * Dispatched count : 3756 * Dequeued count : 3656 If a start a new consumer on the same topic, the messages are only dispatched to the new consumer while the older one is still seen as connected (consumer count on the mbean is 2). Once the problem appear the only solution is to restart the consumer or the activemq instance. It seems that even if the consumer is seen as connected, messages as not dispatched for an unknow reason. Which logs can I enable in order to diagnose the problem (on activemq side and/or consumer side) ? I have already made a thread dump, not thread are blocke -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira