Hi,
In the logfiles of our application server we see the following entries a couple of times per week (I've seen these errors both with EPS and TCP).
2013-04-10 15:27:33,939 ERROR http-0.0.0.0-38080-3 [com.opentext.ecm.bpm.locking.OptimisticLockingImpl] The data object '_default' (of 'WIz1365593462976a7c64bfb-0b64-4db3-9675-9b94450c7ea1') was not read.
2013-04-10 15:27:33,939 INFO http-0.0.0.0-38080-3 [com.opentext.ecm.bpm.service.ProcessServiceImpl] Error in method 'setObject'
2013-04-10 15:27:33,939 ERROR http-0.0.0.0-38080-3 [com.opentext.ecm.bpm.service.ProcessServiceImpl] The value of the object '_default' can not be changed (of 'WIz1365593462976a7c64bfb-0b64-4db3-9675-9b94450c7ea1'), it has to be read first.
2013-04-10 15:27:33,942 ERROR http-0.0.0.0-38080-3 [com.opentext.ecm.tcp.ws.impl.process.ProcessServiceBean] setObject(TcpObject,String,String,String,TcpObject,String,byte[])
com.opentext.ecm.tcp.ws.TcpException: Bpm.Common.ObjectNotRead: The object was not read.
Params: {OBJECT_NAME=_default, Id=WIz1365593462976a7c64bfb-0b64-4db3-9675-9b94450c7ea1, SERVER_STACK_TRACE=com.opentext.ecm.bpm.locking.exception.ObjectNotReadException: The value of the object '_default' can not be changed (of 'WIz1365593462976a7c64bfb-0b64-4db3-9675-9b94450c7ea1'), it has to be read first.
This entries correspond with following error in the TCP WebClient log:
2013-04-10 15:27:32,697 [5] ERROR OpenText.Ecm.Tcp.Service.ProcessServiceProxy [(null)] - The object was not read.
System.ServiceModel.FaultException`1[OpenText.Ecm.Tcp.Service.ProcessService.TcpException]: The object was not read. (Fault Detail is equal to OpenText.Ecm.Tcp.Service.ProcessService.TcpException).
2013-04-10 15:27:32,723 [5] ERROR OpenText.Ecm.Tcp.Data.ModelAction [(null)] - The object was not read.
OpenText.Ecm.Tcp.Data.ServiceException: The object was not read.
… OpenText.Ecm.Tcp.Data.ServiceException: The object was not read. at OpenText.Ecm.Tcp.Service.ProcessServiceProxy.SetObject(AccessContext accCtxt, String workItemId, String objectName, DataObject dataObject) at OpenText.Ecm.Tcp.Model.ProcessModel.SetObject(AccessContext accCtxt, String workItemId, String objectName, DataObject dataObject) at OpenText.Ecm.Tcp.Model.WorkItemAction.SaveWorkItem()
2013-04-10 15:27:32,780 [5] DEBUG OpenText.Ecm.Tcp.Model.WorkItemAction [(null)] - Method 'SaveWorkItem' returned at 'False'.
2013-04-10 15:27:32,780 [5] DEBUG OpenText.Ecm.Tcp.Model.WorkItemAction [(null)] - Method 'Execute' returned at .
2013-04-10 15:27:32,780 [5] DEBUG OpenText.Ecm.Tcp.Model.Dispatcher [(null)] - Method 'ExecuteAction' returned at .
2013-04-10 15:27:32,780 [5] DEBUG OpenText.Ecm.Tcp.Model.Dispatcher [(null)] - Method 'Dispatch' returned at 'OpenText.Ecm.Tcp.StateEvent, Id:, Originator: MainController'.
We are still trying to find out what causes this error. We've once reproduced this error by accident in our development environment, which was after a form has been left open for about 2 hours and after that a field has been set using
PwInst.SetField("_default.DossierAfsluiten", false);
PwInst.SendOn();
This resulted in an error "The workitem is outdated and could not be saved" for the user in the webclient (which can be linked to this error via the exceptiontext.en-us file.
However we tried to reproduce this, but until now haven't been able to do this.
Anyone an idea what could be causing this?
Regards,
Peter