sounds correct for me
if you want to run tests and see things clearer, you probably can try this
in your MDB instead
@ActivationConfigProperty(propertyName = "maxMessagesPerSessions",
propertyValue = "1")
so each MDB will only fetch 1 message at a time
I am not sure if this parameter is related, but it's another one you can
try, if your configuration is not working as expected.
<Resource id="MyJmsConnectionFactory"
type="javax.jms.ConnectionFactory">
ResourceAdapter = Default\ JMS\ Resource\ Adapter
PoolMaxSize = 100
</Resource>
[]
Leo
On Tue, Sep 22, 2015 at 5:15 PM, sgjava <[email protected]> wrote:
> If I have multiple MDBs that I want to scale to 100 beans simultaneously,
> how
> would I configure TomEE? Currently I'm using:
>
> system.properties:
>
> Default\ JMS\ Resource\ Adapter.ThreadPoolSize=100
> Default\ MDB\ Container.InstanceLimit=100
>
> bean:
>
> @MessageDriven(activationConfig = {
> @ActivationConfigProperty(propertyName = "maxSessions", propertyValue
> = "100"),
> @ActivationConfigProperty(propertyName = "maxMessagesPerSessions",
> propertyValue = "100")})
>
> But this would only cover 100 simultaneous beans? For instance, say I have
> 10 beans that could have 100 messages active at the same time or 1000
> beans.
> How would the configuration look?
>
>
>
> --
> View this message in context:
> http://tomee-openejb.979440.n4.nabble.com/Scaling-MDBs-beyond-default-10-limit-tp4676322.html
> Sent from the TomEE Users mailing list archive at Nabble.com.
>
