ORABPEL-05002 When Trying tp Establish SSH Connection Using SFTP Adapters In SOA (Doc ID 2880833.1)

Last updated on NOVEMBER 15, 2023

Applies to:

Symptoms

On : 11.1.1.7.0 version, Technology Adapters

Error in SOA when invoking service using SFTP adapter
the following error occurs.

ERROR
-----------------------

Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: Block cannot handle exception.
failure of the block "BpPrc0" to handle a business exception for the instance "30687329"; exception reported is: faultName: {{http://schemas.oracle.com/bpel/extension}remoteFault}
messageType: {{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage}
parts: {{
summary=Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'PutErrorXML' failed due to: JCA Binding Component connection issue.
JCA Binding Component is unable to create an outbound JCA (CCI) connection.
CllReceiveFTPLoaderXml:CLL_F369_PUTERROR_XMLFTP [ PutErrorXML_ptt::PutErrorXML(opaque) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: Error in establishing a session with SSH Server..
Error in establishing a session with SSH Server..
Unable to establish a session with the server.
Please ensure hostname and port specified to login to the server are correct.

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.

,detail=Failed to read remote identification
,code=null}

This error contained the exceptions thrown by the underlying routing system.
Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).

This error contained an exception thrown by the message handler.
Check the exception trace in the log (with logging level set to debug mode).

ORABPEL-05002

Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: Block cannot handle exception.
failure of the block "BpPrc0" to handle a business exception for the instance "30687329"; exception reported is: faultName: {{http://schemas.oracle.com/bpel/extension}remoteFault}
messageType: {{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage}
parts: {{
summary=Exception occured when binding was invoked.
Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'PutErrorXML' failed due to: JCA Binding Component connection issue.
JCA Binding Component is unable to create an outbound JCA (CCI) connection.
CllReceiveFTPLoaderXml:CLL_F369_PUTERROR_XMLFTP [ PutErrorXML_ptt::PutErrorXML(opaque) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: Error in establishing a session with SSH Server..
Error in establishing a session with SSH Server..
Unable to establish a session with the server.
Please ensure hostname and port specified to login to the server are correct.

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.

,detail=Failed to read remote identification
,code=null}

This error contained the exceptions thrown by the underlying routing system.
Contact Oracle Support Services. Provide the error message, the composite source and the exception trace in the log files (with logging level set to debug mode).

This error contained an exception thrown by the message handler.
Check the exception trace in the log (with logging level set to debug mode).

at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:238)
at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatchTask.java:89)
at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:65)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1152)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:622)
at com.collaxa.cube.engine.dispatch.Dispatcher$ContextCapturingThreadFactory$2.run(Dispatcher.java:933)
at java.lang.Thread.run(Thread.java:745)
>

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.