|
| Re: [CDO] BasicIndexOutOfBoundsException while opening a viewPart [message #1729234 is a reply to message #1728108] |
Tue, 12 April 2016 10:35  |
|
Hi Maxime,
Please see my inline comments below...
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
Am 31.03.2016 um 15:42 schrieb Maxime Romand:
> Hi,
>
> I have an eclipse RCP application that use CDO.
> The basic layout is a CDO Server on a computer and several client applications on others computers connected to it.
> I use one CDORessource.
>
> Each Client has a CDOView opened on this resource.
>
> Sometimes (5%-10% of the time I'd say) on a client when I open a specific viewPart that call the model on the CDOview ,
It's impossible for me to test this unless you can provide a test case or the exact steps to reproduce the problem ;-(
If you want to play with our cool test bed (see subclasses of AbstractCDOTest) and need some pointers, let me know.
> The view doesn't open and I got the following stacktrace
>
>
> !ENTRY org.eclipse.e4.ui.workbench 4 0 2016-03-29 13:25:22.615
> !MESSAGE !STACK 0
> org.eclipse.net4j.signal.RemoteException: org.eclipse.emf.common.util.BasicEList$BasicIndexOutOfBoundsException:
> index=2, size=2
> at org.eclipse.emf.common.util.BasicEList.get(BasicEList.java:346)
> at org.eclipse.emf.cdo.server.internal.net4j.protocol.LoadChunkIndication.responding(LoadChunkIndication.java:105)
The fact that the server executes a LoadChunkIndication means that the client has a CDORevision with partially loaded
lists/collections. That probably means that you configured your CDOSession with setCollectionLoadingPolicy(). Most
likely you can prevent the problem by commenting that call out.
> at org.eclipse.emf.cdo.server.internal.net4j.protocol.CDOServerIndication.responding(CDOServerIndication.java:134)
> at org.eclipse.net4j.signal.IndicationWithResponse.doExtendedOutput(IndicationWithResponse.java:106)
> at org.eclipse.net4j.signal.Signal.doOutput(Signal.java:334)
> at org.eclipse.net4j.signal.IndicationWithResponse.execute(IndicationWithResponse.java:75)
> at org.eclipse.emf.cdo.server.internal.net4j.protocol.CDOServerReadIndication.execute(CDOServerReadIndication.java:36)
> at org.eclipse.net4j.signal.Signal.runSync(Signal.java:271)
> at org.eclipse.net4j.signal.Signal.run(Signal.java:150)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
>
> at org.eclipse.net4j.signal.RemoteExceptionIndication.indicating(RemoteExceptionIndication.java:56)
> at org.eclipse.net4j.signal.Indication.doExtendedInput(Indication.java:57)
> at org.eclipse.net4j.signal.Signal.doInput(Signal.java:365)
> at org.eclipse.net4j.signal.Indication.execute(Indication.java:51)
> at org.eclipse.net4j.signal.Signal.runSync(Signal.java:271)
> at org.eclipse.net4j.signal.Signal.run(Signal.java:150)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
>
>
> Then even if I close the viewPart and reopen it, it doesn't change anything. I have to restart the client completely
> and reconnect it to the CDO Server
> It happens only with this particular viewpart and I don't know where to start to investigate because my code is not
> involve in the stacktrace.
>
> I'd be glad if you had an indication for me.
>
> Thanks & Best regards
>
> Maxime
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
Powered by
FUDForum. Page generated in 0.03461 seconds
] 
Search
Help
Register
Login
Home
