Hi Everyone!!!, We are facing below error during message publishing in AQ and AQJMS adapter using ATP and Dbaas Adapters.
----------------------------------------------------------------------------------------------------------
ERROR
"Exception while processing Invoke request for endpoint <publish_REQUEST>. Error Message : JCA Binding Component connection issue.
JCA Binding Component is unable to create an outbound JCA (CCI) connection.
file:/tmp/d2d86457-55c1-432d-a3b8-182ab9f37afe/publish_REQUEST.wsdl [ publish_REQUESTPortType::Produce_Message(parameters) ] - : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12136
ERRJMS_ERR_CR_TOPIC_PROD.
ERRJMS_ERR_CR_TOPIC_PROD.
Unable to create Topic producer due to JMSException.
Please examine the log file to determine the problem.
ORA-17002: I/O error: Connection reset, connect lapse 30002 ms., Authentication lapse 0 ms.
https://docs.oracle.com/error-help/db/ora-17002/
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.
; nested exception is:
BINDING.JCA-12511
JCA Binding Component connection issue.
JCA Binding Component is unable to create an outbound JCA (CCI) connection.
file:/tmp/d2d86457-55c1-432d-a3b8-182ab9f37afe/publish_REQUEST.wsdl [ publish_REQUESTPortType::Produce_Message(parameters) ] - : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: BINDING.JCA-12136
ERRJMS_ERR_CR_TOPIC_PROD.
ERRJMS_ERR_CR_TOPIC_PROD.
Unable to create Topic producer due to JMSException.
Please examine the log file to determine the problem.
ORA-17002: I/O error: Connection reset, connect lapse 30002 ms., Authentication lapse 0 ms.
https://docs.oracle.com/error-help/db/ora-17002/
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.
---------------------------------------------------------------------------------------------------------------------------------------
Questions:-
1)What is the exact root cause of ORA-17002 "Connection reset"?
2)Could this be related to connection pool exhaustion or DB connections?
We are trying to understand whether this is:
-
A DBlevel connectivity issue
-
A connection pool configuration issue
-
Or an network timeout issue
Observation we observed:
-
Other integrations using the same credentials are working.
-
This issue occurs while publishing the message itself.