Upgrade to JGroups 2.4.1.SP1

[brian.stansberry]

Bela's released a 2.4.1.SP1 (see http://jira.jboss.com/jira/browse/JGRP?report=com.atlassian.jira.plugin.system.project:changelog-panel) that's going in AS 4.2.0. I'd like to move AS trunk to it as well, but the build fails with:

C:\dev\jboss\jboss-head\build\build-thirdparty.xml:143: A versioning problem exi
sts:
Component: jgroups is at version: 2.4.1.SP1
 but it is also required to be compatible with: [Compatible@12b6c89{id=null, ver
sion=2.4.1}]
 by: jboss/messaging

Seems we need a process for coordinating these kinds of moves. What do you guys need to be able to do declare compatiblity?

[clebert.suconic]

I just added compatibility on repository.jboss.org/jboss/messaging

I don't know how it will take to be replicated though.


Also... we will release JBossMessaging.1.2.0.SP1 this week...

do you think I should upgrade JGroups on this release as well? What were the main fixes? (any links?)

[clebert.suconic]

What were the main fixes? (any links?)

Duh! :-D :::

Bela's released a 2.4.1.SP1 (see http://jira.jboss.com/jira/browse/JGRP?report=com.atlassian.jira.plugin.system.project:changelog-panel ) that's going in AS 4.2.0. I'd like to move AS trunk to it as well, but the build fails with:

My fingers were faster than my eyes :-)...

But I keep the question... should I upgrade 1.2.0.SP1 to use this new SP release?

[clebert.suconic]

Also....


I have tested this new release with our clustering testcases.. everything looks fine.

[brian.stansberry]

Thanks, Clebert.

JGroups releases aren't interoperable (i.e. a server running 2.4.1 will have issues clustering with one on 2.4.1.SP1), so I don't know if you want to switch versions in an SP. That's somewhat a policy decision for the Messaging team.

IMO the most significant thing in 2.4.1.SP1 for normal usage is the fix for http://jira.jboss.com/jira/browse/JGRP-422. We saw the error message reported on that JIRA pretty frequently during shutdown of an AS instance; I assume messaging users would as well. The effect of the problem is just the ERROR message; the shutdown happens correctly.