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:
|
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:
|
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:
|
|
Verify that the inputs entered on the Connections page are correct. |
4 | Testing the connection fails with the following
exception:
|
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:
|
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:
|
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:
|
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:
|
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:
|
10 | When a message is being produced without any policy in
place, the instance fails with this
message:
|
Publishing of messages with no policy for a push. | Create the following policy to publish the message for
the stream
group:
Note: If the following policy is created, no
separate policy is required to push
data.
|
11 | When a message is consumed without any policy in place,
the instance fails with the following
message:
|
Consumption of messages with no policy for a pull. | Create the following policy to consume the message for
the stream
group:
Note: If the following policy is created, no
separate policy is required to pull
data:
|
12 | Error Summary:
|
Mapping issue. | Map or populate all fields if the Avro message schema is selected, except where the schema type is a union type. |
13 | Error Summary:
Error Occurrence Scenario: The Read from beginning, Reset to beginning, or Read from specific offset options are selected for the active consumer group. Verification Steps: Ensure that no consumers are running for the specified group and topic partition. Retry after some time. |