Artem Bilan

Yes, we are planning to address this issue in the current `6.0` timeline.

This looks more like this issue: https://github.com/spring-projects/spring-integration/issues/3576. Please, see the solution in the end. Probably you have the same problem.

What is your `TransactionManager`? The `JdbcMetadataStore.putIfAbsent()` is marked with `@Transactional`. So, if it is declared as a bean and there is an appropriate `TransactionManager` (typically a `DataSourceTransactionManager`), the outer transaction...

OK. It probably would be great if you are able to share with us a simple Spring Boot project which let us to reproduce issue and debug the situation.

Perhaps we need to revise this issue for a similar fix we did in the `DefaultLockRepository`: https://github.com/spring-projects/spring-integration/issues/3733. So, this `JdbcMetadataStore` will be free from `@Transactional` and you will be able...

@oxcafedead , doesn't look like: https://www.eclipse.org/paho/index.php?page=clients/java/index.php. Probably they have plans for that support, but no official release yet. Thanks

Thank you for the pointer, @oxcafedead ! > released this on Jul 14 So, that happened recently. Anyway I see that we need to build v5-compatible channel adapters to support...

Hi @vivianazimbone ! would you mind to elaborate more what exactly Paho does not support yet for v5 protocol? Thanks

For some other point of view: https://github.com/spring-cloud/spring-cloud-schema-registry

I think it's time to change a `LockRegistry.obtain()` contract with such a `Duration leaseTime`. Most of the implementations for distributed locks really provide that functionality to avoid the described situation...