Outside-in (OIT) Exporter Hangs on Dispose Method even After Oilink.exe Process is Terminated
(Doc ID 2686544.1)
Last updated on AUGUST 14, 2023
Applies to:Oracle Outside In Technology - Version 8.5.4 and later
Information in this document applies to any platform.
On : 8.5.4 version, Outside In Search Export SDK
When exporting attachments from .msg files, new sub document exporters are created for attachment to be exported. After the export (or when an exception occurs) the ExporterImpl instance created is disposed.
Exporting a set of 100 .msg files take 5 minutes (when profiling). Using (ReSharper) profiling it was detected that almost all of these 5 minutes is spend within the ExporterImpl. It appears that within this Dispose routine, an attempt is made to read data from the external oilink.exe process when this process has already terminated. Attempt to read data while the oilink.exe is already terminated, disposing takes an extremely long time.
Expectation is within the Dispose method, it is correctly detected oilink.exe is to be terminated.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document