Hi,

I am running into the same issue. In my case, the 15 'threads' is a bottleneck that can easily be remedied if I could double or triple the pool sizes. I am able to reduce the size to 10 (or any number below 15) but I cannot increase it.

Am I missing something obvious?

This is the closest to an exaplantion I can find: http://community.jboss.org/wiki/ConfigJBossMDB?decorator=print, See 'General Pooling Notes'.

Cheers,

-H

Thanks for the quick reply, Brad.

Thats great news for us. Which properties did you set in the ActivationConfigProperty section? I already have the @Pool set.

Thanks Brad!

Adding 'maxSession' did the trick for me.

@MessageDriven(
    activationConfig={
        ...
          @ActivationConfigProperty(propertyName="maxSession",propertyValue="50")
     }
)

I tried using MaxPoolSize as you suggested but i got the following error:

No property found for: MaxPoolSize on JavaBean: org.jboss.resource.adapter.jms.inflow.JmsActivationSpec

Cheers!

Thanks for the post. I had the same problem and using both

@PoolClass(value = org.jboss.ejb3.StrictMaxPool.class, maxSize = 30)

and

@ActivationConfigProperty(propertyName = "maxSession", propertyValue = "30")

Helped me.

Thank you

Raj

I have been suffering trying to tune my MDB's pools so I would like to share some things I found out:

1.

Change ejb3-interceptors-aop.xml its only good if you want/can change the config to all of yours ejbs.

If you have, for instance, many MDBs and want to increase the pool for just that critical one, change the ejb3-interceptors-aop.xml may not be a good choice since all others MDB's pools will be increased as well and some memory will be wasted.

Besides that, you are going to increase a bit your deployment complexity since a file outside your ear/jar needs to be managed.

2.

@Pool or @PoolClass?

It depends on your JBoss version. For <= 4.2.3 @PoolClass, otherwise, @Pool.

I tested only in 4.2.3 and 5.1.0.

3.

@ActivationConfigProperty(propertyName = "maxSession", propertyValue = XX)

I keep the XX equal to the pool size. The maxSession property defines the "the maximum number of jms sessions that can concurrently deliver  messages to this mdb", so it makes sense to me keep then equal. What do you think?

4.

Using XML (*-aop.xml)

With an ejb jar inside an ear, I could only make it work with @AspectDomain annotation.

Hope it help!

These are just my experience, if someone want to add something, please, do it!

Hi,

I'm using JBoss 5.1. This configuration has worked for me:

@ActivationConfigProperty(propertyName = "maxSession", propertyValue = "50")})

@Pool (value=PoolDefaults.POOL_IMPLEMENTATION_STRICTMAX,maxSize=50,timeout=20000)

@PoolClass is an attribute for JBoss 4. In JBoss 5 it was replaced by @Pool.

Bye,

For JBoss 5.1, modifying following setting in deploy/jca-jbos-beans.xml works.

<bean name="WorkManagerThreadPool" class="org.jboss.util.threadpool.BasicThreadPool">

....

....

....

<property name="maximumPoolSize">xx</property>

I found that:

{code}
...
@MessageDriven(
...
     @ActivationConfigProperty(propertyName = "maxSession", propertyValue = "100") })
@Pool(value = PoolDefaults.POOL_IMPLEMENTATION_THREADLOCAL, maxSize = 100, timeout = 10000)
...
{code}

have the same effect as (with no @ActivationConfigProperty with maxSession property):

{code}
...
@Pool(value = PoolDefaults.POOL_IMPLEMENTATION_STRICTMAX, maxSize = 100, timeout = 10000)
...
{code}

can somebody explain us with more details the differences between both approaches?

thanks in advance

maxSession determines the amount of session/consumers the resource adapter will create to forward messages into the MDB.

The pool size governs the amount of MDB instances that are available for processing this inflow.

hi Carlo de Wolf

and what the difference of PoolDefaults.POOL_IMPLEMENTATION_THREADLOCAL an PoolDefaults.POOL_IMPLEMENTATION_STRICTMAX

what algorithm should I use and when?

thanks in advance