Description Anders Forsell 2009-02-25 08:42:25 EST

I have turned on change policy "CDOAdapterPolicy.ALL" for my transaction. I do get the expected EMF notifications on the client, but I am also getting a NullPointerException in "handleInvalidation", CDOViewImpl line 1083, "synchronized (objects)", where objects is null (stack trace is below).
Also, the NPE was seen in "reload()" line 1340, "synchronized (object)".

I am using CDO 2.0 (M5).

Could it be a race condition where the "doDeactivate()" sets "objects" to null, and then other threads are accessing the "handleInvalidation" or "reload" methods?

The following state of the CDOTransaction was copied from the debugger, when it was stopped in "handleInvalidation":

adapterPolicyManager	CDOViewImpl$AdapterManager  (id=194)	
changeSubscriptionManager	null	
conflict	0	
dirty	false	
featureAnalyzer	null	
firstSavepoint	null	
handlers	ArrayList<E>  (id=202)	
lastCommitTime	0	
lastLookupID	null	
lastLookupObject	null	
lastSavepoint	null	
lastTemporaryID	0	
lifecycleSemaphore	Semaphore  (id=207)	
lifecycleState	ILifecycleState  (id=209)	
listeners	ArrayList<E>  (id=211)	
lock	ReentrantLock  (id=213)	
objects	null	
options	null	
rootResource	null	
session	null	
store	null	
transactionStrategy	null	
uriHandler	CDOURIHandler  (id=221)	
viewID	9	
viewSet	null	

This is the stack trace:

!ENTRY org.eclipse.emf.cdo 4 0 2009-02-25 14:29:36.913
!MESSAGE NullPointerException
!STACK 0
java.lang.NullPointerException
	at org.eclipse.emf.internal.cdo.view.CDOViewImpl.handleInvalidation(CDOViewImpl.java:1086)
	at org.eclipse.emf.internal.cdo.session.CDOSessionImpl$1.run(CDOSessionImpl.java:570)
	at org.eclipse.net4j.util.concurrent.QueueRunner.work(QueueRunner.java:26)
	at org.eclipse.net4j.util.concurrent.QueueRunner.work(QueueRunner.java:1)
	at org.eclipse.net4j.util.concurrent.QueueWorker.work(QueueWorker.java:64)
	at org.eclipse.net4j.util.concurrent.Worker$WorkerThread.run(Worker.java:154)