Bug 45354

GemBuilder for Java

2.3, 2.2, 2.1.2, 2.1.1, 2.1, 2.0

All Platforms

3.0

GbjBroker can get object does not exist errors during gem spawning

Under rare conditions the GbjBroker may record an object does not exist error in its log and thereafter be unable to spawn additional gems for the gem pool.  The stack in the broker log will look like:

The object with object ID XXXXXXX does not exist.

1 ComplexVCBlock in GsbFPLFramework >> defaultEventErrorHandler @ 73 [GsMethod OOP 343397585] 2 ComplexBlock in GsbFPLFramework >> handleEvent: @ 18 [GsMethod OOP 98351469] 3 Object >> _gsReturnTos @ 1 [GsMethod OOP 1004741] 4 GciInterface >> nbLogin: @ 2 [GsMethod OOP 2674473] 5 GsbSCGemManager >> spawnGem: @ 6 [GsMethod OOP 245249] 6 GsbGemManager >> spawnGems:spacing: @ 13 [GsMethod OOP 240969] 7 GsbGemManager >> spawnGems: @ 8 [GsMethod OOP 240477] 8 GsbFPLClientSocket >> spawnGems: @ 4 [GsMethod OOP 246189] 9 GsbFPLMessage >> addGems: @ 6 [GsMethod OOP 5167333] 10 GsbFPLMessage >> dispatch @ 26 [GsMethod OOP 5167393] 11 GsbFPLtcmsMessage >> dispatch @ 187 [GsMethod OOP 710449] 12 GsbFPLMessage >> dispatchMarshalled @ 6 [GsMethod OOP 300353] 13 GsbFPLClientSocket >> processString: @ 7 [GsMethod OOP 244721] 14 GsbFPLClientSocket >> process @ 37 [GsMethod OOP 242481] 15 GsbClientSocket >> handleConnectedEvent @ 2 [GsMethod OOP 248293] 16 GsbClientSocket >> handleEvent @ 4 [GsMethod OOP 248105] 17 GsbFPLFramework >> handleEvent: @ 28 [GsMethod OOP 98351469] 18 GsbFPLFramework >> eventLoop: @ 22 [GsMethod OOP 234533] 19 GsbFPLFramework >> start:configKey: @ 38 [GsMethod OOP 233713] 20 GsbFPLFramework >> startBroker: @ 2 [GsMethod OOP 233649] 21 GsbFPLFramework class >> startBroker: @ 3 [GsMethod OOP 238761]

Workaround

Shutdown and restart the GbjBroker.


Last updated: 6/4/15