Skip to content

Incorrect documentation (JavaDoc) on PoolOptions.setName() #5579

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

Open
Brada-Groep opened this issue May 27, 2025 · 1 comment
Open

Incorrect documentation (JavaDoc) on PoolOptions.setName() #5579

Brada-Groep opened this issue May 27, 2025 · 1 comment
Labels

Comments

@Brada-Groep
Copy link

The documentation (JavaDoc) on public PoolOptions setName(String) in PoolOptions.java is as follows:

Set the pool name, used when the pool shared, otherwise ignored.
@param name the new name
@return a reference to this, so the API can be used fluently

However, it is not ignored. When you give the PoolOptions the same name as another PoolOptions, they become one (or at least something like that).

Why is this is a problem

Because it said that it was ignored when not shared, I put a generic name on my instances.
However, after one Verticle saturated all the connections inside the pool, my entire API froze. And it took me more than a full day to discover what the problem was.

Proposal

What I think the documentation should look like:

Set the pool name, used when the pool is shared. When multiple PoolOptions instances have the same name, they are merged.
@param name the new name
@return a reference to this, so the API can be used fluently

If the documentation was like this from the beginning, it would've saved me a lot of time. I hope this can be picked up!

@vietj
Copy link
Member

vietj commented May 27, 2025

I think the first pool options is used an there is no merge

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants