You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@geronimo.apache.org by "Donald Woods (JIRA)" <ji...@apache.org> on 2007/01/02 17:11:28 UTC

[jira] Updated: (GERONIMO-2455) Upgrade to new MX4J service release

     [ http://issues.apache.org/jira/browse/GERONIMO-2455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Donald Woods updated GERONIMO-2455:
-----------------------------------

    Attachment: mx4j-remote-3.0.2-bundle.jar
                mx4j-jmx-3.0.2-bundle.jar
                mx4j-3.0.2-bundle.jar

> 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.0, 1.1, 1.1.1, 1.1.2, 1.2
>            Reporter: Kevan Miller
>         Assigned To: Kevan Miller
>             Fix For: 1.1.2
>
>         Attachments: mx4j-3.0.2-bundle.jar, mx4j-jmx-3.0.2-bundle.jar, mx4j-remote-3.0.2-bundle.jar
>
>
> 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