You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Jason Dillon (JIRA)" <ji...@apache.org> on 2007/03/19 21:46:32 UTC
[jira] Closed: (GERONIMO-2455) Upgrade to new MX4J service release
[ https://issues.apache.org/jira/browse/GERONIMO-2455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason Dillon closed GERONIMO-2455.
----------------------------------
Resolution: Fixed
Fix Version/s: (was: 1.1.2)
Assignee: Jason Dillon (was: Kevan Miller)
Aight, then I'm updating this issue to remove the fix for 1.1.2 and closing.
And you are right about the 1.1.1 build... w/o some modifications and extra artifacts in your repo this baby won't build. We need to work on fixing this for future builds... but you knew that ;-)
> 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: Jason Dillon
> Fix For: 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.