Hello,
thank you for the advice regarding the relevance. We've had issues
where we ran out of statelesses from the pool but it was mostly due to,
for instance, overloaded SQL so the real issue what elsewhere. Still it
made us wonder whether we should consider tuning this parameter too.
Given that it's per bean, I guess the default of 10 is likely
appropriate after all yes..
Thank you!
Emmanuel
On 20/12/17 16:45, Romain Manni-Bucau wrote:
it is per bean yes, you can poll them all at once through JMX API
now on the impl itself there are almost no case where a stateless is really
relevant today with CDI (and potentially microprofile or deltaspike
throttler) so maybe check the app really need it before adding tooling on
top of it
Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> | Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau>
2017-12-20 16:43 GMT+01:00 Emmanuel Touzery <
[email protected]>:
Certainly I can't poll every stateless bean in my app, too many of
them, I think it'd have a performance impact on the app.
(I meant I can't poll the active instances through JMX)
emmanuel
