Hi Sharnel, (1) I cannot create a patch unless you create a ticket I can attach it to. (2) I can easily recognize this kind of corruption and allow MCF to skip the document, and I've committed that change (r1838171). However, partially indexing a document that is partially corrupted like this is not something that is straightforward to do; the connector currently skips corrupted documents entirely.
Karl On Wed, Aug 15, 2018 at 11:54 PM Sharnel Merdeck Pereira < spere...@worldbankgroup.org> wrote: > Hi, > > > > I am using MCF v 2.9.1 with dfc 7.1 > > > > On indexing there are documents which are corrupt . The metadata to these > objects are fine but only the file content is corrupt. > > > > Indexing stops with below : > > > > org.apache.manifoldcf.crawler.common.DCTM.DocumentumException: > [DM_STORAGE_E_BAD_TICKET]error: > "Use of invalid ticket for storage object with name ifcdocs_store_01; > storage may be improperly configured. > > Ticket was 000000008007b986. Data Ticket was 1." > > at > org.apache.manifoldcf.crawler.common.DCTM.DocumentumObjectImpl.getFile(DocumentumObjectImpl.java:375) > ~[?:?] > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) ~[?:1.8.0_181] > > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > ~[?:1.8.0_181] > > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > ~[?:1.8.0_181] > > at java.lang.reflect.Method.invoke(Method.java:498) > ~[?:1.8.0_181] > > at > sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357) > ~[?:1.8.0_181] > > > > - there are many such corrupt docs which is breaking indexing. > - No errors on dfc logs > > > > Kindly help with a patch fix so that we can extract the metadata , ignore > file content if the above exception occurs and continue indexing. > > > > Thanks > > Sharnel > > >