Mailing-List: contact activemq-users-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: activemq-users@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: domain of lists@nabble.com designates
 72.21.53.35 as permitted sender)
Message-ID: <5809009.post@talk.nabble.com>
Date: Mon, 14 Aug 2006 22:10:08 -0700 (PDT)
From: SimonInOz <simon.pearce@bt.com>
To: activemq-users@geronimo.apache.org
Subject: Re: ActiveMQ eats memory
In-Reply-To: <E0E2C049-D7A3-4B6D-B4AD-25459018C8FD@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <5757487.post@talk.nabble.com> <5759139.post@talk.nabble.com>
 <5789663.post@talk.nabble.com>
 <ec6e67fd0608140037u39eb07e8tbe000ba2f6d45ae1@mail.gmail.com>
 <5806117.post@talk.nabble.com>
 <E0E2C049-D7A3-4B6D-B4AD-25459018C8FD@gmail.com>


Hunting about, it seems the memory displayed by Windows Task Manager is
pretty shaky. I gather Windows basically likes GUI programs, and doesn't
handle non-GUI ones so well. It seems to have trouble with getting the
memory right. I think Java is ok.

I will try to catch ActiveMQ misbehaving, but it's challenging, as it's on a
prod server (not under my control) and they are understadably keen to get it
all working again and not "waste time" with debugging. They tend to reboot.
I'll see if I can set up jmap for them. But I'm not hopeful.

I see there may be some memory leaks in the allocation/deallocation of new
connections - I fear the monitor program we had running would make and
destroy connecxtions at a great rate, so perhaps watching it was causing
part of the problem (the cat was definitely dead).
-- 
View this message in context: http://www.nabble.com/ActiveMQ-eats-memory-tf2088958.html#a5809009
Sent from the ActiveMQ - User forum at Nabble.com.