Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 33273 invoked from network); 9 May 2008 04:19:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 May 2008 04:19:02 -0000 Received: (qmail 16119 invoked by uid 500); 9 May 2008 04:19:03 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 16101 invoked by uid 500); 9 May 2008 04:19:03 -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 16090 invoked by uid 99); 9 May 2008 04:19:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 May 2008 21:19:03 -0700 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 (nike.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; Fri, 09 May 2008 04:18:09 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1JuK3y-0004EN-1z for users@activemq.apache.org; Thu, 08 May 2008 21:18:30 -0700 Message-ID: <17141146.post@talk.nabble.com> Date: Thu, 8 May 2008 21:18:30 -0700 (PDT) From: jaya_srini To: users@activemq.apache.org Subject: Need Help with blocking Producer! MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: jya_srini@Hotmail.com X-Virus-Checked: Checked by ClamAV on apache.org hi We are using ActiveMQ 5.0 release and observing the following on production. After a certain number of messages are sent the Activemq send blocks. The thread dump produced the following daemon prio=6 tid=0x3793f400 nid=0x1f28 waiting for monitor entry [0x38aff000..0x38affc98] java.lang.Thread.State: BLOCKED (on object monitor) at org.apache.activemq.ActiveMQSession.send(ActiveMQSession.java:1587) - waiting to lock <0x07c45ea0> (a java.lang.Object) at org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:226) at org.apache.activemq.ActiveMQMessageProducerSupport.send(ActiveMQMessageProducerSupport.java:268) at org.apache.activemq.ActiveMQTopicPublisher.publish(ActiveMQTopicPublisher.java:146) The connection URI looks like the following failover:(tcp://10.11.12.13:61616?wireFormat.maxInactivityDuration=-1) I am not sure if jms.useAsyncSend=true or jms.dispatchAsync=true will work with a failover transport. Can someone please help me troubleshoot this? Will increasing the memory limit on the broker help? -- View this message in context: http://www.nabble.com/Need-Help-with-blocking-Producer%21-tp17141146s2354p17141146.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.