Product: TIBCO Spotfire®
Defect resulting in MS Excel and Access files loaded in-process by default in versions 7.12 and 7.13
By default, Access, Excel, and SAS files are loaded out-of-process, which means that a separate sub-process is launched to handle loading of the file. This is for fault tolerance reasons: if something goes wrong in the file loading, there is no impact on the main process. With LoadOutOfProcessExceptedFilePaths setting, you can specify excepted files or directories that, when accessed in the web clients, should be loaded in-process instead. To do so, you provide the full path to directories or files that should be loaded in-process, instead of out-of-process, when accessed in the web clients. Specify each file or directory in a separate <string> tag. Read more about this in the documentation.
In Spotfire versions 7.12 and 7.13, however, there is a defect resulting in all files of the mentioned type being loaded in-process with the default configuration.
In Spotfire.Dxp.Worker.Host.exe.config file by default there is an empty string tag in LoadOutOfProcessExceptedFilePaths setting. The expected behavior is that services should ignore empty string and files of above mentioned type should be loaded out-of-process. But, in versions 7.12 and 7.13, the presence of the empty string results in files being imported in-process from all directories.
Removing the empty string tag from the LoadOutOfProcessExceptedFilePaths section in the Spotfire.Dxp.Worker.Host.exe.config file results in files loaded out-of-process by default, as expected.
Here is how the section looks by default (resulting in all files being imported in-process from all directories in version 7.12 and 7.13 unless the empty <string/> tag is removed):
<setting name="LoadOutOfProcessExceptedFilePaths" serializeAs="Xml"> <value> <ArrayOfString> <string/> </ArrayOfString> </value> </setting>Doc: Spotfire.Dxp.Worker.Host.exe.config file
Article is closed for comments.