Description Frieder Jacobi 2011-02-10 10:41:13 EST

Build Identifier: M20100909-0800

The exception is thrown in two scenarios: on the server side (A) as well as on the client side (B).

The reason is the implementation of AbstractCDORevision.hashCode(), which is called right after the constructor and makes use of this.getId()/this.getBranch(), which return null. Unfortunately, none of the revision object's fields has a value other than 0/null, which makes the call of hashCode at this time kind of meaningless. But it is called, since the fresh revision has to be put into a hash map...

The stack trace:

java.lang.NullPointerException
	at org.eclipse.emf.cdo.spi.common.revision.AbstractCDORevision.hashCode(AbstractCDORevision.java:137)
	at java.util.concurrent.ConcurrentHashMap.put(Unknown Source)
	at org.eclipse.net4j.util.om.trace.PerfTracer.start(PerfTracer.java:34)
	at org.eclipse.emf.cdo.spi.common.revision.BaseCDORevision.read(BaseCDORevision.java:127)
	at org.eclipse.emf.cdo.internal.common.protocol.CDODataInputImpl.readCDORevision(CDODataInputImpl.java:371)
        ...

Reproducible: Always

Steps to Reproduce:
scenario A/server side:
1. Enable tracing for the run configuration of the server, check project "org.eclipse.emf.cdo.common (4.0.0)", check all of "perf*" in the right part.
2. Switch to CDO perspective.
3. In "CDO Sessions" view, create a new session, a transaction, and create a new resource in this transaction.
4. Commit this transaction: the NPE is thrown on server side.

scenario B/client side:
1. Enable tracing for the run configuration of the client, check project "org.eclipse.emf.cdo.common (4.0.0)", check all of "perf*" in the right part.
2. Switch to CDO perspective.
3. In "CDO Sessions" view, create a new session.
4. Create a transaction: the NPE is thrown on client side.