[jboss-jira] [JBoss JIRA] Commented: (JGRP-1087) Release JGroups 2.4.7
[
https://jira.jboss.org/jira/browse/JGRP-1087?page=com.atlassian.jira.plug...
]
Richard Achmatowicz commented on JGRP-1087:
-------------------------------------------
There is a problem with ConnectionTableTest on Fedora. When ports are allocated and then
freed, as in the ports used for the connection table acceptor threads, they don't seem
to become immediately available once freed. Thus, tests following the first test can't
grab those same ports. This we have to allow a port range so that a free port can be
chosen. But the clients in ConnectionTableTest use fixed port specifications, and so are
not aware of any ranging which had to go on to find an available port.
Seems that the test should be modified so that clirents are able to obtain the actual port
obtained by the ConnectionTable.
Release JGroups 2.4.7
---------------------
Key: JGRP-1087
URL: https://jira.jboss.org/jira/browse/JGRP-1087
Project: JGroups
Issue Type: Task
Affects Versions: 2.4.7
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Fix For: 2.4.7
This release is required for the EAP 4.2 and 4.3 CP releases, and is primarily a bug fix
release.
The release notes show the following bugs and tasks completed for this release:
Release Notes - JGroups - Version 2.4.7
** Bug
* [JGRP-549] - ConnectionTable: spurious Connection instances on concurrent connects
* [JGRP-956] - Binding to mcast address in UDP.java is not working on Linux with
IPv6
* [JGRP-967] - Deadlock in FD_SOCK
* [JGRP-981] - Wrong view with concurrent startup
* [JGRP-984] - JGroups can not parse IPV6 literals in TCPPING protocol configuration
* [JGRP-990] - Grammatical Error in log message: I'm being am suspected.
* [JGRP-1000] - COMPRESS corrupts some messages
* [JGRP-1060] - NAKACK has inconsistent internal state after concurrent node startup
** Task
* [JGRP-982] - Extend linux method of creating multicast socket to HP-UX
--
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