Hi did you set JmsResourceAdapter.MaximumPoolSize to something higher than 30 or JmsResourceAdapter to something <= 0?
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> 2015-08-05 8:49 GMT+02:00 tschuler <[email protected]>: > Hi! > > We are using TomEE 1.7.2 with message driven beans and ActiveMQ 5.11.1. > In general there are about thirty threads that handles the message driven > bean activities (JmsResourceAdapter-worker- - 1, ..., > JmsResourceAdapter-worker- - 30). > > But from time to time we can see that every mdb execution results in a new > thread (JmsResourceAdapter-worker- - XYZ), the threads in the thread pool > are not reused any more. > The amount of available threads is constantly about thirty but the threads > are new and old ones disappear. > > Increasing / Decreasing the thread pool size (ThreadPoolSize parameter for > Resource ActiveMQResourceAdapter) seems to have no impact. > > Is there an idea why this could happen and how to prevent it? > > Best regards, > Thomas > > > > > -- > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/No-thread-reuse-tp4675721.html > Sent from the TomEE Users mailing list archive at Nabble.com. >
