[
https://jira.jboss.org/jira/browse/JGRP-1041?page=com.atlassian.jira.plug...
]
Richard Achmatowicz commented on JGRP-1041:
-------------------------------------------
Added in DEBUG-level logging so that each time a channel is created, we see the channel
resources used to create the channel. This includes the original resources, plus any
modifications via makeUnique. For example:
org.jgroups.tests.DuplicateTest:
38491 [INFO] DuplicateTest: - Using configuration file tcp.xml
38502 [DEBUG] DuplicateTest: - Creating channel with resources:
38503 [DEBUG] DuplicateTest: - (tcp.bind_port, tcp.port_range) = (7800, 5)
38503 [DEBUG] DuplicateTest: - Modifying channel resources:
38503 [DEBUG] DuplicateTest: - (tcp.bind_port, tcp.port_range) = (25349, 3)
38503 [INFO] DuplicateTest: - Using configuration file tcp.xml
38517 [DEBUG] DuplicateTest: - Creating cloned channel with resources:
38517 [DEBUG] DuplicateTest: - (tcp.bind_port, tcp.port_range) = (25349, 3)
38517 [INFO] DuplicateTest: - Using configuration file tcp.xml
38531 [DEBUG] DuplicateTest: - Creating cloned channel with resources:
38531 [DEBUG] DuplicateTest: - (tcp.bind_port, tcp.port_range) = (25349, 3)
Provide more DEBUG level information on Channel resources used when
running tests in parallel
---------------------------------------------------------------------------------------------
Key: JGRP-1041
URL:
https://jira.jboss.org/jira/browse/JGRP-1041
Project: JGroups
Issue Type: Feature Request
Affects Versions: 2.8
Reporter: Richard Achmatowicz
Assignee: Richard Achmatowicz
Priority: Minor
Fix For: 2.8
When running tests in parallel under testng, the JGroups testsuite provides mechanisms to
allocate channel resources (udp.mcast_addr, udp..mcast_port, bind_port, port_range) in
such a way that JGroups channels in different tests do not interfere with each other. This
is done by allocating non-overlapping ranges of addresses and ports.
However, there is a rather complex trail to follow when trying to find which addresses
will be picked up by tests:
* build.xml + build.properties, which feed to
* runtest parameters, which feed to
* testng parameters, which feed to
* ChannelTestBase parameters, which feed to
* test case paramaters
At present, it is not easy to discover which values a test is using for the channel
resources mentioned above.
It would be nice to be able to see this information in the DEBUG logs, to aid in
resolving problesm with the wrong addresses being used.
--
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