BUMP... Anyone ?
welcome to the forums.
As this is a community forum where all people are volunteers you can not expect an answer within such short time.
To answer your question, the pool size is meant per bean type, so you will have a maximum of 500 instances for each EJB.
The pool is filled legacy so if there is a bean with less parallel use there are less instances build and pooled.
Hi Wolf-Dieter Fink,
Thank you for the welcome and a gazillion tons for your response! I had been breaking my head over this since last 2 weeks - hence the urgency.
Will certainly be a little more patient next time. Just a small follow-up query - for understanding purpose; is there any benefit/loss in performance if many pools are created with same max-limit ?
I'm not aware of as you need to have the same number of pooled instances in both cases.
For testing/verification; I tried the initial setting mentioned in my 1st post; set the max size to 15 and deployed my application. For verifying/monitoring i used the jvisualVM Mbeans and found something weirdly interesting...For bean in the application; it definitely says that poolMaxSize is 15 and poolCurrentSize is 3 or 4; (after few operations on application).
However - attribute poolAvailableCount is 106. (it is described as 'no. of avaiable(i.e not-in-use) instances in the pool'. This count keeps increasing significantly after any operation i carry out (which uses the bean). This is true for all beans - however the value is varying. How is this possible ? Is the attribute supposed to mean something else ? Have attached an image below.