activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "james strachan (JIRA)" <>
Subject [jira] Resolved: (AMQ-1190) JVM crash with AMQ 4.1.0 (jdk1.6.0 on linux)
Date Wed, 07 Mar 2007 10:25:21 GMT


james strachan resolved AMQ-1190.

       Resolution: Fixed
    Fix Version/s: 4.1.1

This looks more like a JVM bug as the JVM itself terminated with an internal error - so its
not an ActiveMQ error. 

Please could you post the log to the sun bug tracker mentioned at the top of the log...

BTW its no big deal if you want to create connections every few minutes, but ideally you'd
cache/pool them...

> JVM crash with AMQ 4.1.0 (jdk1.6.0 on linux)
> --------------------------------------------
>                 Key: AMQ-1190
>                 URL:
>             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.

View raw message