Hi there,
One of my Seaside gems (in Gemstone 2.4.4.1) just ran into the following error (see gem log below). I already ran an object audit on the repository and it’s reporting no problems. I’m not finding any info about this, so it just raises questions marks for me. Johan GemStone: Error Nonfatal The object with object ID 3458764685619232777 is corrupt. Reason: 'om::RefreshObj illegal refresh of always-valid obj' Error Category: 231169 [GemStone] Number: 2261 Arg Count: 2 Context : 3169351937 Arg 1: [3169352193 sz:10 cls: 77313 LargePositiveInteger] 3458764685619232777 Arg 2: [3169352449 sz:50 cls: 74753 String] om::RefreshObj illegal refresh of always-valid obj Now executing the following command saved from "iferr 1": where ==> 1 Object >> at: @1 line 1 [GsMethod 1924609] 2 GsProcess class >> _finishFrameContents:forLevel: @6 line 10 [GsMethod 4489473] 3 GsProcess class >> _frameContentsAt: @7 line 23 [GsMethod 4485377] 4 GsProcess class >> stackReportToLevel: @8 line 12 [GsMethod 4486401] 5 GRGemStonePlatform >> logError:title:shouldCommit: @2 line 4 [GsMethod 120571649] 6 GRGemStonePlatform >> logError:title: @2 line 3 [GsMethod 120567809] 7 WAErrorHandler >> saveExceptionContinuation: @7 line 6 [GsMethod 207527937] 8 ComplexBlock in NPGemStoneErrorHandler >> handleDefault: @3 line 2 [GsMethod 416537601] 9 ComplexBlock in ExecutableBlock >> ensure: @4 line 11 [GsMethod 2304001] 10 ComplexBlock in ExecutableBlock >> ensure: @6 line 11 [GsMethod 2304001] 11 NPGemStoneErrorHandler >> handleDefault: @23 line 3 [GsMethod 416537601] 12 WAErrorHandler >> handleError: @1 line 2 [GsMethod 207526657] 13 WAErrorHandler >> handleGemStoneException: @4 line 4 [GsMethod 207526913] 14 WAHtmlHaltAndErrorHandler >> handleException: @1 line 2 [GsMethod 211105537] 15 NPGemStoneErrorHandler >> handleException: @5 line 5 [GsMethod 416537857] 16 ComplexBlock in WAExceptionHandler >> handleExceptionsDuring: @4 line 5 [GsMethod 210746625] 17 ExceptionHandler >> doTryBlock: @9 line 7 [GsMethod 10065409] 18 ExceptionHandler >> try:on:do: @15 line 18 [GsMethod 10062081] 19 ComplexBlock in ExecutableBlock >> on:do: @2 line 8 [GsMethod 9005057] 20 ComplexVCBlock in WAExceptionHandler >> handleExceptionsDuring: @7 line 8 [GsMethod 210746625] 21 ExceptionHandler >> caughtExceptionWithAction: @5 line 4 [GsMethod 10065153] 22 ComplexBlock in ExceptionHandler >> caughtEx:number:cat:args:handler: @12 line 13 [GsMethod 10064641] 23 ComplexBlock in ExecutableBlock >> ensure: @4 line 11 [GsMethod 2304001] 24 ComplexBlock in ExecutableBlock >> ensure: @6 line 11 [GsMethod 2304001] 25 ExceptionHandler >> caughtEx:number:cat:args:handler: @16 line 14 [GsMethod 10064641] 26 ComplexBlock in ExceptionHandler >> try:on:do: @10 line 12 [GsMethod 10062081] ----------------------------------------------------- GemStone: Error Nonfatal The object with object ID 3458764685619232777 is corrupt. Reason: 'om::RefreshObj illegal refresh of always-valid obj' Error Category: 231169 [GemStone] Number: 2261 Arg Count: 2 Context : 3166932737 Arg 1: [3166932481 sz:10 cls: 77313 LargePositiveInteger] 3458764685619232777 Arg 2: [3166932225 sz:50 cls: 74753 String] om::RefreshObj illegal refresh of always-valid obj topaz 1> ----------------------------------------------------- GemStone: Error Nonfatal Further commits have been disabled for this session because: 'CorruptObj error'. This session must logout. Error Category: 231169 [GemStone] Number: 2249 Arg Count: 1 Context : 3166895617 Arg 1: [3166895105 sz:16 cls: 74753 String] CorruptObj error Now executing the following command saved from "iferr 1": where ==> 1 System class >> _primitiveCommit: @1 line 1 [GsMethod 3226881] 2 System class >> __commit: @1 line 8 [GsMethod 3222017] 3 System class >> _localCommit: @8 line 30 [GsMethod 3222529] 4 TransactionBoundaryDefaultPolicy >> commit: @2 line 3 [GsMethod 7713281] 5 System class >> _commit: @6 line 16 [GsMethod 3222785] 6 System class >> commitTransaction @2 line 28 [GsMethod 3230465] 7 Executed Code @13 line 8 [GsMethod 3224276225] [GsProcess 3166895617] topaz 1> Mon Oct 13 17:50:53 CEST 2014 _____________________________________________________________________________ | Possible Internal Error: HostCoreDump invoked at 10/13/2014 05:50:53 PM.716 CEST in process 972 _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Johan, We have not seen this particular problem before, but you are using a fairly old version of GemStone ... It doesn't look as much like corruption as an incorrect code path being taken for the LargePositiveInteger ... LargePositiveIntegers should be invariant and never get refreshed ... we'd need a C-stack to understand more. If this becomes a persistent production error you can set GEM_HALT_ON_ERROR to 2261 to force a gem to produce a C-stack when it hits this error and we'll be able to go from there... Dale On Mon, Oct 13, 2014 at 9:31 AM, Johan Brichau via Glass <[hidden email]> wrote: Hi there, _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Free forum by Nabble | Edit this page |