Bug 14391

GemBuilder for Java

2.3, 2.2, 2.1.2, 2.1.1, 2.1, 2.0, 1.2.1, 1.2, 1.1, 1.0


Rogue sessions must be stopped manually

It is not possible from GBJ to interrupt GemStone activity.
Therefore, if your GemStone Smalltalk code gets into an infinite loop or
becomes otherwise unresponsive there is no recourse but to kill the
Gem process.  Closing the Java application is not sufficient since
the "rogue" Gem will continue to run, tying up System resources.
Use the Unix 'kill' command or the Windows NT Task Manager to terminate
the Gem.  The process id can be found in the Gem session's log file.


No workaround


Last updated: 3/19/04