You can also let the update happen and handle the Exception that will
follow. This is an application level problem.
Hadrian
On 06/14/2011 02:27 AM, Claus Ibsen wrote:
On Mon, Jun 13, 2011 at 1:08 PM, woggle23 wrote:
Morning Team
I have a system with 2 routes similar to the following:
HTTP
On Tue, Jun 14, 2011 at 1:09 PM, woggle23 wrote:
> I was hoping there would be some form of mutual exclusion lock that I could
> enclose the pertinent elements of my route in (within the dsl statement).
>
You can use a routePolicy which can help dictate when a route is
online. The Camel in Action
I was hoping there would be some form of mutual exclusion lock that I could
enclose the pertinent elements of my route in (within the dsl statement).
Howsoever, the alternative option you mention "detect that the 1st route is
active". By active do you "not suspended" or "is currently routing a
m
On Mon, Jun 13, 2011 at 1:08 PM, woggle23 wrote:
> Morning Team
>
> I have a system with 2 routes similar to the following:
>
> HTTP Endpoint -> xmlToSql -> JDBC -> insert/update -> JDBC
>
> POLL-Database -> JDBC -> update/delete -> JDBC
>
> The 1st route receives an xml message via HTTP, then per
Take a look at http://activemq.apache.org/message-groups.html ActiveMQ
Message Groups ...it is designed to provide concurrent processing while
single threading related messages, etc...
Also, you can roll your own locking implementation using
http://camel.apache.org/hazelcast-component.html camel
