I know right? It's sort of funny actually. We have one instance of TomEE processing 5k+ msg/s for another purpose, but this one is accessing an external resource that will error out if we go too fast.
We can choke resources by limiting the pool and maxSessions, but we need something more predictable than that. If we add a throttling algorithm to the MDB code, we'll be taking time off the JTA timeout, and Thread.sleep() is hardly ever a good idea. We could possibly limit it with Camel at the broker level, but we don't want to put business logic there. If there was a way to inject delay before the JTA timeout started counting, that would be ideal. -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html
