Timeout for DFS service calls

florianp
florianp Member
edited February 12, 2013 in Documentum #1

Hi there,

I'm working with the DFS Java API and was wondering whether there's a simple way to configure a client-side timeout for service-calls that can be configured on the service context, for example?

I have experienced some rare occasions where a Documentum repository was not responding, that's why I am considering a general timeout for all DFS calls.

For testing a hanging service call, I created a dummy TBO implementation that simply blocks the thread for 10 minutes when updating the document:

@Override public void saveEx(boolean keepLock, String versionLabels) throws DfException {   if (isNew() == false) {     try {       Thread.sleep(1000*60*10);     } catch (InterruptedException e) {       e.printStackTrace();     }   } super.saveEx(keepLock, versionLabels); }

I'm not sure if this behaves exactly like a hanging service call, but at least in my tests it worked as expected - my invocations of the update method of the Object Service took about 10minutes.

Is there any configuration I have not yet found, or maybe a runtime-property to pass to the service context to configure the timeout?

I would prefer using existing features of DFS for this instead of implementing my own mechanism.

Regards

Florian

Tagged: