[ https://jira.jboss.org/jira/browse/JGRP-1011?page=com.atlassian.jira.plug... ] Richard Achmatowicz updated JGRP-1011: -------------------------------------- Description: 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. was: This release is required for EAP. 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 relared 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

[ https://jira.jboss.org/jira/browse/JGRP-1011?page=com.atlassian.jira.plug... ] Bela Ban updated JGRP-1011: --------------------------- Fix Version/s: 2.6.11 -- 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

[ https://jira.jboss.org/jira/browse/JGRP-1011?page=com.atlassian.jira.plug... ] Richard Achmatowicz commented on JGRP-1011: ------------------------------------------- Testing for the release usually involves the following set of tests: (i) run the unit/functional tests (unittests-xml) (ii) run the non-unit tests against udp (all-tests-udp) (iii) run the non-unit tests against tcp (all-tests-tcp) (iv) run the manual tests These tests are usually run against IPv4 non-loopback addresses. However, this time, I will run the tests against a) IPv4 loopback addresses b) IPv4 non-loopback addresses c) IPv6 loopback addresses d) IPv6 non-loopback, global addresses The configs used are as follows: // IPv4 loopback jgroups.bind_addr=127.0.0.1 jgroups.tcpping.initial_hosts=127.0.0.1[7800] jgroups.udp.mcast_addr=232.15.15.15 jgroups.udp.mcast_port=45588 jgroups.udp.ip_ttl=5 jgroups.tunnel.router_host=127.0.0.1 jgroups.tunnel.router_port=12001 # use true for IPv6 and false for IPv4 jgroups.useIPv6=false // IPv4 non-loopback jgroups.bind_addr=192.168.2.12 jgroups.tcpping.initial_hosts=192.168.2.12[7800] jgroups.udp.mcast_addr=232.15.15.15 jgroups.udp.mcast_port=45588 jgroups.udp.ip_ttl=5 jgroups.tunnel.router_host=192.168.2.12 jgroups.tunnel.router_port=12001 # use true for IPv6 and false for IPv4 jgroups.useIPv6=false // IPv6 loopback jgroups.bind_addr=::1 jgroups.tcpping.initial_hosts=::1[7800] jgroups.udp.mcast_addr=ff01::1 jgroups.udp.mcast_port=45588 jgroups.udp.ip_ttl=5 jgroups.tunnel.router_host=::1 jgroups.tunnel.router_port=12001 # use true for IPv6 and false for IPv4 jgroups.useIPv6=true // IPv6 non-loopback jgroups.bind_addr=3ffe:ffff:0100:f101::1 jgroups.tcpping.initial_hosts=3ffe:ffff:0100:f101::1[7800] jgroups.udp.mcast_addr=ff0e::1:2:3 jgroups.udp.mcast_port=45588 jgroups.udp.ip_ttl=5 jgroups.tunnel.router_host=3ffe:ffff:0100:f101::1 jgroups.tunnel.router_port=12001 # use true for IPv6 and false for IPv4 jgroups.useIPv6=true -- 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

[ https://jira.jboss.org/jira/browse/JGRP-1011?page=com.atlassian.jira.plug... ] Richard Achmatowicz commented on JGRP-1011: ------------------------------------------- Test results: I list the test which failed repeatedly, followed by the tests which failed, but passed on retry, organized by IP version. ipv4: repeatable failure: * CloseTest(tcp).testMultipleConnectsAndDisconnects (also fails on 2.6.10.GA - no regression) * FlushCloseOpenTest(tcp).testAndLoop (also fails on 2.6.10.GA - no regression) passed on retry: * none ipv4.local: repeatable failure: * CloseTest(tcp).testMultipleConnectsAndDisconnects (also fails on 2.6.10.GA - no regression) * FlushCloseOpenTest(tcp).testAndLoop (also fails on 2.6.10.GA - no regression) passed on retry: * SharedTransportTest(udp).testSendingOfMessageAfterChannelClose * ConnectStressTest (timeout) ipv6: repeatable failure: * CloseTest(tcp).testMultipleConnectsAndDisconnects (not testsed on 2.6.10.GA) * FlushCloseOpenTest(tcp).testAndLoop (not tested on 2.6.10.GA) passed on retry: * MergeTest(udp).testMerging4Members ipv6.local: repeatable failure: * CloseTest(tcp).testMultipleConnectsAndDisconnects (not testsed on 2.6.10.GA) * FlushCloseOpenTest(tcp).testAndLoop (not tested on 2.6.10.GA) * MergeTest(udp).testMerging4Members/testMerge4Members (this test is really broken for IPv6 as it uses IPv4 default mcast addresses and needs to be recrafted) passed on retry: * ConnectStressTest (timeout) -- 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

[ https://jira.jboss.org/jira/browse/JGRP-1011?page=com.atlassian.jira.plug... ] Richard Achmatowicz commented on JGRP-1011: ------------------------------------------- Performed manual tests for udp and tcp with IPv4 addresses and the tests looked OK. Started two instances of Draw with IPv6 addresses and did not see evidence of JGRP-984. There was extensive checking of this issue earlier in the week as well. So far, we have been unable to reproduce it. Modified versions and tagged the release as JGroups_2_6_11_GA. Unfortunately forgot to check in the release notes into docs/ReleaseNotes-JGroups2.6.11.txt so committed them to Branch_2_6 subsequent to tagging. -- 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

[ https://jira.jboss.org/jira/browse/JGRP-1011?page=com.atlassian.jira.plug... ] Richard Achmatowicz commented on JGRP-1011: ------------------------------------------- Uploaded to SourceForge. They have changed their web interface and uploading mechanism considerably. You now add release notes by selecting the file in question and right-clicking. -- 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