Ok so this is not the same pool as the resource adapter one, resource adapter pool has a keep alive ( KeepAliveTime ) of 1 minute by default, this can explain it.
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 9:13 GMT+02:00 tschuler <[email protected]>: > Hi Romain! > > We increased the PoolMaxSize setting for the JmsConnectionFactory: > > Tomee.xml: > [...] > <Resource id="JmsResourceAdapter" type="ActiveMQResourceAdapter"> > BrokerXmlConfig > broker:(tcp://localhost:61616)?persistent=true&useJmx=false > ServerUrl = failover:(tcp://localhost:61616)?randomize=false > DataSource JmsDS > </Resource> > <Resource id="JmsConnectionFactory" type="javax.jms.ConnectionFactory"> > ResourceAdapter = JmsResourceAdapter > PoolMaxSize = 200 > ConnectionMaxIdleMinutes = 0 > TransactionSupport = local > </Resource> > [...] > > Best regards, > Thomas > > > From: Romain Manni-Bucau [via TomEE & OpenEJB] [mailto: > [email protected]] > Sent: Mittwoch, 5. August 2015 09:04 > To: Thomas Schuler <[email protected]> > Subject: Re: No thread reuse > > 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 <[hidden > email]</user/SendEmail.jtp?type=node&node=4675722&i=0>>: > > > 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. > > > > ________________________________ > If you reply to this email, your message will be added to the discussion > below: > > http://tomee-openejb.979440.n4.nabble.com/No-thread-reuse-tp4675721p4675722.html > To unsubscribe from No thread reuse, click here< > http://tomee-openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4675721&code=dGhvbWFzLnNjaHVsZXJAb3BlbnRleHQuY29tfDQ2NzU3MjF8LTE4NTIyNTQ0OTI= > >. > NAML< > http://tomee-openejb.979440.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml > > > > > > > -- > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/No-thread-reuse-tp4675721p4675723.html > Sent from the TomEE Users mailing list archive at Nabble.com. >
