Issue 290 in glassdb: transactionMutex is always nil

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium GLASS-Server Version-GLASS0.231

New issue 290 by [hidden email]: transactionMutex is always nil
http://code.google.com/p/glassdb/issues/detail?id=290

The transactionMutex of GRGemStonePlatform is always nil because an  
abort/begin happens right after having created the semaphore. This prevents  
the critical section from being a critical section.

Possible solutions:
- initialize the class variable when starting the seaside gem
- do a commit in the lazy initialization block
- use a session var

Updates:
        Status: Accepted
        Owner: [hidden email]

Comment #1 on issue 290 by [hidden email]: transactionMutex is always  
nil
http://code.google.com/p/glassdb/issues/detail?id=290

The right answer is to initialize the class variable during class  
initialization ... but that doesn't patch existing implementations ... I  
think I'll add a post load doit that ensures that the mutex is  
initialized...

Updates:
        Status: Ready

Comment #2 on issue 290 by [hidden email]: transactionMutex is always  
nil
http://code.google.com/p/glassdb/issues/detail?id=290

fixed in Grease-GemStone-Core-dkh.40...fix when integrated into Grease  
1.0.6 (1.0.5.1 is a branch that shouldn't be used in general)

Updates:
        Status: Fixed

Comment #3 on issue 290 by [hidden email]: transactionMutex is always  
nil
http://code.google.com/p/glassdb/issues/detail?id=290

Grease 1.0.6 (dkh.154)

Updates:
        Labels: -GLASS-Server -Version-GLASS0.231 GLASS-Grease Version-Grease1.0.5  
Fixed-1.0.6

Comment #4 on issue 290 by [hidden email]: transactionMutex is always  
nil
http://code.google.com/p/glassdb/issues/detail?id=290

(No comment was entered for this change.)