Errors in D2 App Server Log
We are seeing the following error in our D2 App Server log -- has anyone seen this and know the cause/fix? It does not seem to cause any issues but keeps cluttering the logs .... We've cleared caches, restarted all servers, etc. but keeps happening...
2017-03-18 12:14:29 [INFO ] [ajp-apr-8009-exec-2] - c.e.x.s.services.RpcBrowserServiceImpl : Context UTAustinQual-1489857249664-trw2363-1389793010
2017-03-18 12:14:29 [WARN ] [ajp-apr-8009-exec-9] - c.e.d.d.w.s.config.D2X3ConfigService : Error while trying to save user last object
com.documentum.fc.common.DfException: [DM_OBJ_MGR_E_VERSION_MISMATCH]error: "save of object 0802d1548001e10d of type x3_preferences failed because of version mismatch: old version was 9"
at com.documentum.fc.client.impl.docbase.DocbaseExceptionMapper.newException(DocbaseExceptionMapper.java:57) [dfc.jar:na]
at com.documentum.fc.client.impl.connection.docbase.MessageEntry.getException(MessageEntry.java:39) [dfc.jar:na]
at com.documentum.fc.client.impl.connection.docbase.DocbaseMessageManager.getException(DocbaseMessageManager.java:137) [dfc.jar:na]
at com.documentum.fc.client.impl.connection.docbase.netwise.NetwiseDocbaseRpcClient.checkForMessages(NetwiseDocbaseRpcClient.java:330) [dfc.jar:na]
at com.documentum.fc.client.impl.connection.docbase.netwise.NetwiseDocbaseRpcClient.applyForInt(NetwiseDocbaseRpcClient.java:601) [dfc.jar:na]
at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection$6.evaluate(DocbaseConnection.java:1341) [dfc.jar:na]
at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.evaluateRpc(DocbaseConnection.java:1139) [dfc.jar:na]
at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.applyForInt(DocbaseConnection.java:1334) [dfc.jar:na]
at com.documentum.fc.client.impl.docbase.DocbaseApi.parameterizedSave(DocbaseApi.java:767) [dfc.jar:na]
at com.documentum.fc.client.DfSysObject$1.evaluate(DfSysObject.java:383) [dfc.jar:na]
at com.documentum.fc.client.DfSysObject.doSaveImpl(DfSysObject.java:413) [dfc.jar:na]
at com.documentum.fc.client.DfSysObject.doSave(DfSysObject.java:216) [dfc.jar:na]
at com.documentum.fc.client.DfPersistentObject.saveEx(DfPersistentObject.java:924) [dfc.jar:na]
at com.documentum.fc.client.DfPersistentObject.save(DfPersistentObject.java:919) [dfc.jar:na]
at com.emc.x3.api.preferences.X3Preferences.save(X3Preferences.java:883) [D2-Widget-API-4.6.0.jar:na]
at com.emc.x3.api.preferences.X3Preferences.save(X3Preferences.java:891) [D2-Widget-API-4.6.0.jar:na]
at com.emc.x3.api.preferences.X3Preferences___PROXY.save(X3Preferences___PROXY.java) [na:na]
at com.emc.d2fs.dctm.web.services.config.D2X3ConfigService.setLastUsedObject_aroundBody64(D2X3ConfigService.java:1930) [D2FS4DCTM-WEB-4.6.0.jar:na]
at com.emc.d2fs.dctm.web.services.config.D2X3ConfigService$AjcClosure65.run(D2X3ConfigService.java:1) [D2FS4DCTM-WEB-4.6.0.jar:na]
at org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:221) [aspectjrt-1.6.11.jar:na]
at com.emc.d2fs.dctm.aspects.InjectSessionAspect.process(InjectSessionAspect.java:217) [D2FS4DCTM-WEB-4.6.0.jar:na]
at com.emc.d2fs.dctm.web.services.config.D2X3ConfigService.setLastUsedObject(D2X3ConfigService.java:1915) [D2FS4DCTM-WEB-4.6.0.jar:na]
at com.emc.x3.server.services.RpcDoclistServiceImpl.setLastUsedFolder(RpcDoclistServiceImpl.java:321) [X3-Doclist-4.6.0.jar:na]
at com.emc.x3.server.services.RpcDoclistServiceImpl.getCabinetDocListItem(RpcDoclistServiceImpl.java:156) [X3-Doclist-4.6.0.jar:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [na:1.7.0_72]
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) [na:1.7.0_72]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) [na:1.7.0_72]
at java.lang.reflect.Method.invoke(Unknown Source) [na:1.7.0_72]
Comments
-
For which user are you getting the error?
Usualty version mismatch is caused where to process are trying to save the same object:
process 1 fetch the object
process 2 fetch the object
process 1 save the object (causing increment of i_vstamp)
process 2 save the object (this causes a version mismatch because the object was saved by another process after it got fetched)
My two cents
Alain
0 -
Hello Rene,
The version mismatch error usually occurs when Documentum tries to save the non-current version of an object. That is, the i_vstamp of the object has already been incremented by some other process/method call etc. It is not user-specific.
In your code, please ensure that you save your object before calling another method, esp. when the execution is asynchronous.
Thanks,
Anu
0 -
Same thing here. Also originating from D2X3ConfigService.setLastUsedObject(D2X3ConfigService.java:1915) which is called from RpcDoclistServiceImpl.setLastUsedFolder(RpcDoclistServiceImpl.java:321)
In our case it came from getFolderDocListItemFromId(RpcDoclistServiceImpl.java:115)
This happened after a change state of a lifecycle, when D2 locates the object that was just promoted.
0 -
This keeps cluttering our logs too. Did you found a solution?
/Per
0 -
Any one find the solution of this issue????
0 -
hi all, i am also facing the same issue Anyone find the solution to this issue????
0 -
Hi,
Yes, this error may happen when multiple process saving same object, As you said it's OOTB D2, below steps may help to narrow down to find root cause,
- Note all enabled D2 jobs and ,make it all disable
- Stop all services CS and JDM and D2, clear logs,
- Start all services
- Now observe logs when this error happening by starting one by one job.
Dump users x3_preferences object, sample id from your logs 0802d1548001e10d
0 -
Thank you
0
Categories
- All Categories
- 108 Developer Announcements
- 53 Articles
- 106 General Questions
- 145 IM Services
- 43 OpenText Hackathon
- 32 Developer Tools
- 20.6K Analytics
- 4.1K AppWorks
- 8.9K Extended ECM
- 899 Cloud Fax and Notifications
- 77 Digital Asset Management
- 9.3K Documentum
- 29 eDOCS
- 120 Exstream
- 39.8K TeamSite
- 1.7K Web Experience Management