Thanks a lot Karl - that seems to be doing the trick. Cheers
Vince > On 25 Apr 2016, at 14:14, Karl Wright <[email protected]> wrote: > > The ticket is CONNECTORS-1302. There is a patch attached. > > Karl > > > On Mon, Apr 25, 2016 at 9:07 AM, Karl Wright <[email protected] > <mailto:[email protected]>> wrote: > Looking deeper, I see there are lots of checks for SmbException cases similar > to but not identical to this one. Unfortunately, SmbException only includes > text, so when the messages change we have to change as well. I have a patch > ready and will create a ticket that you can try. > > Karl > > > On Mon, Apr 25, 2016 at 8:41 AM, Karl Wright <[email protected] > <mailto:[email protected]>> wrote: > Hi Vince, > > I don't recall ever hitting this before, actually. Could you open a Jira > ticket? It should be straightforward to fix this; it will need to recognize > the SmbException and issue a ServiceInterruption for that document. > > Thanks, > Karl > > > On Mon, Apr 25, 2016 at 7:50 AM, Vince McNamara <[email protected] > <mailto:[email protected]>> wrote: > Hi, > > I’m trying to crawl/index a large Windows file share using the JCIFS 1.3.18 > library (MCF version 2.0.1 in Datafari 2.2). > > The MCF job quits with this error :- > > Error: SmbException thrown: The process cannot access the file because it is > being used by another process. > > Looking at the exception handling in SharedDriveConnector.java, it looks like > this particular error case is not handled, but I would expect it to arise > fairly frequently when crawling over Windows shares - it is not possible to > know in advance which files are going to be held open by users when the crawl > tries to access them. > > Before trying to change the code, can I check if this is a known issue and if > there’s an existing work-around? > > Thanks a lot > > Vince > > > > >
