Bug 15520

Bug: 15520

Impact:

Product:

GemStone/S

Versions:

6.7.2.1, 6.7.2, 6.7.1, 6.7, 6.6.5, 6.6.4, 6.6.3.3, 6.6.3.2, 6.6.3, 6.6.2, 6.6.1, 6.6, 6.5.8, 6.5.7.5, 6.5.7, 6.5.6, 6.5.5, 6.5.4, 6.5.2, 6.5.1, 6.5, 6.3.1, 6.3, 6.2.x, 6.2, 6.1.6, 6.1.5, 6.1.x, 6.0.x, 5.1.5.1, older versions

Platform:

All

Fixed In:

Stone hangs when repository is full

As described in Chapter 4 of the GemStone System Administration
Guide, the Stone attempts to prevent the repository from ever
filling completely. The final action it takes is to send a stop
session to the Gems with the oldest commit records. However, under
certain circumstances, the Gems are waiting for communications
from their clients, and ignore the Stone's request. The repository
then fills completely, causing the Stone to hang for lack of disk
space.

Workaround

Try to ensure that Gems are not left in a state where they ignore
signals from the Stone. For example, don't leave topaz sessions
sitting at the topaz prompt waiting for instructions. Make sure
topaz is executing some code.

The owner of a Gem process can also logout the Gem manually, or,
if necessary, terminate the Gem manually.