all,

in our very long-running ox installation we seem to have run into a database consistency problem: various methods that try to build user maps fail because they are looking for a deleted user, here is a sample log entry:

Code:
SEVERE: 1:378:plitsch.platsch@defaultcontext:EAS:androidc1761139351 OX server returned error
400015: com.openexchange.usm.api.exceptions.OXCommunicationException: OX server returned error, json-error={"error_params":[3,1],"category":8,"error":"Contact %1$d not found in
 context %2$d.","code":"CON-0125","error_id":"848401358-12032"}
        at com.openexchange.usm.contenttypes.util.AbstractTransferHandler.checkResult(AbstractTransferHandler.java:542)
        at com.openexchange.usm.contenttypes.contacts.impl.ContactContentTypeTransferHandler.getListOfResults(ContactContentTypeTransferHandler.java:366)
        at com.openexchange.usm.contenttypes.contacts.impl.ContactContentTypeTransferHandler.getAllUsers(ContactContentTypeTransferHandler.java:359)
        at com.openexchange.usm.contenttypes.contacts.impl.ContactContentTypeImpl.getAllUsers(ContactContentTypeImpl.java:292)
        at com.openexchange.usm.contenttypes.contacts.impl.ContactsContentTypeService.getAllUsers(ContactsContentTypeService.java:108)
        at com.openexchange.usm.eas.delegate.SyncDelegate.createUserIdNameEmailMap(SyncDelegate.java:566)
        at com.openexchange.usm.eas.delegate.SyncDelegate.getUserIdMap(SyncDelegate.java:2289)
        at com.openexchange.usm.eas.delegate.sync.AttendeesXmlType.writeXml(AttendeesXmlType.java:71)
        at com.openexchange.usm.eas.delegate.sync.AttendeesXmlType.writeToXML(AttendeesXmlType.java:61)
        at com.openexchange.usm.eas.delegate.SyncDelegate.writeApplData(SyncDelegate.java:968)
        at com.openexchange.usm.eas.delegate.SyncDelegate.writeAddElement(SyncDelegate.java:2155)
        at com.openexchange.usm.eas.delegate.SyncDelegate.writeCommandsInResponse(SyncDelegate.java:1577)
        at com.openexchange.usm.eas.delegate.SyncDelegate.writeCollectionInResponse(SyncDelegate.java:1471)
        at com.openexchange.usm.eas.delegate.SyncDelegate.handleRequest(SyncDelegate.java:357)
        at com.openexchange.usm.eas.delegate.BaseXMLDelegate.handleRequest(BaseXMLDelegate.java:120)
        at com.openexchange.usm.eas.servlet.EASServlet.handleRequest(EASServlet.java:608)
        at com.openexchange.usm.eas.servlet.EASServlet.doPost(EASServlet.java:485)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at com.openexchange.ajp13.coyote.AjpProcessor.process(AjpProcessor.java:835)
        at com.openexchange.ajp13.coyote.sockethandler.CoyoteTask.call(CoyoteTask.java:184)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
        at java.util.concurrent.FutureTask.run(FutureTask.java:166)
        at com.openexchange.threadpool.internal.CustomThreadPoolExecutor$Worker.runTask(CustomThreadPoolExecutor.java:781)
        at com.openexchange.threadpool.internal.CustomThreadPoolExecutor$Worker.run(CustomThreadPoolExecutor.java:807)
checking the database reveals user id 3 no longer exists except in del_user. is this a bug or is our database broken (in that case: can it be fixed by removing references to that deleted user) ?

any ideas, anyone?

thanks and best regards,

guenter