Smalltalk › Gemtalk › GLASS

Fwd: ProcessorScheduler error

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

6 messages Options

otto

Fwd: ProcessorScheduler error

Hi,

Andrew is not getting joy with subscribing to the mailing list, so
here's a question. Has anyone encountered this problem? Your help will
be appreciated, thanks.

Here us the package info info:
GemStone: gss64_2_4_x_branch-22581
Architecture: x86-64 (Linux)
Packages:
Hyper1.333-jgf.20
HyperSeaside-dkh.5
Seaside2.8g1-jgf.630
Here is the error:
GemStone: Error Nonfatal
The object aProcessorScheduler may not be committed, instances of
its class are non-persistent.
Error Category: 231169 [GemStone] Number: 2407 Arg Count: 1 Context : 237154049
Arg 1: [237007873 sz:11 cls: 116481 ProcessorScheduler] a ProcessorScheduler
readyQueue [236987137 sz:1 cls: 92929 SortedCollection] a SortedCollection
activeProcess [20 sz:0 cls: 76289 UndefinedObject] nil
lastGciProcess [20 sz:0 cls: 76289 UndefinedObject] nil
delayQueue [236985345 sz:2 cls: 92929 SortedCollection] a SortedCollection
lastTimeMs [20 sz:0 cls: 76289 UndefinedObject] nil
readDict [236984577 sz:14 cls: 90881
IdentityKeyValueDictionary] an IdentityKeyValueDictionary
writeDict [237007617 sz:14 cls: 90881
IdentityKeyValueDictionary] an IdentityKeyValueDictionary
suspendedDict [236982529 sz:14 cls: 90881
IdentityKeyValueDictionary] an IdentityKeyValueDictionary
waitingSet [236982017 sz:5 cls: 73985 IdentitySet] an IdentitySet
lastGroup [10 sz:0 cls: 74241 SmallInteger] 1
errorEventQueue [20 sz:0 cls: 76289 UndefinedObject] nil

Now executing the following command saved from "iferr 1":
where
1 ExceptionA >> defaultAction @17 line 18 [GsMethod 11867393]
Error >> defaultAction @2 line 7 [GsMethod 11860993]
ExceptionA >> _defaultAction @1 line 4 [GsMethod 11866625]
ExceptionHandler >> outer @4 line 5 [GsMethod 11878145]
ExceptionA >> pass @2 line 11 [GsMethod 11867649]
HTTPConnection >> handleInternalServerException: @12 line 13
[GsMethod 64956417]
ComplexBlock in HTTPConnection >> internalErrorHandler @6 line 6
[GsMethod 64955905]
ExceptionHandler >> caughtExceptionWithAction: @5 line 4 [GsMethod 11881217]
ComplexBlock in ExceptionHandler >> caughtEx:number:cat:args:handler:
@12 line 13 [GsMethod 11880705]
ComplexBlock in ExecutableBlock >> ensure: @4 line 11 [GsMethod 2305025]
ComplexBlock in ExecutableBlock >> ensure: @6 line 11 [GsMethod 2305025]
ExceptionHandler >> caughtEx:number:cat:args:handler: @16 line 14
[GsMethod 11880705]
ComplexBlock in ExceptionHandler >> try:on:do: @10 line 12 [GsMethod 11879169]
Object >> _gsReturnTos @1 line 1 [GsMethod 1875713]
System class >> __commit: @1 line 8 [GsMethod 3222017]
System class >> _localCommit: @8 line 30 [GsMethod 3222273]
TransactionBoundaryDefaultPolicy >> commit: @2 line 3 [GsMethod 7703297]
System class >> _commit: @6 line 16 [GsMethod 3222529]
System class >> commitTransaction @2 line 28 [GsMethod 3229185]
System class >> _commitPrintingDiagnostics @2 line 9 [GsMethod 3151361]
SystemCommitTransaction >> defaultAction @1 line 3 [GsMethod 46338561]
ExceptionA >> _defaultAction @1 line 4 [GsMethod 11866625]
ExceptionA >> signal @7 line 37 [GsMethod 11872513]
ExceptionA >> signal: @3 line 12 [GsMethod 11867137]
ExceptionA class >> signal: @2 line 3 [GsMethod 12069121]
ExceptionA class >> signal @2 line 9 [GsMethod 12068865]
SeasidePlatformSupport class >> doCommitTransaction @6 line 9
[GsMethod 67120385]
SeasideHTTPService >> doCommitTransaction @4 line 4 [GsMethod 47277057]
ComplexVCBlock in SeasideHTTPService >> answerToCheckingLock: @43 line
34 [GsMethod 47281665]
ComplexBlock in ExecutableBlock >> ensure: @4 line 11 [GsMethod 2305025]
ComplexVCBlock in ExecutableBlock >> ensure: @6 line 11 [GsMethod 2305025]
TransientRecursionLock >> critical: @15 line 8 [GsMethod 20958721]
SeasideHTTPService >> answerToCheckingLock: @60 line 7 [GsMethod 47281665]
SeasideHTTPService >> process: @3 line 6 [GsMethod 47281153]
ComplexBlock in SeasideHTTPService >> start @4 line 5 [GsMethod 47278081]
HTTPRequest >> respondUsing: @1 line 5 [GsMethod 43068929]
HTTPServer >> answerTo: @6 line 7 [GsMethod 43175169]
ComplexBlock in HTTPConnection >> produceResponseFor: @8 line 9
[GsMethod 64956161]
ExceptionHandler >> doTryBlock: @9 line 7 [GsMethod 11881473]
ExceptionHandler >> try:on:do: @15 line 18 [GsMethod 11879169]
ComplexBlock in ExecutableBlock >> on:do: @2 line 8 [GsMethod 9454337]
SpExceptionContext class >> for:onAnyErrorDo: @2 line 6 [GsMethod 22594305]
HTTPConnection >> produceResponseFor: @13 line 11 [GsMethod 64956161]
HTTPConnection >> getAndDispatchMessages @9 line 14 [GsMethod 64954881]
ComplexBlock in OSkSocketInboundConnection >> interact @3 line 6
[GsMethod 43563521]
ComplexBlock in ExecutableBlock >> ensure: @4 line 11 [GsMethod 2305025]
ComplexBlock in ExecutableBlock >> ensure: @6 line 11 [GsMethod 2305025]
OSkSocketInboundConnection >> interact @7 line 7 [GsMethod 43563521]
OSkSocketListenerService >> handleInboundConnectionOn: @8 line 10
[GsMethod 64521985]
ComplexBlock in OSkSocketListenerService >> acceptInboundConnections
@12 line 15 [GsMethod 64524289]
GsProcess >> _startPart2 @15 line 17 [GsMethod 4498433]
GsProcess >> _start @1 line 9 [GsMethod 4502785]

SeanTAllen

Re: Fwd: ProcessorScheduler error

You would get that error when trying to store a non persistent object
as part of a persisten root.

In this case, it would be an instance of ProcessorScheduler that you
are trying to store.
I would start by looking at the references to ProcessorScheduler and
seeing where
that might intersect with your code.

James Foster-8

Re: Fwd: ProcessorScheduler error

In reply to this post by otto

Hi Andrew,

I recently spent some time investigating this problem and entered a bug with possible fix: http://code.google.com/p/glassdb/issues/detail?id=123.

We believe that the underlying bug is fixed in last week's server release of 2.4.4 (ftp://ftp.gemstone.com/pub/GemStone64/2.4.4/GemStone64Bit2.4.4-x86_64.Linux.zip).

James

On Jul 6, 2010, at 12:34 AM, Otto Behrens wrote:

> Hi,
>
> Andrew is not getting joy with subscribing to the mailing list, so
> here's a question. Has anyone encountered this problem? Your help will
> be appreciated, thanks.
>
> Here us the package info info:
> GemStone: gss64_2_4_x_branch-22581
> Architecture: x86-64 (Linux)
> Packages:
> Hyper1.333-jgf.20
> HyperSeaside-dkh.5
> Seaside2.8g1-jgf.630
> Here is the error:
> GemStone: Error Nonfatal
> The object aProcessorScheduler may not be committed, instances of
> its class are non-persistent.
> Error Category: 231169 [GemStone] Number: 2407 Arg Count: 1 Context : 237154049
> Arg 1: [237007873 sz:11 cls: 116481 ProcessorScheduler] a ProcessorScheduler
> readyQueue [236987137 sz:1 cls: 92929 SortedCollection] a SortedCollection
> activeProcess [20 sz:0 cls: 76289 UndefinedObject] nil
> lastGciProcess [20 sz:0 cls: 76289 UndefinedObject] nil
> delayQueue [236985345 sz:2 cls: 92929 SortedCollection] a SortedCollection
> lastTimeMs [20 sz:0 cls: 76289 UndefinedObject] nil
> readDict [236984577 sz:14 cls: 90881
> IdentityKeyValueDictionary] an IdentityKeyValueDictionary
> writeDict [237007617 sz:14 cls: 90881
> IdentityKeyValueDictionary] an IdentityKeyValueDictionary
> suspendedDict [236982529 sz:14 cls: 90881
> IdentityKeyValueDictionary] an IdentityKeyValueDictionary
> waitingSet [236982017 sz:5 cls: 73985 IdentitySet] an IdentitySet
> lastGroup [10 sz:0 cls: 74241 SmallInteger] 1
> errorEventQueue [20 sz:0 cls: 76289 UndefinedObject] nil
>
>
> Now executing the following command saved from "iferr 1":
> where
> 1 ExceptionA >> defaultAction @17 line 18 [GsMethod 11867393]
> Error >> defaultAction @2 line 7 [GsMethod 11860993]
> ExceptionA >> _defaultAction @1 line 4 [GsMethod 11866625]
> ExceptionHandler >> outer @4 line 5 [GsMethod 11878145]
> ExceptionA >> pass @2 line 11 [GsMethod 11867649]
> HTTPConnection >> handleInternalServerException: @12 line 13
> [GsMethod 64956417]
> ComplexBlock in HTTPConnection >> internalErrorHandler @6 line 6
> [GsMethod 64955905]
> ExceptionHandler >> caughtExceptionWithAction: @5 line 4 [GsMethod 11881217]
> ComplexBlock in ExceptionHandler >> caughtEx:number:cat:args:handler:
> @12 line 13 [GsMethod 11880705]
> ComplexBlock in ExecutableBlock >> ensure: @4 line 11 [GsMethod 2305025]
> ComplexBlock in ExecutableBlock >> ensure: @6 line 11 [GsMethod 2305025]
> ExceptionHandler >> caughtEx:number:cat:args:handler: @16 line 14
> [GsMethod 11880705]
> ComplexBlock in ExceptionHandler >> try:on:do: @10 line 12 [GsMethod 11879169]
> Object >> _gsReturnTos @1 line 1 [GsMethod 1875713]
> System class >> __commit: @1 line 8 [GsMethod 3222017]
> System class >> _localCommit: @8 line 30 [GsMethod 3222273]
> TransactionBoundaryDefaultPolicy >> commit: @2 line 3 [GsMethod 7703297]
> System class >> _commit: @6 line 16 [GsMethod 3222529]
> System class >> commitTransaction @2 line 28 [GsMethod 3229185]
> System class >> _commitPrintingDiagnostics @2 line 9 [GsMethod 3151361]
> SystemCommitTransaction >> defaultAction @1 line 3 [GsMethod 46338561]
> ExceptionA >> _defaultAction @1 line 4 [GsMethod 11866625]
> ExceptionA >> signal @7 line 37 [GsMethod 11872513]
> ExceptionA >> signal: @3 line 12 [GsMethod 11867137]
> ExceptionA class >> signal: @2 line 3 [GsMethod 12069121]
> ExceptionA class >> signal @2 line 9 [GsMethod 12068865]
> SeasidePlatformSupport class >> doCommitTransaction @6 line 9
> [GsMethod 67120385]
> SeasideHTTPService >> doCommitTransaction @4 line 4 [GsMethod 47277057]
> ComplexVCBlock in SeasideHTTPService >> answerToCheckingLock: @43 line
> 34 [GsMethod 47281665]
> ComplexBlock in ExecutableBlock >> ensure: @4 line 11 [GsMethod 2305025]
> ComplexVCBlock in ExecutableBlock >> ensure: @6 line 11 [GsMethod 2305025]
> TransientRecursionLock >> critical: @15 line 8 [GsMethod 20958721]
> SeasideHTTPService >> answerToCheckingLock: @60 line 7 [GsMethod 47281665]
> SeasideHTTPService >> process: @3 line 6 [GsMethod 47281153]
> ComplexBlock in SeasideHTTPService >> start @4 line 5 [GsMethod 47278081]
> HTTPRequest >> respondUsing: @1 line 5 [GsMethod 43068929]
> HTTPServer >> answerTo: @6 line 7 [GsMethod 43175169]
> ComplexBlock in HTTPConnection >> produceResponseFor: @8 line 9
> [GsMethod 64956161]
> ExceptionHandler >> doTryBlock: @9 line 7 [GsMethod 11881473]
> ExceptionHandler >> try:on:do: @15 line 18 [GsMethod 11879169]
> ComplexBlock in ExecutableBlock >> on:do: @2 line 8 [GsMethod 9454337]
> SpExceptionContext class >> for:onAnyErrorDo: @2 line 6 [GsMethod 22594305]
> HTTPConnection >> produceResponseFor: @13 line 11 [GsMethod 64956161]
> HTTPConnection >> getAndDispatchMessages @9 line 14 [GsMethod 64954881]
> ComplexBlock in OSkSocketInboundConnection >> interact @3 line 6
> [GsMethod 43563521]
> ComplexBlock in ExecutableBlock >> ensure: @4 line 11 [GsMethod 2305025]
> ComplexBlock in ExecutableBlock >> ensure: @6 line 11 [GsMethod 2305025]
> OSkSocketInboundConnection >> interact @7 line 7 [GsMethod 43563521]
> OSkSocketListenerService >> handleInboundConnectionOn: @8 line 10
> [GsMethod 64521985]
> ComplexBlock in OSkSocketListenerService >> acceptInboundConnections
> @12 line 15 [GsMethod 64524289]
> GsProcess >> _startPart2 @15 line 17 [GsMethod 4498433]
> GsProcess >> _start @1 line 9 [GsMethod 4502785]

Dale Henrichs

Re: Fwd: ProcessorScheduler error

In reply to this post by otto

Andrew,

In the Seaside variant of
http://code.google.com/p/glassdb/issues/detail?id=123, the reference to
a Semaphore occurred because a process fork is performed inside a
#callback: block...it is conceivable that a reference to a
ProcessShcheduler instance could come from the same bug ...

Are you doing any forking or explicitly monkeying with the
ProcessScheduler or Processes in your Seaside component?

Dale

Otto Behrens wrote:

Dale Henrichs

Re: Fwd: ProcessorScheduler error

In reply to this post by James Foster-8

As to downloading and using the 2.4.4 release, I would prefer that folks
wait until I have announced Seaside support for 2.4.

Up until now folks that are using 2.4 are doing so because they are
using Seaside3.0.

I have yet to validate the server upgrade process from 2.3 to 2.4 for
Seaside something that I will be working on when I return from vacation
(later this week)...this means that I have not completely characterized
the issues that you _will_ run into if you try to upgrade from 2.3 to
2.4. When I announce support there will be a concurrent 2.4.4.x release
of the server as well.

If you insist on using 2.4.4 today, then you need to bootstrap your
extent (do not use the seaside extent that is shipped with 2.4.4).

If you want to use Seaside3.0 then you need to get additional
information from me for working with Seaside3.0 since the currently
released version is very bleeding edge in terms of development within
the GemStone environment...the soon-to-be-announced Seaside3.0 will
include support for remote debugging, Magritte2 and Pier2, but I am not
ready today to announce support (especially since I am still on vacation).

Dale

James Foster wrote:

> Hi Andrew,
>
> I recently spent some time investigating this problem and entered a bug with possible fix: http://code.google.com/p/glassdb/issues/detail?id=123.
>
> We believe that the underlying bug is fixed in last week's server release of 2.4.4 (ftp://ftp.gemstone.com/pub/GemStone64/2.4.4/GemStone64Bit2.4.4-x86_64.Linux.zip).
>
> James
>
> On Jul 6, 2010, at 12:34 AM, Otto Behrens wrote:
>
>> Hi,
>>
>> Andrew is not getting joy with subscribing to the mailing list, so
>> here's a question. Has anyone encountered this problem? Your help will
>> be appreciated, thanks.
>>
>> Here us the package info info:
>> GemStone: gss64_2_4_x_branch-22581
>> Architecture: x86-64 (Linux)
>> Packages:
>> Hyper1.333-jgf.20
>> HyperSeaside-dkh.5
>> Seaside2.8g1-jgf.630
>> Here is the error:
>> GemStone: Error Nonfatal
>> The object aProcessorScheduler may not be committed, instances of
>> its class are non-persistent.
>> Error Category: 231169 [GemStone] Number: 2407 Arg Count: 1 Context : 237154049
>> Arg 1: [237007873 sz:11 cls: 116481 ProcessorScheduler] a ProcessorScheduler
>> readyQueue [236987137 sz:1 cls: 92929 SortedCollection] a SortedCollection
>> activeProcess [20 sz:0 cls: 76289 UndefinedObject] nil
>> lastGciProcess [20 sz:0 cls: 76289 UndefinedObject] nil
>> delayQueue [236985345 sz:2 cls: 92929 SortedCollection] a SortedCollection
>> lastTimeMs [20 sz:0 cls: 76289 UndefinedObject] nil
>> readDict [236984577 sz:14 cls: 90881
>> IdentityKeyValueDictionary] an IdentityKeyValueDictionary
>> writeDict [237007617 sz:14 cls: 90881
>> IdentityKeyValueDictionary] an IdentityKeyValueDictionary
>> suspendedDict [236982529 sz:14 cls: 90881
>> IdentityKeyValueDictionary] an IdentityKeyValueDictionary
>> waitingSet [236982017 sz:5 cls: 73985 IdentitySet] an IdentitySet
>> lastGroup [10 sz:0 cls: 74241 SmallInteger] 1
>> errorEventQueue [20 sz:0 cls: 76289 UndefinedObject] nil
>>
>>
>> Now executing the following command saved from "iferr 1":
>> where
>> 1 ExceptionA >> defaultAction @17 line 18 [GsMethod 11867393]
>> Error >> defaultAction @2 line 7 [GsMethod 11860993]
>> ExceptionA >> _defaultAction @1 line 4 [GsMethod 11866625]
>> ExceptionHandler >> outer @4 line 5 [GsMethod 11878145]
>> ExceptionA >> pass @2 line 11 [GsMethod 11867649]
>> HTTPConnection >> handleInternalServerException: @12 line 13
>> [GsMethod 64956417]
>> ComplexBlock in HTTPConnection >> internalErrorHandler @6 line 6
>> [GsMethod 64955905]
>> ExceptionHandler >> caughtExceptionWithAction: @5 line 4 [GsMethod 11881217]
>> ComplexBlock in ExceptionHandler >> caughtEx:number:cat:args:handler:
>> @12 line 13 [GsMethod 11880705]
>> ComplexBlock in ExecutableBlock >> ensure: @4 line 11 [GsMethod 2305025]
>> ComplexBlock in ExecutableBlock >> ensure: @6 line 11 [GsMethod 2305025]
>> ExceptionHandler >> caughtEx:number:cat:args:handler: @16 line 14
>> [GsMethod 11880705]
>> ComplexBlock in ExceptionHandler >> try:on:do: @10 line 12 [GsMethod 11879169]
>> Object >> _gsReturnTos @1 line 1 [GsMethod 1875713]
>> System class >> __commit: @1 line 8 [GsMethod 3222017]
>> System class >> _localCommit: @8 line 30 [GsMethod 3222273]
>> TransactionBoundaryDefaultPolicy >> commit: @2 line 3 [GsMethod 7703297]
>> System class >> _commit: @6 line 16 [GsMethod 3222529]
>> System class >> commitTransaction @2 line 28 [GsMethod 3229185]
>> System class >> _commitPrintingDiagnostics @2 line 9 [GsMethod 3151361]
>> SystemCommitTransaction >> defaultAction @1 line 3 [GsMethod 46338561]
>> ExceptionA >> _defaultAction @1 line 4 [GsMethod 11866625]
>> ExceptionA >> signal @7 line 37 [GsMethod 11872513]
>> ExceptionA >> signal: @3 line 12 [GsMethod 11867137]
>> ExceptionA class >> signal: @2 line 3 [GsMethod 12069121]
>> ExceptionA class >> signal @2 line 9 [GsMethod 12068865]
>> SeasidePlatformSupport class >> doCommitTransaction @6 line 9
>> [GsMethod 67120385]
>> SeasideHTTPService >> doCommitTransaction @4 line 4 [GsMethod 47277057]
>> ComplexVCBlock in SeasideHTTPService >> answerToCheckingLock: @43 line
>> 34 [GsMethod 47281665]
>> ComplexBlock in ExecutableBlock >> ensure: @4 line 11 [GsMethod 2305025]
>> ComplexVCBlock in ExecutableBlock >> ensure: @6 line 11 [GsMethod 2305025]
>> TransientRecursionLock >> critical: @15 line 8 [GsMethod 20958721]
>> SeasideHTTPService >> answerToCheckingLock: @60 line 7 [GsMethod 47281665]
>> SeasideHTTPService >> process: @3 line 6 [GsMethod 47281153]
>> ComplexBlock in SeasideHTTPService >> start @4 line 5 [GsMethod 47278081]
>> HTTPRequest >> respondUsing: @1 line 5 [GsMethod 43068929]
>> HTTPServer >> answerTo: @6 line 7 [GsMethod 43175169]
>> ComplexBlock in HTTPConnection >> produceResponseFor: @8 line 9
>> [GsMethod 64956161]
>> ExceptionHandler >> doTryBlock: @9 line 7 [GsMethod 11881473]
>> ExceptionHandler >> try:on:do: @15 line 18 [GsMethod 11879169]
>> ComplexBlock in ExecutableBlock >> on:do: @2 line 8 [GsMethod 9454337]
>> SpExceptionContext class >> for:onAnyErrorDo: @2 line 6 [GsMethod 22594305]
>> HTTPConnection >> produceResponseFor: @13 line 11 [GsMethod 64956161]
>> HTTPConnection >> getAndDispatchMessages @9 line 14 [GsMethod 64954881]
>> ComplexBlock in OSkSocketInboundConnection >> interact @3 line 6
>> [GsMethod 43563521]
>> ComplexBlock in ExecutableBlock >> ensure: @4 line 11 [GsMethod 2305025]
>> ComplexBlock in ExecutableBlock >> ensure: @6 line 11 [GsMethod 2305025]
>> OSkSocketInboundConnection >> interact @7 line 7 [GsMethod 43563521]
>> OSkSocketListenerService >> handleInboundConnectionOn: @8 line 10
>> [GsMethod 64521985]
>> ComplexBlock in OSkSocketListenerService >> acceptInboundConnections
>> @12 line 15 [GsMethod 64524289]
>> GsProcess >> _startPart2 @15 line 17 [GsMethod 4498433]
>> GsProcess >> _start @1 line 9 [GsMethod 4502785]
>

Dale Henrichs

Re: Fwd: ProcessorScheduler error

In reply to this post by James Foster-8

Additional info regarding
http://code.google.com/p/glassdb/issues/detail?id=123.

There _is_ a smalltalk-level patch described in Issue 123 that may work
until 2.4.4.x is ready for Seaside users.

Dale

James Foster wrote: