[
https://issues.redhat.com/browse/WFLY-13897?page=com.atlassian.jira.plugi...
]
Radoslav Husar edited comment on WFLY-13897 at 9/29/20 4:25 PM:
----------------------------------------------------------------
There seem to be couple of problems at play here:
1. The graceful shutdown doesn't work because the client doesn't authenticate,
because there is no such configuration - Jira TBA.
2. When graceful shutdown doesn't success, PID is not obtained on JDK8 – fix
ISPN-12366.
3. When PID is obtained on JDK11, the kill command is incorrect - fix ISPN-12368.
4. If that is fixed - the kill command only kills the parent process (sh) and not the
child process (java = the server) - fix ISPN-12368
was (Author: rhusar):
There seem to be couple of problems at play here:
1. The graceful shutdown doesn't work because the client doesn't authenticate,
because there is no such configuration - Jira TBA.
2. When graceful shutdown doesn't success, PID is not obtained on JDK8 – also caused
by ISPN-12366.
3. When PID is obtained on JDK11, the kill command is incorrect.
4. If that is fixed - the kill command only kills the parent process (sh) and not the
child process (java = the server).
infinispan-server instances provisioned by testsuite never shutdown
-------------------------------------------------------------------
Key: WFLY-13897
URL:
https://issues.redhat.com/browse/WFLY-13897
Project: WildFly
Issue Type: Bug
Components: Clustering, Test Suite
Affects Versions: 21.0.0.Beta1
Reporter: Paul Ferraro
Assignee: Radoslav Husar
Priority: Critical
Running the clustering testsuite locally leaves 9 instances of infinispan-server
running. This wreaks havoc on the CI, which will remain running until the VM shuts down.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)