Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of gary.tully@gmail.com
 designates 209.85.128.184 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=ClasC8Dtq2hHKBQ0G+JFORou6Ulu3FE/83JKGrsBCQUFOKnbQ+ax80ncW1dInoLgEg
         U+aoOeQoib89PdGc9kFJtrqGBI0rJixZNUMXh1Cq5YMSdmlyqBcsD9/hHpbl7xwMxwUz
         6uib5tMfhqrq1nbwR2ukVLlZg3ckCWAdflK90=
Message-ID: <3a73c17c0812090650t78bb6262n999fcc6a8d2c13da@mail.gmail.com>
Date: Tue, 9 Dec 2008 14:50:00 +0000
From: "Gary Tully" <gary.tully@gmail.com>
To: users@activemq.apache.org
Subject: Re: Deadlock on producerWindow.waitForSpace()
In-Reply-To: <20913298.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20913298.post@talk.nabble.com>

with 5.2 right? that sounds plausible as failover is the default
transport and the default inactivity timeout is 30 seconds.
I guess is is possible that the producerAck gets lost, I don't think
there is a recovery cache on the broker sending side.
Do you see the failover transport doing a reconnect? Does it take more
than 30 seconds for the consumer to consume the messages and release
the memory.

If you can produce a failing junit test case please raise a jira issue
and attach it.


2008/12/9 Danielius Jurna <danielius.jurna@gmail.com>:
>
> I have one very slow consumer and activemq is configured for throttling. The
> problem is that my producer deadlocks on producerWindow.waitForSpace(). All
> my queues goes down to 0, but producer still waits for space.
> My ideas is that if connection to broker is lost, usageMutex.norifyAll() is
> never called. And it seems that failover connection closes connection on
> inactivity.
> Can any AMQ developer comment on how procuder throttling behaves on
> reconnect to broker?
> --
> View this message in context: http://www.nabble.com/Deadlock-on-producerWindow.waitForSpace%28%29-tp20913298p20913298.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>


-- 
http://blog.garytully.com

Open Source SOA
http://FUSESource.com