The DynamoDbLockRegistry.tryLock() must honor a contract
artembilan opened this issue ยท 4 comments
Turns out the AmazonDynamoDBLockClient.acquireLock()
steps into a busy-wait loop with a sleep time out instead of answering the result immediately like it is required by the tryLock()
contract.
See spring-cloud/spring-cloud-stream-binder-aws-kinesis#186 for more info.
Hi @artembilan do we know when this fix will make it into a public release please? Latest artifact for spring-integration-aws
is 2.5.1
. Otherwise do you suggest any workarounds for this still running on the older version? Thanks
Thanks for heads-up, @francocm !
I think I will release 2.5.2
just tomorrow after I release the current Spring Integration 5.5.14
The version 2.5.2
has been released. Will be available in Maven Central shortly.
Thank you ๐