Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <1299172463.1225734905811.JavaMail.jira@brutus>
Date: Mon, 3 Nov 2008 09:55:05 -0800 (PST)
From: "Gary Tully (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Issue Comment Edited: (AMQ-1757) ETA on AMQ5.2
In-Reply-To: <1873597940.1212091801167.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/activemq/browse/AMQ-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46986#action_46986 ] 

gtully edited comment on AMQ-1757 at 11/3/08 9:54 AM:
----------------------------------------------------------

current status: the following need to be resolved before the release:

1 Blocker:
AMQ-1824 

An Issue with lots of votes where patch seems valid:
AMQ-1191

And since this critical one just popped in with patch:
AMQ-1993

I will resolve AMQ-1824 today and the other two should follow with haste.
ETA - no more than two days provided all tests are consistently passing.

      was (Author: gtully):
    current status: the following need to be resolved before the release:

1 Blocker:
https://issues.apache.org/activemq/browse/AMQ-1824 

An Issue with lots of votes where patch seems valid:
https://issues.apache.org/activemq/browse/AMQ-1191

And since this critical one just popped in with patch:
https://issues.apache.org/activemq/browse/AMQ-1993

I will resolve AMQ-1824 today and the other two should follow with haste.
ETA - no more than two days provided all tests are consistently passing.
  
> ETA on AMQ5.2
> -------------
>
>                 Key: AMQ-1757
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1757
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 5.1.0
>            Reporter: vik dhawan
>            Assignee: Gary Tully
>            Priority: Minor
>             Fix For: 5.2.0
>
>
> Hi,
> Do we know the ETA on 5.2 Final release. I am not too much impressed with the 5.1 Release. i found 5.0 still more stable then 5.1. I run into selector problems Exceptions flying through the wire to my consumers all the time when i stress 5.1. 
> Only problem i see with 5.0 is Memory leak because of the old messages are not getting cleaned up. Which i have to purge manually every now and then other then that it works fine for me. 
> I am having a lot of hopes from 5.2 release. 
> Thanks!
> Vik

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