java - Documentum DFS: Timeout for service calls -
i'm working dfs java api , wondering whether knows simple way configure client-side timeout service-calls can configured on service context, example?
i have experienced rare occasions documentum repository not responding, that's why considering general timeout dfs calls.
for testing hanging service call, created dummy tbo implementation blocks thread 10 minutes when updating document:
@override public void saveex(boolean keeplock, string versionlabels) throws dfexception { if (isnew() == false) { seek { thread.sleep(1000*60*10); } grab (interruptedexception e) { e.printstacktrace(); } } super.saveex(keeplock, versionlabels); }
i'm not sure if behaves hanging service call, @ to the lowest degree in tests worked expected - invocations of update method of object service took 10minutes.
is there configuration have not yet found, or maybe runtime-property pass service context configure timeout?
i prefer using existing features of dfs instead of implementing own mechanism.
have tried editing value in dfs-runtime.properties
? don't think timeout can context-specific, should able alter client whole.
reposted https://community.emc.com/message/3249#3249
"please see server runtime startup settings section of deployment guide.
the next list describes precedence dfs-runtime.properties
files take depending on location:
local-dfs‑runtime.properties
file in local classpath runtime properties file specified ‑ddfs.runtime.properties.file
dfs‑runtime.properties
packaged emc‑dfs‑rt.jar
for example, settings in local-dfs‑runtime.propertie
s file on local classpath take precedence of identical settings in dfs‑runtime.properties
file located in emc‑dfs‑rt.jar
or 1 specified ‑d
parameter. dfs application must restarted after changes configuration. best practice, utilize provided configuration file deployed in emc‑dfs‑rt.jar
file base of operations settings , utilize external file override settings wish change."
java documentum documentum-dfs
No comments:
Post a Comment