Done. Thanks!
https://issues.apache.org/jira/browse/CAMEL-5556
--
View this message in context:
http://camel.465427.n5.nabble.com/Understanding-Idempotent-Consumption-tp5718481p5718524.html
Sent from the Camel - Users mailing list archive at Nabble.com.
I experimented with this some more and believe its a race condition
in the HazelcastIdempotentRepository. Patched it and all is well after that.
--
View this message in context:
http://camel.465427.n5.nabble.com/Understanding-Idempotent-Consumption-tp5718481p5718501.html
Sent from the Camel -
Sorry for the very broad question: Can some one please throw some light
on how idempotent consumers actually work?
I would like to have my routes available in a cluster and hence I
am exploring the use of Hazelcase idempotent repository. To prototype
that I experimented with two routes in one co
Claus Ibsen-2 wrote
>
> For topics you need durable subscribers to ensure they receive the
> message.
> As the message will be discarded if sent to a topic with no active
> subscribers.
> Durable subscribers ensures the message will be stored, and send when
> the subscriber becomes active.
>
As
We use Camel to send and receive messages from ActiveMQ and observe that
seemingly randomly our integration tests fail. I have not been able to
observe any pattern and even with Camel turned up to TRACE level, see no
exceptions/errors in the logs.
Most test cases are a variation of the following:
Donald Whytock wrote:
>
> You can do it with a single email endpoint that points to your SMTP
> server, producing an exchange for each event for each user by putting
> the destination email address in the message's "to" header.
>
Thanks and that is what I have planned. When ever the users infor
This might be question that falls in the premature optimization category.
I am working on a project where users create watch lists on the various
events in the system based on
certain criteria and whenever the events that satisfy their criteria are
met, an email is sent to the user. Say
for exam
Thanks Don. But I would like some clarity on the other points - which jar
goes where. My approach of throwing stuff in the various places and seeing
which one sticks just doesn't seem right.
--
View this message in context:
http://camel.465427.n5.nabble.com/Recommended-way-of-packaging-Camel-in-a
I see an older
http://camel.465427.n5.nabble.com/Camel-ActiveMQ-in-Tomcat6-td474122.html
thread talk about this but to understand better (and get clarification on
another issue mentioned below), I would like to know the opinion of the list
on the recommended way of packaging Camel in an webapp. O
Thanks for the inputs.
I was able to get my original example working after tweaking the packageScan
configuration.
The original reason the camel context failed to start was that it complained
that the bean 'Listener' could not
be found. I removed the class, which had the above addListener method
I am working on a abstraction library that would allow a bunch of our
web-apps to include that library and
publish and subscribe to JMS destinations (and do other magical things).
Publication works fine (at least on
the POC I have!) but I am having trouble wrapping my head around
subscriptions.
Th
11 matches
Mail list logo