I managed to reproduce this here. I used a very simple MDB that just echoed
a message to the console and slept for 5 seconds.
I'd expect to see a single consumer at that point in JConsole, but I'd
expect to see <InstanceLimit> or <MaxSession> number of MDB instances all
running concurrently. As it happens, with your config, I was seeing 10.
I tweaked your config a little:
<Container id="mdbid" type="MESSAGE">
ResourceAdapter = JmsResourceAdapter
InstanceLimit = 100
activation.maxSessions = 80
</Container>
<Resource id="JmsResourceAdapter" type="ActiveMQResourceAdapter">
BrokerXmlConfig = xbean:file:${catalina.home}/conf/activemq.xml
ServerUrl =
nio://localhost:54545?soTimeout=60000&daemon=true&keepAlive=true&connectionTimeout=120000&wireFormat.tcpNoDelayEnabled=true&wireFormat.maxInactivityDuration=240000&wireFormat.maxInactivityDurationInitalDelay=120000
threadPoolSize = 100
</Resource>
<Resource id="jms/ConnectionFactory" type="javax.jms.ConnectionFactory">
ResourceAdapter = JmsResourceAdapter
connectionMaxWaitTime = 30 seconds
MaxThreadPoolSize = 80
</Resource>
It does appear that you've run into a bug where InstanceLimit isn't picked
up correctly, however. I should have a fix committed for that by the end of
the day.
Jon
On Mon, Jul 6, 2020 at 1:49 PM Dignesh <[email protected]> wrote:
> tomee.xml <
> http://tomee-openejb.979440.n4.nabble.com/file/t375864/tomee.xml>
> a.ear <http://tomee-openejb.979440.n4.nabble.com/file/t375864/a.ear>
> I have attached the sample ear file and the tomee.xml file.
> I would be helpful for you to replicate the issue internally.
> Also I have attached the screenshot of single consumer shown in the
> Jconsole
> tool.
> Capture.JPG
> <http://tomee-openejb.979440.n4.nabble.com/file/t375864/Capture.JPG>
>
>
>
> --
> Sent from:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>
