LODESTAR Adapter FPORTAL Services are Locking XML Files in LTMH\Runtime\temp directory (Doc ID 1059935.1)

Last updated on AUGUST 22, 2016

Applies to:

LODESTAR EIP - Version: 04.53.00.01.00 - Release: 4.5
Information in this document applies to any platform.

Symptoms

When running the LODESTAR Adapter version 4.53, XML files are being created in \LTMH\Runtime\temp\ directory (under the LODESTAR installation directory).

The XML files cannot be deleted as they are locked by the Adapter service and can become large and cause problems on the file system.

Scenarios

Scenario 1 : Payload above 32K
  1. Create an Adapter FilePortal service. Configure the STORAGE_LEVEL service property to 2 for full storage. No business rule is necessary.
  2. Set the debug level to three or higher.
  3. Create a payload file larger than 32 Kb.
  4. Allow the service to process the file.
  5. Attempt to delete the temporary file in the Lodestar\LTMH\Runtime\temp folder.
Scenario 2 : Buffered Payload
  1. Create an Adapter FilePortal service. Configure the RDL_MEMORY_BUFFER_SIZE service property to 0. This will force any payload out of memory and into a temporary file.
  2. Set the debug level to three or higher.
  3. Create a simple business rule, such as an MDM Ready rule or an RDL.
  4. Create a payload for the service to process. The size does not matter.
  5. Allow the service to process the file.
  6. Attempt to delete the temporary file in the Lodestar\LTMH\Runtime\temp\{host name}/{port}/{service name} folder.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms