Status: Accepted
Owner:
[hidden email]
Labels: Type-Defect Priority-Medium GLASS-Scripts Version-3.0.x
New issue 291 by
[hidden email]: Maintenance Gem Topaz Exit [Seaside
3.0 / GemStone 3.0]
http://code.google.com/p/glassdb/issues/detail?id=291 From Ken Treis :
I'm setting up my first GSS/3.0-based deployment, and my Maintenance gem
keeps dying when the first MFC notification comes through:
> ...Expired: 0 sessions.
> Starting markForCollect.: 2011-08-26T09:17:03.50576305389404-07:00
> a Notification occurred (notification 3020), Successful completion of
> markForCollection.
> 494494 live objects found.
> 14 possible dead objects, occupying approximately 1260 bytes, may be
> reclaimed. (error 3020)
> topaz 1> topaz 1> [268 sz:0 cls: 68097 Boolean] true
> topaz 1>
> [Info]: Logging out at 08/26/11 16:17:04 UTC
I'm guessing that this is just an issue with the exception handlers in the
startMaintenance30 script, but if so... then I'm not going to be the only
one experiencing this. Changing the handler line from:
on: Error, Halt, BreakpointNotification
to:
on: Error, Halt, Notification
... seems to solve the problem, but I doubt that this is the proper
solution.
see
http://forum.world.st/Maintenance-Gem-Topaz-Exit-Seaside-3-0-GemStone-3-0-td3771345.html
for more details
Locked
