]
Jason Greene updated WFLY-61:
-----------------------------
Fix Version/s: 8.0.0.Final
timeout handling waiting for future
-----------------------------------
Key: WFLY-61
URL:
https://issues.jboss.org/browse/WFLY-61
Project: WildFly
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Domain Management
Reporter: Alexey Loubyansky
Assignee: Brian Stansberry
Fix For: 8.0.0.CR1, 8.0.0.Final
The issue was reported in AS7-5350 which points to a CLI testcase that fails on windows.
The test starts a CLI process and deliberately specifies a wrong port for the controller
expecting a failure during connection. The CLI sends a read-attribute operation request on
connect to make sure the connection is working. The test is waiting for a response from
the controller for 10 sec and then times out. The time out of the ModelControllerClient is
5 sec. The test still fails after 10 sec time out but the error output stream of the CLI
process does contain the stack trace of the expected exception, i.e. that the controller
was not available at the specified address.
When the testcase times out, it destroys the CLI process, perhaps, this triggers some
actions and the exception is finally thrown and the stack trace gets logged but it's
too late.
--
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: