Hello.

We had a Karaf feature that uses the camel-quartz feature either for direct
quartz endpoint or for periodic file reading. No problem at all...

We have added a new feature with a single quartz endpoint, and it seems
that when this feature is installed, or its bundle stopped or started, the
quartz scheduler resets the other endpoints in old routes.

I think there's a unique shared default scheduler. But is it a normal
behavior for it to produce the kind of interference between bundles ?

We use Camel 3.22.1, Karaf 4.4.4.

Thanks for your help.

Regards.

Reply via email to