Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <31793515.1173264081416.JavaMail.root@brutus>
Date: Wed, 7 Mar 2007 02:41:21 -0800 (PST)
From: "james strachan (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Commented: (AMQ-1190) JVM crash with AMQ 4.1.0 (jdk1.6.0 on
 linux)
In-Reply-To: <32028700.1173259581245.JavaMail.root@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/activemq/browse/AMQ-1190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38677 ] 

james strachan commented on AMQ-1190:
-------------------------------------

Cool - thanks for checking! :)

> JVM crash with AMQ 4.1.0 (jdk1.6.0 on linux)
> --------------------------------------------
>
>                 Key: AMQ-1190
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1190
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 4.1.0
>         Environment: Debian Sarge Linux 2.6.8-2-686-smp #1 SMP Tue Aug 16 12:08:30 UTC 2005 i686 GNU/Linux
> java version "1.6.0"
> Java(TM) SE Runtime Environment (build 1.6.0-b105)
> Java HotSpot(TM) Client VM (build 1.6.0-b105, mixed mode, sharing)
>            Reporter: Fredrik Jonson
>             Fix For: 4.1.1
>
>         Attachments: activemq.xml, hs_err_pid21535.log
>
>
> The activemq process (jvm) crashed after about a week of low intensive use on a default configured (out of the box) installation of activemq.
> With low intensive, I mean 
>  * about one queueconnection connecting/disconnecting per minute (24/7).
>  * A couple of constantly connected message listeners.
>  * less than 10 queues in use.
>  * Very few messages, say 10 per minute.
> I suspect this is related to the memory leak issues reported before (and that supposedly should be fixed in
> 4.1.1), but as it involved a jvm _crash_ i figured I'd report it anyway.
> Attached is the jvm crash report.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.