Ken,
Yes the MarkForCollection error was changed for GemStone 3.0 ... I am still working through identifying 3.0 issues for Seaside...
You should be aware that we have uncovered some bugs in GemStone 3.0 relative to Seaside so I think it would be prudent to hold off on going into production with GemStone 3.0.0 and wait for a follow on release... At this point it is a good idea to explore 3.0 so that we can identify additional issues before we make a bugfix release ...
I am also working through the upgrade issues for upgrading from 2.4 to 3.0 and at the moment I haven't resolved all of the issues ...
We do not have a hard date for the next bugfix release, but the bugfix release date will likely be driven by Seaside...
Dale
----- Original Message -----
| From: "Ken Treis" <
[hidden email]>
| To: "GemStone Seaside beta discussion" <
[hidden email]>
| Sent: Friday, August 26, 2011 9:27:55 AM
| Subject: [GS/SS Beta] Maintenance Gem Topaz Exit [Seaside 3.0 / GemStone 3.0]
|
| 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.
|
| --
| Ken Treis
| Miriam Technologies, Inc.
|
|
Locked
