[JBoss JIRA] (ISPN-12318) Query.maxResult() ignored during entity loading
by Gustavo Fernandes (Jira)
[ https://issues.redhat.com/browse/ISPN-12318?page=com.atlassian.jira.plugi... ]
Gustavo Fernandes updated ISPN-12318:
-------------------------------------
Fix Version/s: 12.0.0.Dev04
> Query.maxResult() ignored during entity loading
> -----------------------------------------------
>
> Key: ISPN-12318
> URL: https://issues.redhat.com/browse/ISPN-12318
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying
> Affects Versions: 12.0.0.Dev03
> Reporter: Gustavo Fernandes
> Assignee: Gustavo Fernandes
> Priority: Critical
> Fix For: 12.0.0.Dev04
>
>
> When a query has a maxResult it should not try to load/collect/read/hidrate all hits but rather restrict it to the requested page size. This causes unnecessary allocations of Strings and byte[]. In particular, the {{KeyTransformationHandler#stringToKey}} method produces a large amount of garbage.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 6 months
[JBoss JIRA] (ISPN-12370) Implement proper form login and digest login
by Katia Aresti (Jira)
Katia Aresti created ISPN-12370:
-----------------------------------
Summary: Implement proper form login and digest login
Key: ISPN-12370
URL: https://issues.redhat.com/browse/ISPN-12370
Project: Infinispan
Issue Type: Enhancement
Components: Console
Affects Versions: 12.0.0.Dev04
Reporter: Katia Aresti
Assignee: Katia Aresti
Today the console relies on the navigator popup to log in.
This is not clean and it's very confusing for many reasons:
* White page
* The app downloaded at least two times
We should download the application only once and if authentication is done with digest (not keycloak) then we should handle the digest requests ourselfs.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 6 months
[JBoss JIRA] (ISPN-12368) ServerRunMode.FORKED always leaks running server processes when cluster shutdown fails
by Radoslav Husar (Jira)
[ https://issues.redhat.com/browse/ISPN-12368?page=com.atlassian.jira.plugi... ]
Radoslav Husar updated ISPN-12368:
----------------------------------
Component/s: Server
> ServerRunMode.FORKED always leaks running server processes when cluster shutdown fails
> --------------------------------------------------------------------------------------
>
> Key: ISPN-12368
> URL: https://issues.redhat.com/browse/ISPN-12368
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Affects Versions: 11.0.3.Final, 12.0.0.Dev04
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Major
>
> See WFLY-13897 for the 'reproducer' in WildFly.
> This is due to a couple of things:
> 1. Obtaining PID in JDK8 is not implemented.
> 2. Obtaining PID is broken in higher JDKs due to ISPN-12366.
> 3. The obtained PID is wrong anyway, because its the PID of the parent shell process, not the child server process.
> 4. The kill command usage is incorrect and fails anyway.
> 5. Even if killed, the monitoring process leaks anyway due to ISPN-12367.
> 6. The stop command doesn't check for client and server errors on the REST call.
> The fix is to assign random UUID to a server process and filter properly; use process API correctly.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 6 months
[JBoss JIRA] (ISPN-12367) ServerRunMode.FORKED can leak running "tail -f .../server/log/server.log" processes
by Radoslav Husar (Jira)
[ https://issues.redhat.com/browse/ISPN-12367?page=com.atlassian.jira.plugi... ]
Radoslav Husar updated ISPN-12367:
----------------------------------
Component/s: Server
> ServerRunMode.FORKED can leak running "tail -f .../server/log/server.log" processes
> -----------------------------------------------------------------------------------
>
> Key: ISPN-12367
> URL: https://issues.redhat.com/browse/ISPN-12367
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Affects Versions: 11.0.3.Final, 12.0.0.Dev04
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Major
>
> After a couple of test runs:
> {noformat}
> [rhusar@ribera clustering]$ ps
> PID TTY TIME CMD
> 44513 ttys000 0:00.03 /Applications/iTerm.app/Contents/MacOS/iTerm2 --server /usr/bin/login -fpl rhusar /Applications/iTerm.app/Contents/MacOS/iTerm2 --launch_shell
> 44516 ttys000 0:01.13 -bash
> 6297 ttys001 0:00.06 /Applications/iTerm.app/Contents/MacOS/iTerm2 --server /usr/bin/login -fpl rhusar /Applications/iTerm.app/Contents/MacOS/iTerm2 --launch_shell
> 6299 ttys001 0:00.54 -bash
> 15288 ttys001 0:02.20 watch jps -l | sort
> 2833 ttys002 0:00.00 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 2976 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 3213 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 3421 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 3738 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 4040 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 4445 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 4748 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 6246 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 6657 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 6871 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 7046 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 7358 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 7697 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 9209 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 9356 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 9482 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 9904 ttys002 0:00.02 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 10059 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 10485 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 10754 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 10921 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 11082 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 11355 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 15149 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 15642 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 15839 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 16370 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 16914 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 17066 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 17604 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 17893 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 18034 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 18385 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 6 months
[JBoss JIRA] (ISPN-12368) ServerRunMode.FORKED always leaks running server processes when cluster shutdown fails
by Radoslav Husar (Jira)
[ https://issues.redhat.com/browse/ISPN-12368?page=com.atlassian.jira.plugi... ]
Radoslav Husar updated ISPN-12368:
----------------------------------
Status: Pull Request Sent (was: Coding In Progress)
Git Pull Request: https://github.com/infinispan/infinispan/pull/8727
> ServerRunMode.FORKED always leaks running server processes when cluster shutdown fails
> --------------------------------------------------------------------------------------
>
> Key: ISPN-12368
> URL: https://issues.redhat.com/browse/ISPN-12368
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 11.0.3.Final, 12.0.0.Dev04
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Major
>
> See WFLY-13897 for the 'reproducer' in WildFly.
> This is due to a couple of things:
> 1. Obtaining PID in JDK8 is not implemented.
> 2. Obtaining PID is broken in higher JDKs due to ISPN-12366.
> 3. The obtained PID is wrong anyway, because its the PID of the parent shell process, not the child server process.
> 4. The kill command usage is incorrect and fails anyway.
> 5. Even if killed, the monitoring process leaks anyway due to ISPN-12367.
> 6. The stop command doesn't check for client and server errors on the REST call.
> The fix is to assign random UUID to a server process and filter properly; use process API correctly.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 6 months
[JBoss JIRA] (ISPN-12367) ServerRunMode.FORKED can leak running "tail -f .../server/log/server.log" processes
by Radoslav Husar (Jira)
[ https://issues.redhat.com/browse/ISPN-12367?page=com.atlassian.jira.plugi... ]
Radoslav Husar updated ISPN-12367:
----------------------------------
Status: Pull Request Sent (was: Coding In Progress)
Git Pull Request: https://github.com/infinispan/infinispan/pull/8727
> ServerRunMode.FORKED can leak running "tail -f .../server/log/server.log" processes
> -----------------------------------------------------------------------------------
>
> Key: ISPN-12367
> URL: https://issues.redhat.com/browse/ISPN-12367
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 11.0.3.Final, 12.0.0.Dev04
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Major
>
> After a couple of test runs:
> {noformat}
> [rhusar@ribera clustering]$ ps
> PID TTY TIME CMD
> 44513 ttys000 0:00.03 /Applications/iTerm.app/Contents/MacOS/iTerm2 --server /usr/bin/login -fpl rhusar /Applications/iTerm.app/Contents/MacOS/iTerm2 --launch_shell
> 44516 ttys000 0:01.13 -bash
> 6297 ttys001 0:00.06 /Applications/iTerm.app/Contents/MacOS/iTerm2 --server /usr/bin/login -fpl rhusar /Applications/iTerm.app/Contents/MacOS/iTerm2 --launch_shell
> 6299 ttys001 0:00.54 -bash
> 15288 ttys001 0:02.20 watch jps -l | sort
> 2833 ttys002 0:00.00 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 2976 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 3213 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 3421 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 3738 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 4040 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 4445 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 4748 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 6246 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 6657 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 6871 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 7046 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 7358 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 7697 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 9209 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 9356 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 9482 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 9904 ttys002 0:00.02 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 10059 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 10485 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 10754 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 10921 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 11082 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 11355 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 15149 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 15642 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 15839 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 16370 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 16914 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 17066 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 17604 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 17893 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 18034 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> 18385 ttys002 0:00.01 tail -f /Users/rhusar/git/wildfly/testsuite/integration/clustering/target/infinispan-server-11.0.3.Final/server/log/server.log
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 6 months
[JBoss JIRA] (ISPN-12368) ServerRunMode.FORKED always leaks running server processes when cluster shutdown fails
by Radoslav Husar (Jira)
[ https://issues.redhat.com/browse/ISPN-12368?page=com.atlassian.jira.plugi... ]
Radoslav Husar updated ISPN-12368:
----------------------------------
Description:
See WFLY-13897 for the 'reproducer' in WildFly.
This is due to a couple of things:
1. Obtaining PID in JDK8 is not implemented.
2. Obtaining PID is broken in higher JDKs due to ISPN-12366.
3. The obtained PID is wrong anyway, because its the PID of the parent shell process, not the child server process.
4. The kill command usage is incorrect and fails anyway.
5. Even if killed, the monitoring process leaks anyway due to ISPN-12367.
6. The stop command doesn't check for client and server errors on the REST call.
The fix is to assign random UUID to a server process and filter properly; use process API correctly.
was:
See WFLY-13897 for the 'reproducer' in WildFly.
This is due to a couple of things:
1. Obtaining PID in JDK8 is not implemented.
2. Obtaining PID is broken in higher JDKs due to ISPN-12366.
3. The obtained PID is wrong anyway, because its the PID of the parent shell process, not the child server process.
4. The kill command usage is incorrect and fails anyway.
5. Even if killed, the monitoring process leaks anyway due to ISPN-12367.
The fix is to assign random UUID to a server process and filter properly; use process API correctly.
> ServerRunMode.FORKED always leaks running server processes when cluster shutdown fails
> --------------------------------------------------------------------------------------
>
> Key: ISPN-12368
> URL: https://issues.redhat.com/browse/ISPN-12368
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 11.0.3.Final, 12.0.0.Dev04
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Major
>
> See WFLY-13897 for the 'reproducer' in WildFly.
> This is due to a couple of things:
> 1. Obtaining PID in JDK8 is not implemented.
> 2. Obtaining PID is broken in higher JDKs due to ISPN-12366.
> 3. The obtained PID is wrong anyway, because its the PID of the parent shell process, not the child server process.
> 4. The kill command usage is incorrect and fails anyway.
> 5. Even if killed, the monitoring process leaks anyway due to ISPN-12367.
> 6. The stop command doesn't check for client and server errors on the REST call.
> The fix is to assign random UUID to a server process and filter properly; use process API correctly.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 7 months
[JBoss JIRA] (ISPN-12368) ServerRunMode.FORKED always leaks running server processes when cluster shutdown fails
by Radoslav Husar (Jira)
[ https://issues.redhat.com/browse/ISPN-12368?page=com.atlassian.jira.plugi... ]
Radoslav Husar updated ISPN-12368:
----------------------------------
Description:
See WFLY-13897 for the 'reproducer' in WildFly.
This is due to a couple of things:
1. Obtaining PID in JDK8 is not implemented.
2. Obtaining PID is broken in higher JDKs due to ISPN-12366.
3. The obtained PID is wrong anyway, because its the PID of the parent shell process, not the child server process.
4. The kill command usage is incorrect and fails anyway.
5. Even if killed, the monitoring process leaks anyway due to ISPN-12367.
The fix is to assign random UUID to a server process and filter properly; use process API correctly.
was:
See WFLY-13897 for the 'reproducer' in WildFly.
This is due to a couple of things:
1. Obtaining PID in JDK8 is not implemented.
2. Obtaining PID is broken in higher JDKs due to ISPN-12366.
3. The obtained PID is wrong anyway, because its the PID of the parent shell process, not the child server process.
4. The kill command usage is incorrect and fails anyway.
5. Even if killed, the monitoring process leaks anyway due to ISPN-12367.
The fix is to assign random UUID to a server process and filter properly.
> ServerRunMode.FORKED always leaks running server processes when cluster shutdown fails
> --------------------------------------------------------------------------------------
>
> Key: ISPN-12368
> URL: https://issues.redhat.com/browse/ISPN-12368
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 11.0.3.Final, 12.0.0.Dev04
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Major
>
> See WFLY-13897 for the 'reproducer' in WildFly.
> This is due to a couple of things:
> 1. Obtaining PID in JDK8 is not implemented.
> 2. Obtaining PID is broken in higher JDKs due to ISPN-12366.
> 3. The obtained PID is wrong anyway, because its the PID of the parent shell process, not the child server process.
> 4. The kill command usage is incorrect and fails anyway.
> 5. Even if killed, the monitoring process leaks anyway due to ISPN-12367.
> The fix is to assign random UUID to a server process and filter properly; use process API correctly.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 7 months
[JBoss JIRA] (ISPN-12368) ServerRunMode.FORKED always leaks running server processes when cluster shutdown fails
by Radoslav Husar (Jira)
Radoslav Husar created ISPN-12368:
-------------------------------------
Summary: ServerRunMode.FORKED always leaks running server processes when cluster shutdown fails
Key: ISPN-12368
URL: https://issues.redhat.com/browse/ISPN-12368
Project: Infinispan
Issue Type: Bug
Reporter: Radoslav Husar
Assignee: Radoslav Husar
See WFLY-13897 for the 'reproducer' in WildFly.
This is due to a couple of things:
1. Obtaining PID in JDK8 is not implemented.
2. Obtaining PID is broken in higher JDKs due to ISPN-12366.
3. The obtained PID is wrong anyway, because its the PID of the parent shell process, not the child server process.
4. The kill command usage is incorrect and fails anyway.
The fix is to assign random UUID to a server process and filter properly.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 7 months