Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <10866793.1162929653904.JavaMail.jira@brutus>
Date: Tue, 7 Nov 2006 12:00:53 -0800 (PST)
From: "Kevan Miller (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Commented: (GERONIMO-2455) Upgrade to new MX4J service
 release
In-Reply-To: <16717270.1159793779574.JavaMail.root@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/GERONIMO-2455?page=comments#action_12447915 ] 
            
Kevan Miller commented on GERONIMO-2455:
----------------------------------------

I created a Maven upload request for 3.0.2 -- http://jira.codehaus.org/browse/MAVENUPLOAD-1220

Once available, I'll update our version number...

> Upgrade to new MX4J service release
> -----------------------------------
>
>                 Key: GERONIMO-2455
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-2455
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: buildsystem
>    Affects Versions: 1.1.1, 1.1, 1.0, 1.1.2, 1.2
>            Reporter: Kevan Miller
>         Assigned To: Kevan Miller
>             Fix For: 1.1.2, 1.2
>
>
> There's a timing hole in the mx4j Monitor implementation. In some scenarios, a Monitor will not receive an appropriate Notifcation after being started. The fix for the problem has been committed to mx4j head. I've run tests using a private build from mx4j head, all looks well.
> Once available, we should upgrade to the mx4j service release 3.0.2. 

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