ASYNC connection mode is blocking `main` thread
mario45211 opened this issue · 1 comments
Describe the bug
By using a native_client option with fallback flag set (which enabled ASYNC connection mode) main thread is blocked, when client is unable to get connection to cluster and prevent application from the proper starting.
Expected behavior
ASYNC mode should let application starts regardless of the Hazeclast connection state, which was clearly pointed out that lack of valid connection would bypass second-level-cache.
Additional context
I'm building my application using Spring Boot with its Hazelcast integration and then connecting to bootstrapped cluster from Hibernate.
Spring Boot: 2.6.6
Hz version: 4.2.4
Dependency: hazelcast-hibernate53, version 2.2.1 (via Spring Boot dependency manager)
My mistake - I've provided many addresses separated by comma, which is not supported by native_client_address property so the client was trying to connect to cluster using single address like host:port,host2:port2.
On the other hand - above should be supported.