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
Pools insufficient demand to initialize #23
Comments
Just tried with RC32 and get the same problem;
|
Thanks for the report. I'll have a look soon keeping an eye out for possible stalls. |
… the number of active observers #23
…resource can be made available in pool #23
I've
Please give 0.1-RC33 a go (available on Maven Central in about 10 minutes). |
Ah, hold off on Rc33, I don't think I finished the job. |
Yep, finished the review (just checking the insufficient demand part). Please try 0.1-RC33. |
Doesn't seem to have fixed our issue, however I've had a closer look and it appears the issue only occurs if we using a blocking call somewhere down the line. In this case we're calling a method that subsequently requests several hundred database queries but eventually calls a With the blocking operation we get the following output;
|
Ah yes, that could definitely get you into trouble. You might be able to call |
Thanks.. trying to get all our blocking calls switched over. |
Good conversation to have, I think I need to make a section in the README about the trouble we can get into with blocking. |
Hello,
We're having an odd issue when using the pool (see debug output below).
After awhile we start to see database queries just not running (VisualVM confirms no JDBC activity other than the database ping. It looks as though the pool is getting stuck but we're really not sure how/why. It does appear to recover after a period of time
Currently trying to reproduce this in a small simple test
This is the output we get when the database activity stops
What we normally get when working
Pool configuration
I have tried adjusting the above idle times and pool size but it doesn't appear to have any effect.
The executor service has 10 threads.
Any help/thoughts would be appreciated. We'll keep working to get you a test case for it as well.
Note we are using 0.1-rc19, so going to grab the latest version and test it again..
The text was updated successfully, but these errors were encountered: