Return-Path: Delivered-To: apmail-geronimo-activemq-dev-archive@www.apache.org Received: (qmail 32276 invoked from network); 10 Nov 2006 10:26:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Nov 2006 10:26:23 -0000 Received: (qmail 33112 invoked by uid 500); 10 Nov 2006 10:26:34 -0000 Delivered-To: apmail-geronimo-activemq-dev-archive@geronimo.apache.org Received: (qmail 33095 invoked by uid 500); 10 Nov 2006 10:26:34 -0000 Mailing-List: contact activemq-dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: activemq-dev@geronimo.apache.org Delivered-To: mailing list activemq-dev@geronimo.apache.org Received: (qmail 33086 invoked by uid 99); 10 Nov 2006 10:26:34 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Nov 2006 02:26:34 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Nov 2006 02:26:22 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id A3B6A7142F7 for ; Fri, 10 Nov 2006 02:26:02 -0800 (PST) Message-ID: <17886813.1163154362664.JavaMail.root@brutus> Date: Fri, 10 Nov 2006 02:26:02 -0800 (PST) From: "james strachan (JIRA)" To: activemq-dev@geronimo.apache.org Subject: [jira] Commented: (AMQ-1028) AMQ Stops dispatching messages after a period of time without errors/warnings In-Reply-To: <12298615.1162885922493.JavaMail.root@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/activemq/browse/AMQ-1028?page=comments#action_37408 ] james strachan commented on AMQ-1028: ------------------------------------- A badly behaved consumer can't bring the entire messaging system down. Dealing with slow consumers on non-persistent messaging is a common problem though - either increase the RAM, enforce persistence or use slow consumer handling... http://incubator.apache.org/activemq/slow-consumer-handling.html > AMQ Stops dispatching messages after a period of time without errors/warnings > ----------------------------------------------------------------------------- > > Key: AMQ-1028 > URL: https://issues.apache.org/activemq/browse/AMQ-1028 > Project: ActiveMQ > Issue Type: Bug > Affects Versions: 4.0.2 > Environment: Os: Ubuntu Linux i386 - Java: J2RE SE 1.5.0_08-b03 > Reporter: Bas van Beek > Priority: Critical > Fix For: 4.0.2 > > > The ActiveMQ stand alone server seems to stop dispatching messages to topics after a period of time. > New clients can connect... new subscriptions to topics can be made... no errors are shown... messages are just not sent... including to and from the new clients... > No errors or warnings can be found in the ActiveMQ.log (even in debug mode) > JConsole doesn't show the new messages coming in (EnqueueCount doesn't change) > Stomp Protocol is used exclusively -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira