HI Matthew, Thanks for the advice. I will do as advice to apply state to the binary data.
Chris -----Original Message----- From: Matthew Shaw [mailto:[email protected]] Sent: Thursday, November 16, 2017 7:58 PM To: [email protected] Subject: RE: Multiple instance of a camel service Hi, How is the binary data state persisted? My point being I don't think there would be a component in any implementation that would do what you're asking without a great deal of customisation for your process needs. Can you apply state to your binary data, then it doesn't matter what instance of your service in the cluster runs. Let the cluster, behave like a cluster. Cheers, Matt. -----Original Message----- From: Christine Vladic [mailto:[email protected]] Sent: Friday, 17 November 2017 1:34 PM To: [email protected] Subject: Multiple instance of a camel service Hi, I have a quartz camel service that invokes a REST API that returns a binary data. This service will be deployed in a clustered node thus multiple instances will invoke the same REST API and gets the same payload. Question, is there a camel pattern or component that can prevent instances of the same camel service processing the same data. Thank you, Chris This email, including any attachments sent with it, is confidential and for the sole use of the intended recipient(s). This confidentiality is not waived or lost, if you receive it and you are not the intended recipient(s), or if it is transmitted/received in error. Any unauthorised use, alteration, disclosure, distribution or review of this email is strictly prohibited. The information contained in this email, including any attachment sent with it, may be subject to a statutory duty of confidentiality if it relates to health service matters. If you are not the intended recipient(s), or if you have received this email in error, you are asked to immediately notify the sender. You should also delete this email, and any copies, from your computer system network and destroy any hard copies produced. If not an intended recipient of this email, you must not copy, distribute or take any action(s) that relies on it; any form of disclosure, modification, distribution and/or publication of this email is also prohibited. Although the Queensland Ambulance Service takes all reasonable steps to ensure this email does not contain malicious software, the Queensland Ambulance Service does not accept responsibility for the consequences if any person's computer inadvertently suffers any disruption to services, loss of information, harm or is infected with a virus, other malicious computer programme or code that may occur as a consequence of receiving this email. Unless stated otherwise, this email represents only the views of the sender and not the views of the Queensland Government. ******************************************************************************** The content presented in this publication is distributed by the Queensland Government as an information source only. The State of Queensland makes no statements, representations or warranties about the accuracy, completeness or reliability of any information contained in this publication. The State of Queensland disclaims all responsibility and all liability (including without limitation for liability in negligence) for all expenses, losses, damages and costs you might incur as a result of the information being inaccurate or incomplete in any way, and for any reason reliance was placed on such information.
