Mailing-List: contact activemq-dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: activemq-dev@geronimo.apache.org
Message-ID: <16576154.1164398342743.JavaMail.root@brutus>
Date: Fri, 24 Nov 2006 11:59:02 -0800 (PST)
From: "Rob Davies (JIRA)" <jira@apache.org>
To: activemq-dev@geronimo.apache.org
Subject: [jira] Assigned: (AMQ-914) OutOfMemoryError
In-Reply-To: <30552071.1157622863162.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

     [ https://issues.apache.org/activemq/browse/AMQ-914?page=all ]

Rob Davies reassigned AMQ-914:
------------------------------

    Assignee: Rob Davies

> OutOfMemoryError
> ----------------
>
>                 Key: AMQ-914
>                 URL: https://issues.apache.org/activemq/browse/AMQ-914
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 4.0.1
>            Reporter: Daniel Aioanei
>         Assigned To: Rob Davies
>         Attachments: activemq.xml, jmxconsole.png
>
>
> I was doing some testing with a single MDP listening to a queue which had about 247300 messages, with a postgres backend. ActiveMQ server was started using the default activemq startup script (on Linux). In this configuration the cpu normally stays mostly idle and I described this behaviour in another bug report.
> Another issue came to surface when I tried to profile the client application with EclipseColorer to see why a single MDP can't hog my machine. But when I tried so, 4 OutOfMemoryError messages were logged by ActiveMQ server. Note that I was *not* profiling the server, but the client which is a totally different process.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira