The BatchFTP getIfExists Method Incorrectly Throws A BatchException In Java CAPS 6.3. (Doc ID 1532026.1)

Last updated on NOVEMBER 02, 2016

Applies to:

Oracle Java CAPS Enterprise Service Bus - Version R6.3 and later
Information in this document applies to any platform.

Symptoms

There is a difference in the behavior of the BatchFTP_1.getClient().getIfExists() method between Java CAPS 6.2 and Java CAPS 6.3 which is:

[#|2012-11-12T12:14:28.375+0000|INFO|sun-appserver2.1.1|STC.eGate.CMap.Collabs.prjTestFTP.cmTestFTP_jcdTestFTP1.prjTestFTP.jcdTestFTP|_ThreadID=22;_ThreadName=p: thread-pool-1; w: 5;Context=project=prjTestFTP,deployment=dp1,collab=cmTestFTP_jcdTestFTP1,external=FileIn;|++++ - exception message is: Batch FTP eWay error when doing data transfer operation in [get()], message=[BATCH-MSG-M0172: FtpFileClientImpl.get(): No qualified file is available for retrieving.].Nested exception follows: ---
java.io.FileNotFoundException: BATCH-MSG-M0172: FtpFileClientImpl.get(): No qualified file is available for retrieving.--- End of nested exception.
|#]

 The same behavior is required in Java CAPS 6.3 that was in Java CAPS 6.2. The behavior in Java CAPS 6.2 is consistent with the behavior described in the JavaDoc which states:

'Same as get but if there is no file found matching the name pattern given in "Target Directory Name" and "Target File Name", just return siliently.'

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