The parameter described by Petter will help, but you will still block threads. Another approach is to develop integration as two separate routes. On the first route, you get a jms message, update db and send a second message.
If you use InOnly for the manufacturer of this route and set JMSReplyTo, as well as preserveMessageQuo = true, the camel will send a message, but does not wait for a response.
Then you use the second route, which listens for the response in the specified queue and performs the second db update. This way you are not blocking any threads.
source share