You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The first time worked great, but when the first token expire I am facing jdbc connection failed. My code is showing the refresh token correctly when max-lifetime is ended, and the getToken is called for getPassword.
My code is based on spring and I am using this annotations for generate only one Hikari by application, because I think Hikari don't support multithread with multi-instances, because of that I used the singleton annotation on a @configuration:
@Bean(name = "DataSource")
@Scope(value = ConfigurableBeanFactory.SCOPE_SINGLETON)
//Create datadource with configuration
Could you explain or give an example how to refresh token using this pool of connections. I am feeling that the old connections are stuck and we are not using the new ones
The text was updated successfully, but these errors were encountered:
Hi, Team Hikari =)
Guys I am having difficult to implement Hikari with snowflake, the problem is that I need to refresh the token and for that I use this suggestion:
I just change a little bit because I am using azure, at the end i need to pass this properties:
The first time worked great, but when the first token expire I am facing jdbc connection failed. My code is showing the refresh token correctly when max-lifetime is ended, and the getToken is called for getPassword.
My code is based on spring and I am using this annotations for generate only one Hikari by application, because I think Hikari don't support multithread with multi-instances, because of that I used the singleton annotation on a @configuration:
Could you explain or give an example how to refresh token using this pool of connections. I am feeling that the old connections are stuck and we are not using the new ones
The text was updated successfully, but these errors were encountered: