Errors in D2 App Server Log

edited October 16, 2017 in Documentum #1

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] -  : 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( [dfc.jar:na]

  at com.documentum.fc.client.impl.connection.docbase.MessageEntry.getException( [dfc.jar:na]

  at com.documentum.fc.client.impl.connection.docbase.DocbaseMessageManager.getException( [dfc.jar:na]

  at com.documentum.fc.client.impl.connection.docbase.netwise.NetwiseDocbaseRpcClient.checkForMessages( [dfc.jar:na]

  at com.documentum.fc.client.impl.connection.docbase.netwise.NetwiseDocbaseRpcClient.applyForInt( [dfc.jar:na]

  at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection$6.evaluate( [dfc.jar:na]

  at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.evaluateRpc( [dfc.jar:na]

  at com.documentum.fc.client.impl.connection.docbase.DocbaseConnection.applyForInt( [dfc.jar:na]

  at com.documentum.fc.client.impl.docbase.DocbaseApi.parameterizedSave( [dfc.jar:na]

  at com.documentum.fc.client.DfSysObject$1.evaluate( [dfc.jar:na]

  at com.documentum.fc.client.DfSysObject.doSaveImpl( [dfc.jar:na]

  at com.documentum.fc.client.DfSysObject.doSave( [dfc.jar:na]

  at com.documentum.fc.client.DfPersistentObject.saveEx( [dfc.jar:na]

  at [dfc.jar:na]

  at [D2-Widget-API-4.6.0.jar:na]

  at [D2-Widget-API-4.6.0.jar:na]

  at [na:na]

  at [D2FS4DCTM-WEB-4.6.0.jar:na]

  at$ [D2FS4DCTM-WEB-4.6.0.jar:na]

  at org.aspectj.runtime.reflect.JoinPointImpl.proceed( [aspectjrt-1.6.11.jar:na]

  at com.emc.d2fs.dctm.aspects.InjectSessionAspect.process( [D2FS4DCTM-WEB-4.6.0.jar:na]

  at [D2FS4DCTM-WEB-4.6.0.jar:na]

  at [X3-Doclist-4.6.0.jar:na]

  at [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]



  • Alain_Molimard2
    edited March 23, 2017 #2

    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


  • renewtx
    edited March 30, 2017 #3

    it's not specific to a user -- we see it for many users.

  • anupatnaik
    edited April 4, 2017 #4

    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.



  • renewtx
    edited April 4, 2017 #5

    There is no code ... this is all OOTB D2 functionality where this is happening.

  • MatthijsDB
    edited April 5, 2017 #6

    Same thing here. Also originating from D2X3ConfigService.setLastUsedObject( which is called from RpcDoclistServiceImpl.setLastUsedFolder(

    In our case it came from getFolderDocListItemFromId(

    This happened after a change state of a lifecycle, when D2 locates the object that was just promoted.

  • PerThylander
    edited October 16, 2017 #7

    This keeps cluttering our logs too. Did you found a solution?


  • Mohamed.Sayed
    edited January 9, 2018 #8

    Any one find the solution of this issue????

  • hi all, i am also facing the same issue Anyone find the solution to this issue????

  • 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,

    1. Note all enabled D2 jobs and ,make it all disable
    2. Stop all services CS and JDM and D2, clear logs,
    3. Start all services
    4. Now observe logs when this error happening by starting one by one job.

    Dump users x3_preferences object, sample id from your logs 0802d1548001e10d

Sign In or Register to comment.