You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Kleczka Peter John <pk...@gmail.com> on 2011/10/08 19:32:59 UTC
Updating cached content without restart?
Hi
I am using Spring for my Camel routes. I have an XSLT component that calls for the style sheet over HTTP. If that resource changes I have to restart ActiveMQ. I read that I could use Camel 2.6 and turn off caching on the XSLT component, but I wonder if there are other methods to refresh this resource. I am using ActiveMQ 5.4.2, and I do want the resource cached, but just want to be able to tell the application to update without a restart.
A second part to this question (apologies if this is more appropriate to an ActiveMQ forum) is that if the web resource is unavailable when I start ActiveMQ, it seems that I must restart ActiveMQ when the web resource becomes available again. Is there a way to tell it to retry?
Re: Updating cached content without restart?
Posted by Claus Ibsen <cl...@gmail.com>.
On Sat, Oct 8, 2011 at 7:32 PM, Kleczka Peter John <pk...@gmail.com> wrote:
> Hi
>
> I am using Spring for my Camel routes. I have an XSLT component that calls for the style sheet over HTTP. If that resource changes I have to restart ActiveMQ. I read that I could use Camel 2.6 and turn off caching on the XSLT component, but I wonder if there are other methods to refresh this resource. I am using ActiveMQ 5.4.2, and I do want the resource cached, but just want to be able to tell the application to update without a restart.
>
I have created a Camel ticket to add a way from JMX to purge the cache
so the resource will be re-loaded
https://issues.apache.org/jira/browse/CAMEL-4528
> A second part to this question (apologies if this is more appropriate to an ActiveMQ forum) is that if the web resource is unavailable when I start ActiveMQ, it seems that I must restart ActiveMQ when the web resource becomes available again. Is there a way to tell it to retry?
>
Do you mean using the Camel XSLT component? Afair it loads the
resource on up-start and will fail if the resource is unavailable
(fail fast).
There is no way to configure it to retry later.
>
>
>
>
>
--
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/