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

["Jason Dillon (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/GERONIMO-2455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481976 ] 

Jason Dillon commented on GERONIMO-2455:
----------------------------------------

I've updated 1.2 to use 3.0.2... but 1.1 is still using m1 and these jars aren't in the m1 central repo.

We could add the jars to the 1.1's repository module and then update the version of mx4j to 3.0.2 too... but are we ever going to release 1.1.2?  The build for 1.1 is a *huge* mess... 

> Upgrade to new MX4J service release
> -----------------------------------
>
>                 Key: GERONIMO-2455
>                 URL: https://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, 1.2
>
>         Attachments: mx4j-3.0.2-bundle.jar, mx4j-jmx-3.0.2-bundle.jar, mx4j-remote-3.0.2-bundle.jar, mx4j-tools-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.
-
You can reply to this email to add a comment to the issue online.