Bug 45738

GemStone/S 64 Bit

3.2.9,, 3.2.8, 3.2.7, 3.2.6, 3.2.5, 3.2.4, 3.2.3, 3.2.2, 3.2.1, 3.2


Socket leak in NetLDI after failed fork, potentially causing netldi to run hot

The Netldi forks the Gem or other process that it spawns as child processes.  If a failure occurs in the wrong place in certain code paths, the socket that had been created was not cleaned up. When sufficient socket leaks had occurred, the NetLDI started running hot.


Restarting the netldi periodically avoids issues.

Last updated: 12/16/15