|
| Re: [CDO] NullPointerException in CDODataOutputImpl.writeCDOIDAndVersion() [message #666275 is a reply to message #666145] |
Tue, 19 April 2011 17:12   |
|
Hi Michal,
I can not make a sense out of it either. Maybe you can set a breakpoint in org.eclipse.emf.cdo.internal.server.SessionManager.handleNot ificationProblem(InternalSession, Throwable) and see if that helps you to make it reproducible. If you can reproduce it, please submit a bugzilla. Sorry that I can't say more now.
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
Am 19.04.2011 12:24, schrieb Michał Tkacz:
> I'm getting this exception lately and wondered if it could be caused by a recent (February 19th) change to TransactionCommitContext.detachObjects()? Earlier a list was used for detachedRevisions an it was impossible to have null in the list, now however an array is used and the the old "if (revision != null)" doesn't help anymore.
>
> Note that I still don't how to reproduce it, so what I wrote above is just a wild guess. I imagine detachedObjects are filled when objects are removed from objects' graph, but I'm not sure when revisionManager.getCache().getRevision() may return null or whether it is normal.
>
> I'm using CDO 4.0 build #1255 (M6).
>
> Michal
>
> java.lang.NullPointerException
> at org.eclipse.emf.cdo.internal.common.protocol.CDODataOutputIm pl.writeCDOIDAndVersion(CDODataOutputImpl.java:263)
> at org.eclipse.emf.cdo.internal.common.protocol.CDODataOutputIm pl.writeCDOChangeSetData(CDODataOutputImpl.java:184)
> at org.eclipse.emf.cdo.internal.common.protocol.CDODataOutputIm pl.writeCDOCommitData(CDODataOutputImpl.java:197)
> at org.eclipse.emf.cdo.internal.common.protocol.CDODataOutputIm pl.writeCDOCommitInfo(CDODataOutputImpl.java:212)
> at org.eclipse.emf.cdo.server.internal.net4j.protocol.CommitNot ificationRequest.requesting(CommitNotificationRequest.java:3 7)
> at org.eclipse.emf.cdo.server.internal.net4j.protocol.CDOServer Request.requesting(CDOServerRequest.java:49)
> at org.eclipse.net4j.signal.Request.doExtendedOutput(Request.ja va:65)
> at org.eclipse.net4j.signal.Signal.doOutput(Signal.java:296)
> at org.eclipse.net4j.signal.Request.doExecute(Request.java:57)
> at org.eclipse.net4j.signal.SignalActor.execute(SignalActor.jav a:51)
> at org.eclipse.net4j.signal.Signal.runSync(Signal.java:251)
> at org.eclipse.net4j.signal.SignalProtocol.startSignal(SignalPr otocol.java:396)
> at org.eclipse.net4j.signal.Request.sendAsync(Request.java:51)
> at org.eclipse.emf.cdo.server.internal.net4j.protocol.CDOServer Protocol.sendCommitNotification(CDOServerProtocol.java:125)
> at org.eclipse.emf.cdo.internal.server.Session.sendCommitNotifi cation(Session.java:378)
> at org.eclipse.emf.cdo.internal.server.SessionManager.sendCommi tNotification(SessionManager.java:299)
> at org.eclipse.emf.cdo.internal.server.Repository.sendCommitNot ification(Repository.java:852)
> at org.eclipse.emf.cdo.internal.server.TransactionCommitContext .postCommit(TransactionCommitContext.java:528)
> at org.eclipse.emf.cdo.server.internal.net4j.protocol.CommitTra nsactionIndication.responding(CommitTransactionIndication.ja va:263)
> at org.eclipse.emf.cdo.server.internal.net4j.protocol.CDOServer IndicationWithMonitoring.responding(CDOServerIndicationWithM onitoring.java:170)
> at org.eclipse.net4j.signal.IndicationWithMonitoring.responding (IndicationWithMonitoring.java:90)
> at org.eclipse.net4j.signal.IndicationWithResponse.doExtendedOu tput(IndicationWithResponse.java:96)
> at org.eclipse.net4j.signal.Signal.doOutput(Signal.java:296)
> at org.eclipse.net4j.signal.IndicationWithResponse.execute(Indi cationWithResponse.java:65)
> at org.eclipse.net4j.signal.IndicationWithMonitoring.execute(In dicationWithMonitoring.java:63)
> at org.eclipse.net4j.signal.Signal.runSync(Signal.java:251)
> at org.eclipse.net4j.signal.Signal.run(Signal.java:147)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unkno wn Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
| Re: [CDO] NullPointerException in CDODataOutputImpl.writeCDOIDAndVersion() [message #666615 is a reply to message #666275] |
Thu, 21 April 2011 10:29 |
 Michal Tkacz
Messages: 105
Registered: July 2009 |
Senior Member |
|
|
Ok, I'll try that next week.
Michal
On 04/19/2011 07:12 PM, Eike Stepper wrote:
> Hi Michal,
>
> I can not make a sense out of it either. Maybe you can set a breakpoint
> in
> org.eclipse.emf.cdo.internal.server.SessionManager.handleNot ificationProblem(InternalSession,
> Throwable) and see if that helps you to make it reproducible. If you can
> reproduce it, please submit a bugzilla. Sorry that I can't say more now.
>
> Cheers
> /Eike
>
> ----
> http://www.esc-net.de
> http://thegordian.blogspot.com
> http://twitter.com/eikestepper
>
>
>
> Am 19.04.2011 12:24, schrieb Michał Tkacz:
>> I'm getting this exception lately and wondered if it could be caused
>> by a recent (February 19th) change to
>> TransactionCommitContext.detachObjects()? Earlier a list was used for
>> detachedRevisions an it was impossible to have null in the list, now
>> however an array is used and the the old "if (revision != null)"
>> doesn't help anymore.
>>
>> Note that I still don't how to reproduce it, so what I wrote above is
>> just a wild guess. I imagine detachedObjects are filled when objects
>> are removed from objects' graph, but I'm not sure when
>> revisionManager.getCache().getRevision() may return null or whether it
>> is normal.
>>
>> I'm using CDO 4.0 build #1255 (M6).
>>
>> Michal
>>
>> java.lang.NullPointerException
>> at
>> org.eclipse.emf.cdo.internal.common.protocol.CDODataOutputIm pl.writeCDOIDAndVersion(CDODataOutputImpl.java:263)
>>
>> at
>> org.eclipse.emf.cdo.internal.common.protocol.CDODataOutputIm pl.writeCDOChangeSetData(CDODataOutputImpl.java:184)
>>
>> at
>> org.eclipse.emf.cdo.internal.common.protocol.CDODataOutputIm pl.writeCDOCommitData(CDODataOutputImpl.java:197)
>>
>> at
>> org.eclipse.emf.cdo.internal.common.protocol.CDODataOutputIm pl.writeCDOCommitInfo(CDODataOutputImpl.java:212)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.net4j.protocol.CommitNot ificationRequest.requesting(CommitNotificationRequest.java:3 7)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.net4j.protocol.CDOServer Request.requesting(CDOServerRequest.java:49)
>>
>> at org.eclipse.net4j.signal.Request.doExtendedOutput(Request.ja va:65)
>> at org.eclipse.net4j.signal.Signal.doOutput(Signal.java:296)
>> at org.eclipse.net4j.signal.Request.doExecute(Request.java:57)
>> at org.eclipse.net4j.signal.SignalActor.execute(SignalActor.jav a:51)
>> at org.eclipse.net4j.signal.Signal.runSync(Signal.java:251)
>> at
>> org.eclipse.net4j.signal.SignalProtocol.startSignal(SignalPr otocol.java:396)
>>
>> at org.eclipse.net4j.signal.Request.sendAsync(Request.java:51)
>> at
>> org.eclipse.emf.cdo.server.internal.net4j.protocol.CDOServer Protocol.sendCommitNotification(CDOServerProtocol.java:125)
>>
>> at
>> org.eclipse.emf.cdo.internal.server.Session.sendCommitNotifi cation(Session.java:378)
>>
>> at
>> org.eclipse.emf.cdo.internal.server.SessionManager.sendCommi tNotification(SessionManager.java:299)
>>
>> at
>> org.eclipse.emf.cdo.internal.server.Repository.sendCommitNot ification(Repository.java:852)
>>
>> at
>> org.eclipse.emf.cdo.internal.server.TransactionCommitContext .postCommit(TransactionCommitContext.java:528)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.net4j.protocol.CommitTra nsactionIndication.responding(CommitTransactionIndication.ja va:263)
>>
>> at
>> org.eclipse.emf.cdo.server.internal.net4j.protocol.CDOServer IndicationWithMonitoring.responding(CDOServerIndicationWithM onitoring.java:170)
>>
>> at
>> org.eclipse.net4j.signal.IndicationWithMonitoring.responding (IndicationWithMonitoring.java:90)
>>
>> at
>> org.eclipse.net4j.signal.IndicationWithResponse.doExtendedOu tput(IndicationWithResponse.java:96)
>>
>> at org.eclipse.net4j.signal.Signal.doOutput(Signal.java:296)
>> at
>> org.eclipse.net4j.signal.IndicationWithResponse.execute(Indi cationWithResponse.java:65)
>>
>> at
>> org.eclipse.net4j.signal.IndicationWithMonitoring.execute(In dicationWithMonitoring.java:63)
>>
>> at org.eclipse.net4j.signal.Signal.runSync(Signal.java:251)
>> at org.eclipse.net4j.signal.Signal.run(Signal.java:147)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unkno wn Source)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
>> at java.lang.Thread.run(Unknown Source)
|
|
|
| Re: [CDO] NullPointerException in CDODataOutputImpl.writeCDOIDAndVersion() [message #666634 is a reply to message #666615] |
Thu, 21 April 2011 11:43 |
|
Am 21.04.2011 12:29, schrieb Michał Tkacz:
> Ok, I'll try that next week.
Happy Easter weekend!
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
>
> Michal
>
> On 04/19/2011 07:12 PM, Eike Stepper wrote:
>> Hi Michal,
>>
>> I can not make a sense out of it either. Maybe you can set a breakpoint
>> in
>> org.eclipse.emf.cdo.internal.server.SessionManager.handleNot ificationProblem(InternalSession,
>> Throwable) and see if that helps you to make it reproducible. If you can
>> reproduce it, please submit a bugzilla. Sorry that I can't say more now.
>>
>> Cheers
>> /Eike
>>
>> ----
>> http://www.esc-net.de
>> http://thegordian.blogspot.com
>> http://twitter.com/eikestepper
>>
>>
>>
>> Am 19.04.2011 12:24, schrieb Michał Tkacz:
>>> I'm getting this exception lately and wondered if it could be caused
>>> by a recent (February 19th) change to
>>> TransactionCommitContext.detachObjects()? Earlier a list was used for
>>> detachedRevisions an it was impossible to have null in the list, now
>>> however an array is used and the the old "if (revision != null)"
>>> doesn't help anymore.
>>>
>>> Note that I still don't how to reproduce it, so what I wrote above is
>>> just a wild guess. I imagine detachedObjects are filled when objects
>>> are removed from objects' graph, but I'm not sure when
>>> revisionManager.getCache().getRevision() may return null or whether it
>>> is normal.
>>>
>>> I'm using CDO 4.0 build #1255 (M6).
>>>
>>> Michal
>>>
>>> java.lang.NullPointerException
>>> at
>>> org.eclipse.emf.cdo.internal.common.protocol.CDODataOutputIm pl.writeCDOIDAndVersion(CDODataOutputImpl.java:263)
>>>
>>> at
>>> org.eclipse.emf.cdo.internal.common.protocol.CDODataOutputIm pl.writeCDOChangeSetData(CDODataOutputImpl.java:184)
>>>
>>> at
>>> org.eclipse.emf.cdo.internal.common.protocol.CDODataOutputIm pl.writeCDOCommitData(CDODataOutputImpl.java:197)
>>>
>>> at
>>> org.eclipse.emf.cdo.internal.common.protocol.CDODataOutputIm pl.writeCDOCommitInfo(CDODataOutputImpl.java:212)
>>>
>>> at
>>> org.eclipse.emf.cdo.server.internal.net4j.protocol.CommitNot ificationRequest.requesting(CommitNotificationRequest.java:3 7)
>>>
>>> at
>>> org.eclipse.emf.cdo.server.internal.net4j.protocol.CDOServer Request.requesting(CDOServerRequest.java:49)
>>>
>>> at org.eclipse.net4j.signal.Request.doExtendedOutput(Request.ja va:65)
>>> at org.eclipse.net4j.signal.Signal.doOutput(Signal.java:296)
>>> at org.eclipse.net4j.signal.Request.doExecute(Request.java:57)
>>> at org.eclipse.net4j.signal.SignalActor.execute(SignalActor.jav a:51)
>>> at org.eclipse.net4j.signal.Signal.runSync(Signal.java:251)
>>> at
>>> org.eclipse.net4j.signal.SignalProtocol.startSignal(SignalPr otocol.java:396)
>>>
>>> at org.eclipse.net4j.signal.Request.sendAsync(Request.java:51)
>>> at
>>> org.eclipse.emf.cdo.server.internal.net4j.protocol.CDOServer Protocol.sendCommitNotification(CDOServerProtocol.java:125)
>>>
>>> at
>>> org.eclipse.emf.cdo.internal.server.Session.sendCommitNotifi cation(Session.java:378)
>>>
>>> at
>>> org.eclipse.emf.cdo.internal.server.SessionManager.sendCommi tNotification(SessionManager.java:299)
>>>
>>> at
>>> org.eclipse.emf.cdo.internal.server.Repository.sendCommitNot ification(Repository.java:852)
>>>
>>> at
>>> org.eclipse.emf.cdo.internal.server.TransactionCommitContext .postCommit(TransactionCommitContext.java:528)
>>>
>>> at
>>> org.eclipse.emf.cdo.server.internal.net4j.protocol.CommitTra nsactionIndication.responding(CommitTransactionIndication.ja va:263)
>>>
>>> at
>>> org.eclipse.emf.cdo.server.internal.net4j.protocol.CDOServer IndicationWithMonitoring.responding(CDOServerIndicationWithM onitoring.java:170)
>>>
>>> at
>>> org.eclipse.net4j.signal.IndicationWithMonitoring.responding (IndicationWithMonitoring.java:90)
>>>
>>> at
>>> org.eclipse.net4j.signal.IndicationWithResponse.doExtendedOu tput(IndicationWithResponse.java:96)
>>>
>>> at org.eclipse.net4j.signal.Signal.doOutput(Signal.java:296)
>>> at
>>> org.eclipse.net4j.signal.IndicationWithResponse.execute(Indi cationWithResponse.java:65)
>>>
>>> at
>>> org.eclipse.net4j.signal.IndicationWithMonitoring.execute(In dicationWithMonitoring.java:63)
>>>
>>> at org.eclipse.net4j.signal.Signal.runSync(Signal.java:251)
>>> at org.eclipse.net4j.signal.Signal.run(Signal.java:147)
>>> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unkno wn Source)
>>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
>>> at java.lang.Thread.run(Unknown Source)
>
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
Powered by
FUDForum. Page generated in 0.02265 seconds
] 
Search
Help
Register
Login
Home
