Hi,
When doing "splitter" processing in parallel does it copy the entire exchange
for each process? I've noticed that after a splitter, i have a parallel
process that calls a restlet like this:
Thanks Karel … I had taken a look at it. Will research it in more detail
> On May 17, 2016, at 11:25 AM, Karel Bernolet wrote:
>
> Have you looked into the leader election integration pattern?
> I think camel-zookeeper and camel-hazelcast support it.
>
> On Tue, May
Hello,
We are getting the below error in Kafka consumer for Camel 2.17 with Kafka
0.9.0.1
2016-05-17 14:43:06,269 [nsfeed-invoice]] INFO AbstractCoordinator
- Marking the coordinator 2147483155 dead.
2016-05-17 14:43:06,274 [nsfeed-invoice]] INFO AbstractCoordinator
-
Actually, you can (I wrote camel-mllp :-) ).
When the camel-mllp component is used as a consumer (i.e. a TCP listener), the
body of the exchange will be a byte[] containing the HL7 message. You can use
the camel-hl7 data format to unmarshal just as you do when you’re using
camel-mina2 or
Have you looked into the leader election integration pattern?
I think camel-zookeeper and camel-hazelcast support it.
On Tue, May 17, 2016 at 4:56 PM, Sherwin Pinto wrote:
> Hi Yogesh,
>
> Thanks for your response. I am evaluating our options . Using quartz in a
> clustered
I see the problem. In 2.15.x the constructor of ManagedRoute was changed
to: this.description = route.getDescription(), however before it was:
this.description = route.toString().
Where toString was defined as "EventDrivenConsumerRoute[" + getEndpoint() +
" -> " + processor + "]" (for
Yes
I'm using mina:tcp and HL7MLLPCodec
after the from in doTry
I'm using unmarshal hapi.
to convert the hl7 message.
with camel-mllp (I don't ave trying) yout can use onException in your
context for handling the parse exception.
A+JYT
--
View this message in context:
Hi Yogesh,
Thanks for your response. I am evaluating our options . Using quartz in a
clustered environment is definitely an option . Are there any other
configurations you would recommend ?
Thanks
Sherwin
> On May 17, 2016, at 7:25 AM, yogu13 wrote:
>
> if you are using
Deepak -
There are quite a few ways to go about this, but I think the easiest thing for
you (given what you said so far), would be to write a bean the behaves the way
you want - set the response code header to what you (i.e.
Exchange.HTTP_RESPONSE_CODE/CamelHttpResponseCode), throw and
As an example in the prior version the getDescription() method would return
something like:
EventDrivenConsumerRoute[Endpoint[file://C:/JMS/gangplank/work/guard_ACK/?delay=1000=true=%23partialFilter=.error=none]
-> Pipeline[[Channel[convertBodyTo[byte[]]], Channel[RecipientList[Simple:
OK - then I don’t think you’ll ever get that body from a real system when
you’re using Camel (unless you do something to make it happen).
Two of the components that support MLLP (camel-mina2, camel-netty4) do NOT
parse/convert the message by default - they just wrap the payload in the MLLP
if you are using timer to trigger the poll for file transfer then quartz
could be used, quartz has cluster support.
Regards,
-Yogesh
--
View this message in context:
http://camel.465427.n5.nabble.com/Running-Same-set-of-Camel-routes-Camel-Context-on-multiple-nodes-tp5782680p5782702.html
Sent
I'm not sure that the body is equal to "error decoding HL7"
I'm using mina and hl7 to implément mllp protocol.
A+JYT
--
View this message in context:
http://camel.465427.n5.nabble.com/choice-when-not-working-as-expected-in-the-camel-route-tp5782452p5782701.html
Sent from the Camel - Users
Hi,
Not clear on the difference. It seems at runtime I only get the last one
set.
Am I expected to use both to serve different purposes?
James
14 matches
Mail list logo