NoSuchMethodError: com.amazonaws.transform.JsonUnmarshallerContext.getCurrentToken()

[gigq]

From https://forums.aws.amazon.com/thread.jspa?messageID=585971:

Generating Sensor 1
Exception in thread "main" java.lang.NoSuchMethodError: com.amazonaws.transform.JsonUnmarshallerContext.getCurrentToken()Lcom/fasterxml/jackson/core/JsonToken;
at com.amazonaws.services.kinesis.model.transform.PutRecordResultJsonUnmarshaller.unmarshall(PutRecordResultJsonUnmarshaller.java:40)
at com.amazonaws.services.kinesis.model.transform.PutRecordResultJsonUnmarshaller.unmarshall(PutRecordResultJsonUnmarshaller.java:31)
at com.amazonaws.http.JsonResponseHandler.handle(JsonResponseHandler.java:104)
at com.amazonaws.http.JsonResponseHandler.handle(JsonResponseHandler.java:41)
at com.amazonaws.http.AmazonHttpClient.handleResponse(AmazonHttpClient.java:730)
at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:417)
at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:245)
at com.amazonaws.services.kinesis.AmazonKinesisClient.invoke(AmazonKinesisClient.java:2326)
at com.amazonaws.services.kinesis.AmazonKinesisClient.putRecord(AmazonKinesisClient.java:557)
at producer.SensorReadingProducer.run(SensorReadingProducer.java:151)
at producer.SensorReadingProducer.main(SensorReadingProducer.java:167)

[gigq]

The fix in the forum post also works for me, changing the AWS dependancies from LATEST to 1.9.5 fixes it.

[IanMeyers]

Apologies to everyone who got tripped up by this incorrect pom. I have now updated the project pom.xml to use fixed dependencies on version 1.9.7 of the AWS SDK as well as Commons IO and Collections. Please do post any further issues you might have here.

[gigq]

With this pom I get the following error:

Exception in thread "main" java.lang.NoSuchMethodError: com.fasterxml.jackson.core.JsonFactory.requiresPropertyOrdering()Z
    at com.fasterxml.jackson.databind.ObjectMapper.<init>(ObjectMapper.java:445)
    at com.fasterxml.jackson.databind.ObjectMapper.<init>(ObjectMapper.java:366)
    at com.amazonaws.services.kinesis.aggregators.configuration.ExternalConfigurationModel.<clinit>(ExternalConfigurationModel.java:78)
    at com.amazonaws.services.kinesis.aggregators.factory.ExternallyConfiguredAggregatorFactory.buildFromConfig(ExternallyConfiguredAggregatorFactory.java:50)
    at com.amazonaws.services.kinesis.aggregators.consumer.AggregatorConsumer.buildAggregatorsFromConfig(AggregatorConsumer.java:70)
    at com.amazonaws.services.kinesis.aggregators.consumer.AggregatorConsumer.configure(AggregatorConsumer.java:170)
    at com.amazonaws.services.kinesis.aggregators.consumer.AggregatorConsumer.run(AggregatorConsumer.java:80)
    at com.amazonaws.services.kinesis.aggregators.consumer.AggregatorConsumer.main(AggregatorConsumer.java:258)

[IanMeyers]

Yep - looks like we have some work to do on the Jackson dependencies. I've run the producer with the now updated pom.xml (aws dependencies on version 1.9.5 and explicit dependencies on jackson) and it works ok. Please let me know if you still have issues, and thanks for your patience and perseverance.

Ian

[gigq]

Yep can confirm latest version is working now. Thanks.

[sankarinnoart]

I am using latest versions of jackson(2.6.3). But it's not working facing the same issue.

[sankarinnoart]

Any body having complete java program to access AWS S3 KMS.

[IanMeyers]

@sankarinnoart Understood - currently with the way that the AWS SDK talks to Jackson, you have to use the version included in the pom. I am now researching a full update of all the dependencies to see if we can get to the latest version of Jackson.