Eclipse Community Forums: EMF » [CDO] Correctly configuring timeouts

Help

Home

Home » Modeling » EMF » [CDO] Correctly configuring timeouts

Show: Today's Messages :: Show Polls :: Message Navigator

[CDO] Correctly configuring timeouts [message #1817951]

Tue, 03 December 2019 14:22

Robert Schulk

Messages: 144
Registered: July 2015

Senior Member

Sometimes, our commits may get quite large and take a couple of seconds to complete.

This leads to occasional exceptions in the net4j communication (see attached example stack).

So what helps in our case is to configure this:

CDONet4jSession#options()#getNet4jProtocol().setTimeout(someHighValue)

But looking around a little, I also found other timeout configurations:

1.) CDONet4jSession#options()#setCommitTimeout(long): this seems to me like it is only a configuration in case a progressmonitor is used for the commit?

2.) CDOTransaction#options()#setCommitInfoTimeout(long) what is this good for? I guess it is there to make sure that the changes are correctly processed by the server? In rare cases, we get a TimeoutRuntimeException on a commit (even though the change seems to always be processed correctly).

Does anyone know more details about the timeouts and how they should be configured?
Thanks!

Attachment: timeout_stacktrace.txt
(Size: 3.31KB, Downloaded 53 times)

Report message to a moderator

Re: [CDO] Correctly configuring timeouts [message #1817972 is a reply to message #1817951]

Tue, 03 December 2019 17:27

Eike Stepper

Messages: 6682
Registered: July 2009

Senior Member

If I'm not totally misled (the remote progress monitoring is a bit complex) you can use CDONet4jSession#options()#setCommitTimeout(long) even if you don't pass your own progress monitor into the commit() method. Internally there are always progress signals exchanged over the wire and they reset the timeout. In the worst case you could pass a NullProgressMonitor to the commit() method, but I don't think that's required.

CDOTransaction#options()#setCommitInfoTimeout(long) is used to specify how long the transaction must wait after a commit to receive the server's OK notification. It can help when you experience "Did not receive an update" exceptions. A ore liekly cause for these exceptions is a bug in the thread pool which is fixed in recent I-builds and the upcoming 2019-12 release.

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper

Report message to a moderator