[jboss-jira] [JBoss JIRA] Commented: (JGRP-1011) Release JGroups 2.6.11

Tue Jul 14 17:58:29 EDT 2009

    [ https://jira.jboss.org/jira/browse/JGRP-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12476296#action_12476296 ] 

Richard Achmatowicz commented on JGRP-1011:
-------------------------------------------

Applied changes to testsuite for IPv6 testing.
Fixed ConnectionTableTest and GossipRouterTest to eliminate dependence on localhost.

> Release JGroups 2.6.11
> ----------------------
>
>                 Key: JGRP-1011
>                 URL: https://jira.jboss.org/jira/browse/JGRP-1011
>             Project: JGroups
>          Issue Type: Task
>    Affects Versions: 2.6.11
>            Reporter: Richard Achmatowicz
>            Assignee: Richard Achmatowicz
>
> This release is required for EAP 5.0  Beta testing. It may be that during the EAP testing cycle, further fixes will be required to JGroups.
> Here are the fixes which are so far logged against this release:
> Release Notes - JGroups - Version 2.6.11
> ** Bug
>    * [JGRP-912] - Failed to parse the jgroups.xml file
>    * [JGRP-984] - JGroups can not parse IPV6 literals in TCPPING protocol configuration
>    * [JGRP-985] - Flush and join problems during constant node failures and constant joins
>    * [JGRP-986] - FLUSH: relax event sequencing for a joining member
>    * [JGRP-997] - AUTH: incorrect matching of src against memberList
>    * [JGRP-1000] - COMPRESS corrupts some messages
>    * [JGRP-1006] - Shared transport: shunned multiple channels can not reconnect
> ** Task
>    * [JGRP-982] - Extend linux method of creating multicast socket to HP-UX
>    * [JGRP-1004] - GroupRequest: don't ignore InterruptedException
> Over and above these issues, this release needs to be throughly tested against IPv6 and this will require changes to the testsuite, as were applied to 2.4.6 (JGRP-951).
>  
> There are other IPv6-related issues which also should be addressed, in particular JGRP-956.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira