geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevan Miller (JIRA)" <j...@apache.org>
Subject [jira] Commented: (GERONIMO-2455) Upgrade to new MX4J service release
Date Mon, 19 Mar 2007 01:43:09 GMT

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

Kevan Miller commented on GERONIMO-2455:
----------------------------------------

Great. Thanks Jason.

I doubt seriously that we'll ever have a 1.1.2. There'd be a bunch of updates required to
meet new Apache src header licensing requirements. It would take a lot of work. 

The 1.1.x build problems are pretty troubling, though. I would assume that an attempt to build
1.1.1 would encounter the same problems... 

> 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.


Mime
View raw message