4:04 p.m.
Brian Stansberry created WFCORE-2099:
----------------------------------------
Summary: Make OperationTimeoutTestCase more robust by increasing timeout for
setup/teardown ops
Key: WFCORE-2099
URL: https://issues.jboss.org/browse/WFCORE-2099
Project: WildFly Core
Issue Type: Task
Components: Domain Management, Test Suite
Reporter: Brian Stansberry
Assignee: Brian Stansberry
OperationTimeoutTestCase deliberately runs with very low blocking timeouts, in order to
execute reasonably efficiently, not waiting long periods for timeouts. But those timeouts
are also in effect for various setup/teardown ops, and that can lead to spurious failures
like this:
{code}
org.jboss.as.test.integration.management.util.MgmtOperationException: Management operation
failed.
at
org.jboss.as.test.integration.domain.management.util.DomainTestUtils.executeForResult(DomainTestUtils.java:160)
at
org.jboss.as.test.integration.domain.OperationTimeoutTestCase.executeForResult(OperationTimeoutTestCase.java:306)
at
org.jboss.as.test.integration.domain.OperationTimeoutTestCase.tearDownDomain(OperationTimeoutTestCase.java:192)
------- Stdout: -------
[Host Controller] [31m[0m[0m13:42:23,027 INFO
[org.jboss.as.controller.management-operation] (Host Controller Service Threads - 5)
WFLYCTL0409: Execution of operation 'remove' on remote process at address
'[[0m
[Host Controller] ("host" => "slave"),
[Host Controller] ("server" => "other-two")
[Host Controller] ]' timed out after 2000 ms while awaiting initial response; remote
process has been notified to terminate operation
[Server:other-two] 13:42:23,033 INFO
[org.jboss.as.test.integration.management.extension.blocker.BlockerExtension]
(ServerService Thread Pool -- 12) Registered blocker-test operations
[Server:main-three] 13:42:23,034 INFO
[org.jboss.as.test.integration.management.extension.blocker.BlockerExtension]
(ServerService Thread Pool -- 4) Registered blocker-test operations
[Server:main-one] 13:42:23,034 INFO
[org.jboss.as.test.integration.management.extension.blocker.BlockerExtension]
(ServerService Thread Pool -- 7) Registered blocker-test operations
[Server:other-two] 13:42:23,034 INFO [org.jboss.as.protocol] (ServerService Thread Pool
-- 2) WFLYPRT0057: cancelled task by interrupting thread Thread[ServerService Thread Pool
-- 12,5,ServerService ThreadGroup]
[Host Controller] [0m[0m13:42:23,042 INFO
[org.jboss.as.test.integration.management.extension.blocker.BlockerExtension] (Host
Controller Service Threads - 9) Registered blocker-test operations[0m
[Host Controller] [0m[0m13:42:23,045 INFO
[org.jboss.as.test.integration.management.extension.blocker.BlockerExtension]
(management-handler-thread - 2) Registered blocker-test operations[0m
Failed operation:
{
"operation" => "remove",
"address" => [("extension" =>
"org.wildfly.extension.blocker-test")]
}
Response:
{
"outcome" => "failed",
"result" => undefined,
"failure-description" => "WFLYDC0022: Operation failed or was rolled
back on all servers.",
"rolled-back" => true,
"server-groups" => {
"main-server-group" => {"host" => {
"master" => {"main-one" => {"response"
=> {
"outcome" => "failed",
"rolled-back" => true
}}},
"slave" => {"main-three" => {"response"
=> {
"outcome" => "failed",
"result" => undefined,
"rolled-back" => true
}}}
}},
"other-server-group" => {"host" => {"slave"
=> {"other-two" => {"response" => {
"outcome" => "failed",
"result" => undefined,
"failure-description" => "WFLYCTL0409: Execution of
operation 'remove' on remote process at address '[
(\"host\" => \"slave\"),
(\"server\" => \"other-two\")
]' timed out after 2000 ms while awaiting initial response; remote process has been
notified to terminate operation",
"rolled-back" => true
}}}}}
}
}
{code}
Simple solution is to add the blocking-timeout header to those ops and use a longer
timeout (say 20 secs).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)