-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
provide API to close pooled connections #248
Comments
zhfeng
added a commit
to zhfeng/quarkus-pooled-jms
that referenced
this issue
May 9, 2024
Hi @sjhiggs can you check with the PR You can use the following codes in your application to clear all the connections. The new connection will be created in the next call to the connection pool. @Inject
PooledJmsWrapper wrapper;
void clear() {
wrapper.clearAll();
} And make sure no connection has been used before call |
This works, thanks! |
zhfeng
added a commit
that referenced
this issue
May 11, 2024
zhfeng
added a commit
that referenced
this issue
May 11, 2024
zhfeng
added a commit
that referenced
this issue
May 11, 2024
@sjhiggs I make there releases to add this feature.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In some cases, it is desirable to force all the connections in the pool to close/re-open, e.g. when restarting a Camel route. This allows clients to re-balance when connecting to brokers in a cluster.
For example, in a clustered broker environment, sometimes broker restarts can cause clients to migrate to a small subset of the available brokers. A method to close the connections in the pool would allow the client to load balance across the full set of available brokers.
The text was updated successfully, but these errors were encountered: