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.
