FTP Adapter Listing is failing in the clustured environement

Question

Hi all,
I observed the first issue after the First time deployment in  Multi-Node environment,after restarting the server I see the Issue 2.
I also observed that Issue #2 is intermittent.Most of the times I see the issue and some times its working fine.
Have any
Issue 1:
Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of
Reference operation 'FileListing' failed due to: Exception occured when binding was invoked. Exception occured during invocation
of JCA binding: "Could not instantiate InteractionSpec oracle.tip.adapter.ftp.outbound.FTPListInteractionSpec due to: XSD Resolution problem.
XSD Resolution problem. Unable to load Translation schemas from
for http://xmlns.oracle.com/RefListFiles_FTP due to:
Please make sure all used XML schemas are imported/included correctly. ". The invoked JCA adapter raised a resource exception.
Please examine the above error message carefully to determine a resolution. ".
The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution.
Issue 2:
<summary>Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'FileListing' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. DocumentManagementComposite:RefListFiles_FTP [ FileListing_ptt::FileListing(Empty,filelist) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12510 JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/FTP/IBP/QA'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/FTP/IBP/QA. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server Please make sure that the JCA connection factory and any dependent connection factories have been configured with a sufficient limit for max connections. Please also make sure that the physical connection to the backend EIS is available and the backend itself is accepting connections. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. </summary>
</part>
<part  name="detail">
<detail>JCA Resource Adapter location error. Unable to locate the JCA Resource Adapter via .jca binding file element <connection-factory/> The JCA Binding Component is unable to startup the Resource Adapter specified in the <connection-factory/> element: location='eis/FTP/IBP/QA'. The reason for this is most likely that either 1) the Resource Adapters RAR file has not been deployed successfully to the WebLogic Application server or 2) the '<jndi-name>' element in weblogic-ra.xml has not been set to eis/FTP/IBP/QA. In the last case you will have to add a new WebLogic JCA connection factory (deploy a RAR). Please correct this and then restart the Application Server </detail>

Answer 1

Service callout can ONLY be used to call Proxy/Business services which are two-way, i.e. which have a response as well. You can not use Service Callout to call a one way service (for ex. a business service to publish a message to JMS queue or MQ queue).
For calling such services you should use Publish action and use QoS option as Exactly-Once within Publish action if you want to catch any errors in Put/Publish.