Troubleshoot Oracle Cloud Infrastructure Streaming Service Adapter Errors

Note the following errors and troubleshooting actions when using the Oracle Cloud Infrastructure Streaming Service Adapter.

Issue Error Error Occurrence Scenario Verification Steps
1 Testing the connection fails with the following exception:
java.util.concurrent.TimeoutException
Wrong port of bootstrap server. Verify that the bootstrap server port provided on the Connections page is correct.
2 Testing the connection fails with the following exception:
OSS-004 : Unable to test connection. Verify Bootstrap Server 
and Trust store details.
Wrong host name of bootstrap server. Verify that the hostname of the bootstrap server provided on the Connections page is correct.
3 Testing the connection fails with the following exception:
OSS-003 : Unable to test connection. Verify Username and Password.
  1. Wrong tenant ID.
  2. Wrong user name.
  3. Wrong stream pool ID.
  4. Wrong password (authentication token).
Verify that the inputs entered on the Connections page are correct.
4 Testing the connection fails with the following exception:
OSS-004 : Unable to test connection. Verify Bootstrap Server and 
Trust store details.
Trust store was not provided (left blank). The trust store on the Connections page cannot be blank.
5 Testing the connection fails with the following exception:
OSS-005 : Unable to test connection. Provide valid Trust store.
Invalid trust store provided. The trust store file does not match the one that contains the public key to connect to the server on the Connections page. Verify that the trust store provided on the Connections page is correct.
6 In the Adapter Endpoint Configuration Wizard, the following exception is displayed:
OSS-006: Unable to find valid Partition or Stream. Verify the OCI 
Streaming Service that you are trying to connect has got valid partition 
and stream available while configuring the adapter.
Provided a file that is not a trust store (for example, you provided a certificate or any text file) or provided an incorrect partition (nonexistent). Verify that you are providing the trust store details or the partition. You must pick up the available stream and partition and have no option to enter any value. However, if the stream and partition that were available at the time of design no later exist, you receive an exception about the nonexisting stream or partition.
7 In the tracking instance, the following exception appears:
{http://schemas.oracle.com/bpel/extension}runtimeFault: Error 
sending bytes: 
oracle.cloud.connector.api.RemoteApplicationException: java.util.concurrent.
ExecutionException: 
org.apache.kafka.common.errors.TimeoutException: Topic OSS_DEMO31 not 
present in metadata after 60000 ms. 
Stream or partition may have been deleted or is inactive. Verify that the stream or partition exists and is active. You may have designed a valid stream or partition, but it may have been deleted later. Therefore, when messages are sent to this integration that was designed with the now nonexistent stream or partition, a runtime exception error is displayed.
8 Error summary:
ICS runtime execution encountered {http://schemas.oracle.com/bpel/extension}
remoteFault while executing operation: Produce Error Code: Produce {http://schemas.oracle.com/bpel/extension}runtimeFault 
Error Reason: Error sending bytes: oracle.cloud.connector.api.RemoteApplicationException: ORABPEL-11208
Given input stream could not be base64 encoded. Base64 decoding failed for InputStream . Check the error stack and fix the 
cause of the error.
Mapping issue. Encode/Decode data with base64 in the mapper based on the use case whenever the target field datatype is xsd:base64Binary. You can click-right the target field in the mapping and select Node Info.
9 When navigating through the Adapter Endpoint Configuration Wizard, the Stream & Partition page shows a blank list for topics and streams. Missing policy. Create the following policy:
Allow group StreamGroup to manage streams in tenancy / compartment
10 When a message is being produced without any policy in place, the instance fails with this message:
Error Reason: Error sending bytes: oracle.cloud.connector.api.RemoteApplicationException: java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.UnknownTopicOrPartitionException: This server does not host this topic-partition. Error Summary: ICS runtime execution encountered {http://schemas.oracle.com/bpel/extension}remoteFault while executing operation: Produce Error Code: Produce {http://schemas.oracle.com/bpel/extension}runtimeFault 
Publishing of messages with no policy for a push. Create the following policy to publish the message for the stream group:
Allow group StreamGroup to manage stream-push in tenancy / compartment
Note: If the following policy is created, no separate policy is required to push data.
Allow group StreamGroup to manage streams in tenancy/ compartment
11 When a message is consumed without any policy in place, the instance fails with the following message:
Error sending bytes: oracle.cloud.connector.api.RemoteApplicationException: org.apache.kafka.common.errors.GroupAuthorizationException: Not authorized to access group: <consumer_group> :Application Error
Consumption of messages with no policy for a pull. Create the following policy to consume the message for the stream group:
Allow group StreamGroup to manage stream-pull in tenancy / compartment 
Note: If the following policy is created, no separate policy is required to pull data:
Allow group StreamGroup to manage streams in tenancy/ compartment
12 Error Summary:
ICS runtime execution encountered {http://schemas.oracle.com/bpel/extension}remoteFault while executing operation: Produce Error Code: Produce 
{http://schemas.oracle.com/bpel/extension}runtimeFault Error Reason: Error sending bytes: oracle.cloud.connector.api.RemoteApplicationException: 
ORABPEL-15236 Translation Failure. Failed to translate XML to JSON. Error while writing AVRO record The data does not conform to the NXSD schema. 
Please correct the problem.
Mapping issue. Map or populate all fields if the Avro message schema is selected, except where the schema type is a union type.