Stack growth due to GemStone exceptions handled and resumed in client
Sequential GemStone exceptions that are handled on the client may causestack growth and consequent memory use. This is due to the way GBS processes
a GbsError, invokes handlers, and then does a continue; subsequent errors
will be raised on the stack and processed similarly, and so on, causing
the stack to grow with each subsequent error.
Workaround:
none/not applicable