That sounds correct to me. The issue setting the InstanceLimit was likely introduced in a change where we added the option for TomEE to operate a pool for the MDB container. Previously TomEE did not have that feature as many resource adapters have endpoint pooling in them. We eventually ran into one that didn't - if I remember correctly this in turn caused MDBs to be initialized and discarded which led to performance issues, particularly if you have some complex logic in a @PostConstruct method.
I can't remember exactly when this was introduced - but according to git, it was around TomEE 7.0.5. Jon On Tue, Jul 7, 2020 at 1:16 PM Dignesh <[email protected]> wrote: > Thank you very much Jon. It is clear now. > One more question. Looking at the code changes you made for 7.0.9 version, > I think the instance Limit was honored properly in 7.0.2 -- at least by > looking into the 7.0.2 code base. The only piece of block missing was JMS > monitoring. Can you please confirm if this is correct. May be the > instanceLimit not setting properly was introduced in later versions of > tomee..? > > MdbContainer.java > <http://tomee-openejb.979440.n4.nabble.com/file/t375864/MdbContainer.java> > > > I have attached the 7.0.2 version of file by adding the diff(s) change.Hope > the diff changes i copied are fine :) > > > > -- > Sent from: > http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html >
