the defaut JMS thread pool size is 30 - should be logged - but if you have only 10 sessions you can get this kind of issue, do you care adjusting one of these parameter to the other please?
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-20 21:52 GMT-07:00 Robert Bray <[email protected]>: > The logging hasn't revealed anything terrible interesting, and I have been > unable to find any exceptions thrown in the processing of the message > before > the error, but I have discovered something interesting: > > by decreasing and increasing this setting > > > <activation-config-property-name>maxSessions</activation-config-property-name> > > <activation-config-property-value>10</activation-config-property-value> > </activation-config-property> > I can make the error occur more and less frequently. > > I don't know if this exception is an indication that the concurrency is too > low and we need to catch the exception and retry the message delivery or if > this is unexpected behavior. > > > > -- > 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-tp4675921p4675950.html > Sent from the TomEE Users mailing list archive at Nabble.com. >
