You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Kevan Miller (JIRA)" <ji...@apache.org> on 2006/12/08 06:37:21 UTC
[jira] Commented: (GERONIMO-2455) Upgrade to new MX4J service
release
[ http://issues.apache.org/jira/browse/GERONIMO-2455?page=comments#action_12456701 ]
Kevan Miller commented on GERONIMO-2455:
----------------------------------------
Just checked the maven upload request that i submitted to get the new mx4j release uploaded to a maven repo. It got rejected for not being up to snuff. I'll have to look to see what's wrong...
> 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