-
1. Re: Configuration of MDB StrictMaxPool in Standalone.xml
pjhavariotis Dec 15, 2016 11:14 AM (in response to dsatishreddy101)The purpose of bean-instance-pools is to configure how many EJB bean instances can exist in EAP container. In this example, each MDB Bean can have up to 1 bean instance.
-
2. Re: Configuration of MDB StrictMaxPool in Standalone.xml
pjhavariotis Dec 15, 2016 11:24 AM (in response to pjhavariotis)1 of 1 people found this helpfulConsider them as "instance pools", not thread pools. The "max-pool-size", denotes the maximum number of EJB instances that can exist in the pool.
Let's assume that max-pool-size=10; this means that for a particular EJB there can only be 10 instances of that EJB at a time.
If there are more than 10 threads trying to use the particular EJB, then the client will block and wait for an instance to become available. The clients will wait for instance-acquisition-timeout and then throw an exception back if an instance has not become available.
-
3. Re: Configuration of MDB StrictMaxPool in Standalone.xml
dsatishreddy101 Dec 15, 2016 11:55 PM (in response to pjhavariotis)Thank you very much for your reply.
But, Red Hat had not mentioned as clear as you said in any of the documents it had provided on its web site. Have you come across any of document ? If not found also no problem...
Once again, Thank you very much for your quick reply and clear explanation!!!!
Get Outlook for Android<https://aka.ms/ghei36>