I currently have a route: jms consumer -> http in-out producer -> jms producer. I want the route to be transactional. In addition, I want to use continuations in the http producer client to have up to 5k requests outstanding at any one time since the external http service is somewhat long-running and can efficiently process large numbers of requests concurrently. A transactional jms consumer by itself is not useful in this use case since it is not practical to allocate large numbers of concurrentConsumer threads.
In order to support this use case, I thought it might be useful to implement a seda-like component in Camel that is backed by camel-hawtdb to provide transactionality and persistence. The camel-hawtdb backend would likely only be read when recovering from an outage to re-initialize the seda queue. This use case might be supported by the following two routes: 1. jms consumer -> seda:a?transactional=true 2. seda:a -> http in-out producer -> jms producer Any thoughts about how Camel might best be enhanced to support this use case? /Ron -- View this message in context: http://camel.465427.n5.nabble.com/transactional-seda-like-component-backed-by-camel-hawtdb-to-support-reliable-async-long-running-routs-tp509602p509602.html Sent from the Camel - Users mailing list archive at Nabble.com.
