Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 53453 invoked from network); 7 Mar 2011 08:28:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 7 Mar 2011 08:28:58 -0000 Received: (qmail 93025 invoked by uid 500); 7 Mar 2011 08:28:57 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 92948 invoked by uid 500); 7 Mar 2011 08:28:57 -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 92938 invoked by uid 99); 7 Mar 2011 08:28:57 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Mar 2011 08:28:57 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mzo@domdv.de designates 193.102.202.1 as permitted sender) Received: from [193.102.202.1] (HELO hermes.domdv.de) (193.102.202.1) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 07 Mar 2011 08:28:51 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=domdv.de; s=; h=Message-ID:In-Reply-To:References:Date:Subject:From:To: MIME-Version:Content-Type:Content-Transfer-Encoding; bh=W0Gwe+Es udPMzuTQK9vkSmhZlSxMjHd5ahGNfBCDCz4=; b=CJsnCZIPaVFE8anHieJacSeg DH7kCnjwVH81AIJs8tDzJnHzuE2K59WKD8nStsx8LI5X66tQdbzsU9Q5rEfAhgRs Mc+yRQ6XPqUWQzh1ND/YjLnxDHFLrcZZqp4URI0k Received: from [10.1.1.3] (helo=castor.lan.domdv.de) by zeus.domdv.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1PwVnq-000614-KT for users@activemq.apache.org; Mon, 07 Mar 2011 09:28:30 +0100 Received: from localhost ([127.0.0.1] helo=mail) by castor.lan.domdv.de with esmtp (Exim 4.69) (envelope-from ) id 1PwVnq-00005n-HP for users@activemq.apache.org; Mon, 07 Mar 2011 09:28:30 +0100 Received: from 10.5.1.183 by mail.lan.domdv.de with HTTP; Mon, 7 Mar 2011 09:28:30 +0100 (CET) Message-ID: <49419.10.5.1.183.1299486510.squirrel@mail.lan.domdv.de> In-Reply-To: References: <51641.10.5.1.183.1299237557.squirrel@mail.lan.domdv.de> Date: Mon, 7 Mar 2011 09:28:30 +0100 (CET) Subject: Re: AMQ-CMS - questions about threads/producerthreads in AMQ From: mzo@domdv.de To: users@activemq.apache.org User-Agent: SquirrelMail/1.4.10a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Checked: Checked by ClamAV on apache.org Hello Timothy, > Creating a Consumer object and registering a MessageListener will result > in messages being received in a separate thread, so there's not really > any need to create a new thread for your consumer. That explains the count of threads upon debugging. I already thought that may be the case, but its good to have it confirmed. > This is commonly done using a Blocking Queue, the producer thread waits > on something being enqueued and once it is, it dequeues it and does > whatever work is needed. But with a queue there would be a problem that if a subscriber gets offline due networking reasons, the messages would stack until a memory error occurs, or? And with a "Blocking Queue" you mean simply a sync Queue or? Are there samples for this? Thanks for the help! Best regards, amqBeginner