BUG:Import timeout

[omero-qa]

• ​https://www.openmicroscopy.org/qa2/qa/feedback/9288/
• ​https://www.openmicroscopy.org/qa2/qa/feedback/9289/

java.io.FileNotFoundException: /Volumes/D/Utilisateurs/Olivier Ganier/10062014_2014_06_10__17_06_08(241).czi (Operation timed out)
	at java.io.RandomAccessFile.open(Native Method)
	at java.io.RandomAccessFile.<init>(RandomAccessFile.java:216)
	at loci.common.NIOFileHandle.<init>(NIOFileHandle.java:127)
	at loci.common.NIOFileHandle.<init>(NIOFileHandle.java:143)
	at loci.common.NIOFileHandle.<init>(NIOFileHandle.java:152)
	at loci.common.Location.getHandle(Location.java:323)
	at loci.common.Location.getHandle(Location.java:293)
	at loci.common.Location.getHandle(Location.java:283)
	at loci.common.Location.getHandle(Location.java:273)
	at loci.common.Location.checkValidId(Location.java:348)
	at loci.formats.ImageReader.getReader(ImageReader.java:177)
	at loci.formats.ImageReader.setId(ImageReader.java:750)
	at loci.formats.ReaderWrapper.setId(ReaderWrapper.java:569)
	at loci.formats.ChannelFiller.setId(ChannelFiller.java:259)
	at loci.formats.ReaderWrapper.setId(ReaderWrapper.java:569)
	at loci.formats.ChannelSeparator.setId(ChannelSeparator.java:270)
	at loci.formats.ReaderWrapper.setId(ReaderWrapper.java:569)
	at loci.formats.Memoizer.setId(Memoizer.java:467)
	at loci.formats.ReaderWrapper.setId(ReaderWrapper.java:569)
	at ome.formats.importer.ImportCandidates.singleFile(ImportCandidates.java:414)
	at ome.formats.importer.ImportCandidates.handleFile(ImportCandidates.java:596)
	at ome.formats.importer.ImportCandidates.execute(ImportCandidates.java:371)
	at ome.formats.importer.ImportCandidates.<init>(ImportCandidates.java:229)
	at ome.formats.importer.ImportCandidates.<init>(ImportCandidates.java:180)
	at org.openmicroscopy.shoola.env.data.OMEROGateway.getImportCandidates(OMEROGateway.java:6481)
	at org.openmicroscopy.shoola.env.data.OmeroImageServiceImpl.importFile(OmeroImageServiceImpl.java:1195)
	at org.openmicroscopy.shoola.env.data.views.calls.ImagesImporter.importFile(ImagesImporter.java:77)
	at org.openmicroscopy.shoola.env.data.views.calls.ImagesImporter.access$000(ImagesImporter.java:53)
	at org.openmicroscopy.shoola.env.data.views.calls.ImagesImporter$1.doCall(ImagesImporter.java:102)
	at org.openmicroscopy.shoola.env.data.views.BatchCall.doStep(BatchCall.java:144)
	at org.openmicroscopy.shoola.util.concur.tasks.CompositeTask.doStep(CompositeTask.java:226)
	at org.openmicroscopy.shoola.env.data.views.CompositeBatchCall.doStep(CompositeBatchCall.java:126)
	at org.openmicroscopy.shoola.util.concur.tasks.ExecCommand.exec(ExecCommand.java:165)
	at org.openmicroscopy.shoola.util.concur.tasks.ExecCommand.run(ExecCommand.java:276)
	at org.openmicroscopy.shoola.util.concur.tasks.AsyncProcessor$Runner.run(AsyncProcessor.java:91)
	at java.lang.Thread.run(Thread.java:695)

[jburel]

Comment from Julio

The source HD was turned down.

Or maybe not to forget. Is there a way that the user gets a more specific feedback?

[jamoore]

At the library level, I'm not sure what else we can provide. We can detect the message "Operation timed out" and possible raise a different event if that will help provide more feedback in the UI.

[mtbcarroll]

Could recognize and handle it entirely within the Insight code, depending on how async response from ImagesImporter is handled?

[mtbcarroll]

#12418 feels like a related kind of issue.

[bpindelski]

It seems to me that the call to setId in ImportCandidates.java:414 swallows the IOException thrown. I can't catch it in OMEROGateway.java, as it's not thrown from the ctor of ImportCandidates. On a second look, that isn't true. There is a safeUpdate() method that notifies any observers about a FILE_EXCEPTION. I'm not sure if it's useful in OMEROGateway.

[jamoore]

All the exceptions from the import library classes should be receivable via IObserver. Perhaps the Insight implementation is receiving the event?

[bpindelski]

Quick debugging shows that deleting a file during import (when the JVM is waiting at creating the ImportCandidates object) causes the StatusLabel to display a red cross and a failure. All looks OK so far. I don't know if I'll be able to reproduce the situation from this ticket.

[jamoore]

As Julio said, this was an understood H/W failure (i.e. hit the power button). Not sure it's worth leaving this open to try to improve. If anyone disagrees or sees something similar happen, re-create.