Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 11172 invoked from network); 14 Feb 2009 00:24:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 14 Feb 2009 00:24:45 -0000 Received: (qmail 78100 invoked by uid 500); 14 Feb 2009 00:24:44 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 78075 invoked by uid 500); 14 Feb 2009 00:24:44 -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 78064 invoked by uid 99); 14 Feb 2009 00:24:44 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Feb 2009 16:24:44 -0800 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.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; Sat, 14 Feb 2009 00:24:36 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1LY8KM-0002Ka-RZ for users@activemq.apache.org; Fri, 13 Feb 2009 16:24:14 -0800 Message-ID: <22007477.post@talk.nabble.com> Date: Fri, 13 Feb 2009 16:24:14 -0800 (PST) From: chrajanirao To: users@activemq.apache.org Subject: How does Producer flow control work with JDBC persitance? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: rajanicm@gmail.com X-Virus-Checked: Checked by ClamAV on apache.org I read below link about producer flow control but I am still confused about how it works when we have JDBC only persistance. http://activemq.apache.org/message-cursors.html I am noticing that ActiveMQ blocks even with JDBC only persistance but it doesn't make sense to me as to why it should block and how does it know when to block? Just to be clear, when I got this blocking problem, the database definitely didn't run out of space! After I removed couple of messages, it started taking in more messages (not just 2). I will be glad if someone explains how it works in this scenario. Thanks, Rajani. -- View this message in context: http://www.nabble.com/How-does-Producer-flow-control-work-with-JDBC-persitance--tp22007477p22007477.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.