How to unlimit the number of MDB instances listening to a WildFly JMS queue

[Aleksandr Dyog]

Hi, All

The default settings - 15 instances. I need more threads for query handling, up to 100 or 200.

I tied that parameter, but it doesn't work:
@ActivationConfigProperty( propertyName = "maxSession", propertyValue = "100")

And I think, it is only for jBoss, not for WildFly.

Any proposals?

[Rob Spoor]

How about this part of the standalone file?
<server xmlns="urn:jboss:domain:2.2"> ... <profile> ... <subsystem xmlns="urn:jboss:domain:ejb3:2.0"> ... <pools> <bean-instance-pools> ... <strict-max-pool name="mdb-strict-max-pool" max-pool-size="20" .../> </bean-instance-pools> </pools> ...

[Aleksandr Dyog]

Even this size don't help to increase instances count:
<strict-max-pool name="mdb-strict-max-pool" max-pool-size="1000000" instance-acquisition-timeout="2" instance-acquisition-timeout-unit="MINUTES"/>

My regular pool size = 400.

[Aleksandr Dyog]

And I'm talking about these parameters :
http://docs.jboss.org/ejb3/docs/tutorial/mdb/mdb.html
... are there any other places in WildFly where count of instances can be configured ?

[Jaikiran Pai]

Also being discussed here https://developer.jboss.org/thread/261001. As Justin noted in that thread, it's combination of the pool size the and maxSession @ActivationConfigProperty on the MDB. If it still isn't working, please provide more details in that other thread including the exact configurations you are using and also add some details on how you are checking the number of instances.

[Aleksandr Dyog]

Ok, I see...
We change logic and move some critical processes to other part of the system.
So this recommendation check little after ...