How does OSB File Proxy Ensure it does not Process Incomplete Files
(Doc ID 965524.1)
Last updated on AUGUST 10, 2018
Applies to:Oracle Service Bus - Version 10.3 and later
Information in this document applies to any platform.
When a file is slowly written to the poller location of the OSB file proxy, and the polling interval is triggered, how does OSB know that it cannot start processing the incoming file?
- NFS file system used as OSB file proxy polling location
- No extra functional mechanism is in place. The OSB "start of processing" the files depends only on the OS file locking and filesize growth. E.g. file mask is set to *.*
- Tested on WLS 10gR3 with OSB 10gR3 running on Oracle Enterprise Linux 5
- Using a NetApp filer storage infrastructure using both CIFS (for Windows) and NFS (for Linux)
- If the sending party or the network between sender and receiver is slow or temporary stuck, it is insufficient to rely on OS file locking and filesize growth.
- The OSB proxy file poller process (in combination with standard NFS settings) can start processing the file, while it is not ready yet for processing, resulting in a failed proces.
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