[CLEANUP] fixing failing test KarafBootTest#verifyStaleLockBehavior

[NJtwentyone]

• changing the pid for a stale process to -1, instead of 0 to work with all systems

suggested fix, set stale/unused pid to -1, since it is a valid PID for an invalid process for windows and *nix:

• https://devblogs.microsoft.com/oldnewthing/20040223-00/?p=40503
• https://www.linfo.org/pid.html#:~:text=A%20PID%20(i.e.%2C%20process%20identification,always%20a%20non%2Dnegative%20integer.

Backstory:

On my local M2 Chip Mac, I was having the unit test KarafBootTest#verifyStaleLockBehavior fail, the process id (pid) 0 was actually being used

When I set it to really high number pid 999999... that isn't used, the test pass:

When I set the pid to -1, the test pass:

[hitachivantarasonarqube[bot]]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[buildguy]

[](https://docs.jfrog-applications.jfrog.io/jfrog-applications/frogbot)

---

[🐸 JFrog Frogbot](https://docs.jfrog-applications.jfrog.io/jfrog-applications/frogbot)