Hi Robert, any reason to use PoolMaxSize=200 and not 100?
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-21 11:53 GMT-07:00 Robert Bray <[email protected]>: > Thanks Romain, > > In the default case, I have the following config > <Resource id="xxxJmsResourceAdapter" type="ActiveMQResourceAdapter"> > BrokerXmlConfig = > broker:(nio://0.0.0.0:61616?daemon=true)?persistent=true > DataSource = > threadPoolSize 100 > </Resource> > > <Resource id="xxxx/jms/connectionfactory" > type="javax.jms.ConnectionFactory"> > ResourceAdapter = xxJmsResourceAdapter > TransactionSupport xa > PoolMaxSize 200 > </Resource> > > and > <activation-config-property> > > > <activation-config-property-name>maxSessions</activation-config-property-name> > > <activation-config-property-value>100</activation-config-property-value> > </activation-config-property> > > With this config I am able to reproduce this error. It appears that the > session are re-used because we reach maxSessions and when that happens we > get this error. > > > > > > -- > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/java-lang-IllegalStateException-The-last-message-delivery-must-be-completed-wit-h-an-afterDeliver-bed-tp4675921p4675956.html > Sent from the TomEE Users mailing list archive at Nabble.com. >
