Bug 48734

GemStone/S 64 Bit

3.5.1, 3.5, 3.4.5, 3.4.4, 3.4.3, 3.4.2, 3.4.1, 3.4, 3.3.9, 3.3.8, 3.3.7, 3.3.6, 3.3.5, 3.3.4, 3.3.3, 3.3.1, 3.3, 3.2.16, 3.2.15, 3.2.14, 3.2.13, 3.2.12, 3.2.x, earlier versions

3.5.2

gslist -p returns invalid process ID when process is not running/status killed

gslist -p returns the processId only of one or more GemStone processes.  The processId comes from the GemStone locks files, and thus is returned for processes that have the status killed and are no longer running.  For processes that have status killed, the PID may have been reused for a different process, including a non-GemStone process.  The results from gslist -p in this case is wrong.

Workaround

Always use the -c argument (which clears killed processes) in addition to the -p.  For example

gslist -c -p gs64stone


Last updated: 5/18/20