• Bug
  • Status: Closed
  • 1 Critical
  • Resolution: Cannot Reproduce
  • ssubbiah
  • Reporter: foshea
  • August 01, 2007
  • 0
  • Watchers: 0
  • July 27, 2012
  • August 15, 2007

Description

http://forums.terracotta.org/forums/posts/list/357.page

2007-07-31 22:13:18,765 INFO - Terracotta Server has started up as ACTIVE node on port 9510 successfully, and is now ready for work. Exception in thread “WorkerThread(managed_object_fault_stage,1)” java.lang.AssertionError: Request for a non-existent object: ObjectID=[121033] at com.tc.objectserver.impl.ObjectManagerImpl.getOrLookupReference(ObjectManagerImpl.java:299) at com.tc.objectserver.impl.ObjectManagerImpl.basicLookupObjectsFor(ObjectManagerImpl.java:433) at com.tc.objectserver.impl.ObjectManagerImpl.processPendingLookups(ObjectManagerImpl.java:777) at com.tc.objectserver.impl.ObjectManagerImpl.postRelease(ObjectManagerImpl.java:576) at com.tc.objectserver.impl.ObjectManagerImpl.addFaultedObject(ObjectManagerImpl.java:351) at com.tc.objectserver.handler.ManagedObjectFaultHandler.handleEvent(ManagedObjectFaultHandler.java:34) at com.tc.async.impl.StageImpl$WorkerThread.run(StageImpl.java:140) java.lang.AssertionError: Request for a non-existent object: ObjectID=[121033] at com.tc.objectserver.impl.ObjectManagerImpl.getOrLookupReference(ObjectManagerImpl.java:299) at com.tc.objectserver.impl.ObjectManagerImpl.basicLookupObjectsFor(ObjectManagerImpl.java:433) at com.tc.objectserver.impl.ObjectManagerImpl.processPendingLookups(ObjectManagerImpl.java:777) at com.tc.objectserver.impl.ObjectManagerImpl.postRelease(ObjectManagerImpl.java:576) at com.tc.objectserver.impl.ObjectManagerImpl.addFaultedObject(ObjectManagerImpl.java:351) at com.tc.objectserver.handler.ManagedObjectFaultHandler.handleEvent(ManagedObjectFaultHandler.java:34) at com.tc.async.impl.StageImpl$WorkerThread.run(StageImpl.java:140)

Comments

Fiona OShea 2007-08-15

Is this the same issues as DEV-838 and DEV-822? thanks

Saravanan Subbiah 2007-08-15

He was actually not using DMI but he doesnt have the bandwidth to test it with the latest 2.4.1

We have fixed a couple of issues in 2.4.1 with exact symptoms and since we dont have the app inhouse, there is no way to verify which is unfortunate. I am closing this until someone comes back to us with the same problem with 2.4.1 or later release.