I have narrowed down a performance bottleneck in the Processor I implemented
in a SEDA route using the AWS Kinesis component.
I tested against an "empty" Processor (i.e. that doesn't do anything) and
got the following metrics:
*For the "empty" Processor*:11:10| INFO | MarkerIgnoringBase.java 107
This has been resolved.
The issue was that an older version of the amazon-kinesis-client was being
used for the CamelContext:
com.amazonaws
amazon-kinesis-client
1.6.5
This was incompatible with the Camel Kinesis component 2.18.1.
*Solution*:
I have checked the docs for 2.18.x here:
https://github.com/apache/camel/blob/camel-2.18.x/components/camel-aws/src/main/docs/aws-kinesis-component.adoc
The parameter name hasn't changed, so I still have the issue.
--
View this message in context:
http://camel.465427.n5.nabble.com/AWS-Kinesis
I am using the Camel 2.18.1 Kinesis component.
When I try to use the 'sequenceNumber' parameter in the Kinesis URI as
below:
aws-kinesis://DataFeedStream?amazonKinesisClient=#kinesisClient&delay=30s&backoffIdleThreshold=5&backoffMultiplier=6&bridgeErrorHandler=true&runLoggingLevel=DEBUG&iteratorT