Skip to Content
author's profile photo
Former Member

Lock on File processing

Did any one know how to choose lock mode on file processing?



Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • author's profile photo
    Former Member
    Oct 01, 2005 at 08:59 PM

    Hi Kumar

    Yes that should be possible, by configuring the sender File/FTP adapter. You can see the procedure at,



    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Please take a look at point 3 in the OSS Note 821267

      <b>3. File Locking</b>

      Q: Does the File Sender Adapter honor if another process has locked a file for exclusive use?

      A: Unfortunately, the J2EE 1.3 technology the File Adapter is built upon does not support file locking. This limitation affects the File Adapter's operation. Depending on whether the JRE implementation for the operating system under which the adapter runs uses mandatory file locking or advisory file locking, opening a file that is currently being written to by another process will fail or not.

      If opening the file fails, no problem exists and the adapter will try to open the file each poll interval until it succeeds.

      However, if opening the file is not prevented by the operating system, the adapter starts to process the file although it is still being modified. Since SP11 of the component XI 3.0 ADAPTER FRAMEWORK CORE there is a parameter named "Msecs to Wait Before Modification Check" in the advanced settings of the File Sender channel configuration to work around this issue. This setting causes the File Adapter to wait a certain time after reading, but before sending a file to the Adapter Engine. If the file has been modified (which is basically determined by comparing the size of the read data with the current file size of the input file) after the configured interval has elapsed, the adapter aborts the processing of the file and tries to process the file again after the retry interval has elapsed.