[jboss-jira] [JBoss JIRA] (JGRP-1793) MergeTest does not close channels correctly
Bela Ban (JIRA)
issues at jboss.org
Sat Feb 22 05:05:48 EST 2014
[ https://issues.jboss.org/browse/JGRP-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bela Ban resolved JGRP-1793.
----------------------------
Resolution: Done
3.4 also uses Util.close(Closeable ... channels), so the fix is only for 3.2.x
> MergeTest does not close channels correctly
> -------------------------------------------
>
> Key: JGRP-1793
> URL: https://issues.jboss.org/browse/JGRP-1793
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.2.13, 3.3.5, 3.4.2
> Reporter: Richard Achmatowicz
> Assignee: Richard Achmatowicz
> Priority: Minor
> Fix For: 3.2.13
>
>
> A typo in the test case results in channels for MergeTest to remain open long after the test has finished:
> {noformat}
> [nrla at lenovo bin]$ ./probe.sh
> -- send probe on /224.0.75.75:7500
> #1 (171 bytes):
> local_addr=D [09993e52-3d74-47b9-152e-2d9703e55734]
> cluster=MergeTest.testMerging4Members
> view=[A|11] [A, B, C, D]
> physical_addr=127.0.0.1:33877
> version=3.2.13.Final
> #2 (165 bytes):
> local_addr=A [30c2b3d8-72b0-0e66-ee49-c5414e117048]
> cluster=MergeTest.testMerging2Members
> view=[B|11] [B, A]
> physical_addr=127.0.0.1:52335
> version=3.2.13.Final
> #3 (171 bytes):
> local_addr=B [d281af3b-9bbc-a556-d654-b2b423fec81b]
> cluster=MergeTest.testMerging4Members
> view=[A|11] [A, B, C, D]
> physical_addr=127.0.0.1:49313
> version=3.2.13.Final
> #4 (171 bytes):
> local_addr=A [93ca13b4-cde3-4fa4-b971-dffd23cdf5fe]
> cluster=MergeTest.testMerging4Members
> view=[A|11] [A, B, C, D]
> physical_addr=127.0.0.1:33183
> version=3.2.13.Final
> #5 (165 bytes):
> local_addr=B [0ed3765f-3ae1-707d-06b5-ba7c8eaed8fc]
> cluster=MergeTest.testMerging2Members
> view=[B|11] [B, A]
> physical_addr=127.0.0.1:38458
> version=3.2.13.Final
> {noformat}
> When these tests are run seqentially, their channels should never be open simultaneously.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list