Red Hat Bugzilla – Bug 978332
DeployableContainer kills the managed server instead of regular shutdown in stop() on Windows
Last modified: 2013-10-15 13:20:04 EDT
Description of problem:
Backport of WFLY-126 to the EAP 6.1.x branch.
This might be due to historical reasons for the TS to run faster, but this messes up clustering tests since shutdown is part of the test.
The problem is that Managed*DeployableContainer kills the managed server instead of regular shutdown in stop() on Windows. ARQ's stop is supposed to shutdown the server 'nicely', for abrupt termination there is jvmKill().
This was probably implemented like this incorrectly assuming that on windows, the process is sent SIGTERM like on *NIX-based OSes but there is no such thing on windows and the process is terminated immediately.
This shows up only in clustered tests, compared to other tests which dont rely on the shutdown sequence to be completed, but clustering testsuite relies on shutdown to disconnect the channel and leave the cluster without FD having to kick in.
Created a PR for this:
TS improvement is welcome.
I do indeed see improvements in the clustering testsuite on Windows.
Radoslav Husar <firstname.lastname@example.org> updated the status of jira WFLY-126 to Closed