I expect that if you configured quartz to use a clustered jobstore, and
connected to the same database with another quartz instance you could add
more triggers, but I don't think the Quartz Component was really designed to
work this way.
Note that its not recommended to insert triggers directly in
Thanks Claus, that was it!
Since the project uses camel-blueprint and camel-blueprint-test, I made the
following exclusion and the problem went away:
org.apache.camel
camel-blueprint
I've spent a whole day trying to get this to work, including upgrading to the
latest Camel (2.11-SNAPSHOT) and ActiveMQ (5.8-SNAPSHOT) to no avail.
The exact same tests work perfectly when the routes are configured in a
Spring definition and tested with the help of CamelSpringTestSupport.
Other p
I have a test class which extends CamelBlueprintTestSupport which has a
number of test methods on it. The tests follow the normal pattern: set mock
expectations/do stuff/make assertions. Sometimes when I run the tests they
all pass, sometimes some of them fail. When they fail I always get the
follo
This is part of a FUSE ESB deployment, so its version 2.10.0.fuse-71-047 of
Camel.
My test class extends CamelBlueprintTestSupport. I use a producerTemplate to
send to the endpoint, like this:
@Produce(uri = "direct-vm:validator")
protected ProducerTemplate validatorProducer;
...
Hi,
I've just split a camel context in two and connected them using direct-vm
like this:
http://camel.apache.org/schema/blueprint"; trace="false">
http://camel.apache.org/schema/blueprint"; trace="false">
...
Now my unit tests on blueprintContext fail randomly (sometimes they pass),
w
