Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (herse.apache.org: domain of james.strachan@gmail.com
 designates 64.233.182.191 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=pGR6J4SFyb5ovZ940VtqAd9M9mhbz2zfh7xz6BZBIVYfBrI/B7e7fPEO50Mg0xuyIJSpfvXtZ022I1lHYTEaUScnt6CUYrpGWEP7I/G+oHEvtFdykDb7rof7JVIT8e4TNqzM7wYgWgE10T77MYeeiA5GXw0MhfA2cnmC0pFV7zg=
Message-ID: <ec6e67fd0702222206k4cdb45b1ufc516b0ccb768c90@mail.gmail.com>
Date: Fri, 23 Feb 2007 06:06:07 +0000
From: "James Strachan" <james.strachan@gmail.com>
To: users@activemq.apache.org
Subject: Re: Memory usage increase after client power failure
In-Reply-To: <200702220627.17159.tomtor@xs4all.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <9014365.post@talk.nabble.com>
	 <ec6e67fd0702190539s2fcad69k70d91ed5e8593f15@mail.gmail.com>
	 <9088099.post@talk.nabble.com> <200702220627.17159.tomtor@xs4all.nl>

Many thanks for catching this Tom - patch applied in trunk.

Eric - do you want to try buiding the 4.2-trunk and seeing if this
fixes your issue?
http://activemq.apache.org/source.html

On 2/22/07, Tom Vijlbrief <tomtor@xs4all.nl> wrote:
> Op woensdag 21 februari 2007 21:05, schreef eccrowe:
>
> > It should also be noted that after a client power off, the remaining active
> > clients very quickly stop receiving their messages.  Server logs still
> > appear to be sending messages but the enqueue count is not increasing in
> > the jmx-console and eventually the server logs stop logging send events as
> > well. All of this with jmx-console indicating 0 memory usage.
> >
> > Are there any default settings which have changed or have been added
> > between 4.0-RC2 and 4.1 which may be causing these additional issues?
> >
>
> There is (was) a problem with dying (Stomp) clients for which
> I created a patch:
>
> https://issues.apache.org/activemq/secure/attachment/15322/patchInactivityMonitor.txt
>
> This could be related to your problem...
>
> ================
> The InactivityMonitor code reads:
>
> public void onException(IOException error) {
> if( monitorStarted.get() ) { stopMonitorThreads();
> getTransportListener().onException(error); }
> }
>
> So if monitorStarted is false the EOFException is completely ignored
> and not propagated to higher layers!
>
> I assume it should be:
>
> public void onException(IOException error) {
> if( monitorStarted.get() ) { stopMonitorThreads(); }
> getTransportListener().onException(error); // tom.vijlbrief
> }
> ==============
>
>
>
> Tom
>


-- 

James
-------
http://radio.weblogs.com/0112098/