-
1. Re: changed PoolSize for MDB of 10 result always to 15 Consumer on the Queue
timfox May 29, 2010 7:23 AM (in response to gip_de)Can you verify if this occurs with 2.1.CR1?
-
2. Re: changed PoolSize for MDB of 10 result always to 15 Consumer on the Queue
ataylor Jun 1, 2010 4:46 AM (in response to timfox)That is correct, PoolSize controls how many MDB's are in th epool not how many consumers there are. maxSessions controls how many sessions/consumers there are.
-
3. Re: changed PoolSize for MDB of 10 result always to 15 Consumer on the Queue
gip_de Jun 2, 2010 12:46 AM (in response to timfox)It is the same behavior in 2.1.CR.
-
4. Re: changed PoolSize for MDB of 10 result always to 15 Consumer on the Queue
gip_de Jun 2, 2010 12:52 AM (in response to ataylor)Hello,
i thought there is a correlation of the Pool-Size of the MDB and the Consumer-Size / maxSessions, because in my Opinion, it makes sense that every bean has it's own session. And so i thought if i reduce the MDB-Pool-Size to 5 i expected there are only 5 Consumer/Sessions on the Queue.
-
5. Re: changed PoolSize for MDB of 10 result always to 15 Consumer on the Queue
ataylor Jun 2, 2010 1:18 AM (in response to gip_de)Like I said before this is correct. Remember that an RA implementation knows nothing about how many MDB's there are. The MDB pool size is controlled by the application server and the sessions controled by the Resource Adapter implementation. From an RA pov there is no way of knowing how many MDB's there are in a pool.
-
6. Re: changed PoolSize for MDB of 10 result always to 15 Consumer on the Queue
timfox Jun 2, 2010 3:41 AM (in response to ataylor)The relationship between the various pool sizes and settings should be explained in the user manual to avoid this kinds of debates.
(I remember asking for this to be added some time back)