####### 1 #######
Adapter: Eloqua
ErrorCode: ICS-20575
ErrorMessage:
Integration "<INTEGRATION>" cannot be activated. Incident has been created with ID 27. [Cause: ICS-20575]:
- Integration "<INTEGRATION>" " cannot be activated because of an internal error. Incident has been created with ID: 27.
- com.bea.wli.sb.transports.TransportException: Failed to create inbound JCABindingService for wsdl: servicebus:/ "<INTEGRATION>_01/Resources/resources/application_901/outbound_302/resourcegroup_397/Eloq_REQUEST.wsdl, operation: execute, exception: BINDING.JCA-12600 Generic error. JCA binding runtime error. Cause: {0}. Please inspect the diagnostic log to determine the reason, and if possible...
- oracle.cloud.connector.api.CloudInvocationException: java.io.IOException: Message sending failed!!
- java.io.IOException: Message sending failed!!
- Message sending failed!!
Moment of Error: This error happened while activating an integration where the Eloqua adapter was configured as a Trigger. Integrations where the Eloqua adapter was configured as an Invoke seemed to work fine.
Solution: We didn’t find a solution for the problem. What we did find was that in the latest release of ICS this problem doesn’t occur.
The version that crashes: Version: 16.3.3.0.0 (160716.2301.0530)
The version that works: Version: 16.4.1.0.0 (160924.1456.0623)
Adapter: Eloqua
ErrorCode: ICS-20575
ErrorMessage:
Integration "<INTEGRATION>" cannot be activated. Incident has been created with ID 27. [Cause: ICS-20575]:
- Integration "<INTEGRATION>" " cannot be activated because of an internal error. Incident has been created with ID: 27.
- com.bea.wli.sb.transports.TransportException: Failed to create inbound JCABindingService for wsdl: servicebus:/ "<INTEGRATION>_01/Resources/resources/application_901/outbound_302/resourcegroup_397/Eloq_REQUEST.wsdl, operation: execute, exception: BINDING.JCA-12600 Generic error. JCA binding runtime error. Cause: {0}. Please inspect the diagnostic log to determine the reason, and if possible...
- oracle.cloud.connector.api.CloudInvocationException: java.io.IOException: Message sending failed!!
- java.io.IOException: Message sending failed!!
- Message sending failed!!
Moment of Error: This error happened while activating an integration where the Eloqua adapter was configured as a Trigger. Integrations where the Eloqua adapter was configured as an Invoke seemed to work fine.
Solution: We didn’t find a solution for the problem. What we did find was that in the latest release of ICS this problem doesn’t occur.
The version that crashes: Version: 16.3.3.0.0 (160716.2301.0530)
The version that works: Version: 16.4.1.0.0 (160924.1456.0623)
This article is written by:
Tomas Brouwers is an IT consultant specialized in integegration with a main focus on Service Oriented Architectures, Enterprise Service Busses, Security and Cloud Based integrations. As an IT enthusiast he loves trying out new software, as I am now working on newer technology as Integration Cloud Service (ICS) and Process Cloud Service (PCS).
Tomas Brouwers is an IT consultant specialized in integegration with a main focus on Service Oriented Architectures, Enterprise Service Busses, Security and Cloud Based integrations. As an IT enthusiast he loves trying out new software, as I am now working on newer technology as Integration Cloud Service (ICS) and Process Cloud Service (PCS).
0 comments:
Post a Comment