-
Notifications
You must be signed in to change notification settings - Fork 98
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
vertx-mongo: Max number of operations (maxWaitQueueSize) of 500 has been exceeded. #112
Comments
Fixed by #113 - Thanks @johnoliver @gillbates 3.5.0 won't be released for sometime but you can compile from source and get the patched binary |
Actually I think the implementation of our pool is somehow buggy maybe? Otherwise, we don't have to change this value as we use the original mongo driver? |
I am still facing this issue after setting Also the doc on https://vertx.io/docs/vertx-mongo-client/java/ says
Although from the code in PR (https://github.com/vert-x3/vertx-mongo-client/pull/113/files) it appears that this int value is a multiplier, and not the exact value. |
@gaurav-m Can you open a new issue for this please? |
Hello, any update on this issue? I'm unable to set this value (waitQueueMultiple). |
Hi all,
during the development with mongo and vertx, we happened to meet a problem by failed setting the value of maxWaitQueueSize.
i.e, it seemed the vertx-mongo hasnot utilize the pooling for the connections to mongo, which is implemented in the official mongo java driver.
Using the following code with mongo default setup, the vertx-mongo will throw
we've attached a sample code to reproduce the issue, anyone may have a look or having the same issue?
sample code:
ps: It seemed that the vertx-mongo failed provide pooling for developers or am I using in in a wrong way? Otherwise, we don't have to manually specify this value to increase the size ...
The text was updated successfully, but these errors were encountered: