[
https://issues.jboss.org/browse/WFLY-11704?page=com.atlassian.jira.plugin...
]
Radoslav Husar updated WFLY-11704:
----------------------------------
Description:
This has been broken for a while now; there are still traces of properties such as
{{as.debug.port.node3}} but never set.
* What could to be done is to pick up {{-Ddebug}} and setup debug lines for *each* server
with specific ports, i.e. ports.
* However, {{suspend=y}} need to be used reasonably, since this makes for an arduous
debugging session.
* Probably one server could be picked up for debugging.
* Moreover, timeouts should probably be heavily increased not to timeout very quickly.
was:
This has been broken for a while now; there are still traces of properties such as
{{as.debug.port.node3}} but never set.
* What could to be done is to pick up {{-Ddebug}} and setup debug lines for *each* server
with specific ports, i.e. ports.
* However, {{suspend=y}} need to be used reasonably, since this makes for an arduous
debugging session.
* Probably one server could be picked up for debugging.
Support -Ddebug for clustering testsuite
----------------------------------------
Key: WFLY-11704
URL:
https://issues.jboss.org/browse/WFLY-11704
Project: WildFly
Issue Type: Task
Components: Clustering, Test Suite
Affects Versions: 15.0.0.Final
Reporter: Radoslav Husar
Assignee: Radoslav Husar
Priority: Minor
This has been broken for a while now; there are still traces of properties such as
{{as.debug.port.node3}} but never set.
* What could to be done is to pick up {{-Ddebug}} and setup debug lines for *each* server
with specific ports, i.e. ports.
* However, {{suspend=y}} need to be used reasonably, since this makes for an arduous
debugging session.
* Probably one server could be picked up for debugging.
* Moreover, timeouts should probably be heavily increased not to timeout very quickly.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)