On Thu, Oct 27, 2011 at 12:05 AM, Calvert, Zach (Zach)** CTR **
wrote:
> Just in case anyone cares, the problem was not the route, or the way I was
> sending, but the configuration of the exchange.
>
> I didn't realize the route didn't define the InOut protocol, but you must set
> exchange.setPa
On Thu, Oct 27, 2011 at 2:04 AM, rspeter wrote:
> Thanks for your reply.
>
> I tried sort of this again, but I received a bean exception
> uri="restlet:http://localhost:8077/poc/reply/{id}?restletMethods=post,get"/>
>
> activemq:test.www?selector=JMSCorrelationID %3D
> ${header.id}
>
>
>
Try using properties instead of headers.
2011/10/27 Calvert, Zach (Zach)** CTR ** :
> I have a basic bean object, setters and getters that I want to pass through
> back up the Camel route. It implements serializable and has the generated
> serialVersionUID. I have tried doing
>
> message.setHe
On Wed, Oct 26, 2011 at 9:52 PM, ebinsingh
wrote:
> Hi,
>
> I have a file of 300,000 records and i use the split mechanism of Camel to
> split them and sends each record to a processer.
> Does Camel store these records on a heap or somewhere before it sends them
> to the processer. How does Camel
Are you sending your message through JMS?If so, the default behavior is to only
keep headers with primitive values and String, Date, BigInteger and primitive
wrappers...
I don't know if this can be customized...http://camel.apache.org/jms.html
Cheers,Mathieu
> From: zcalv...@motive.com
> To:
Thanks for your reply.
I tried sort of this again, but I received a bean exception
http://localhost:8077/poc/reply/{id}?restletMethods=post,get"/>
activemq:test.www?selector=JMSCorrelationID %3D
${header.id}
test
Do you have a any other workaround or working example to consume
I have a basic bean object, setters and getters that I want to pass through
back up the Camel route. It implements serializable and has the generated
serialVersionUID. I have tried doing
message.setHeader("myheader", myBean);
message.getExchange().setProperty("myheader", myBean);
But on the b
Just in case anyone cares, the problem was not the route, or the way I was
sending, but the configuration of the exchange.
I didn't realize the route didn't define the InOut protocol, but you must set
exchange.setPattern(ExchangePattern.InOut);
Zach Calvert
-Original Message-
From: C
I try to have a look into it at end of this week.
Best,
Christian
Actually, as a start this morning, I tried using Camel 2.8.2 -- problem
solved! The message rolls back as expected.
We were using Camel 2.7.2.
Thanks,
Michael Kolakowski
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-only-emits-warning-when-destination-queue-is-full-t
It depends... ;-)
If you use XPath to split the file, the entire XML document is loaded into
memory (that's the way how XPath works :-( ).
If you use a line tokenizer (e.g. \n) to split the message, you can chose to
stream the file.
[1] http://camel.apache.org/splitter.html
Best,
Christian
On We
Hi,
I have a file of 300,000 records and i use the split mechanism of Camel to
split them and sends each record to a processer.
Does Camel store these records on a heap or somewhere before it sends them
to the processer. How does Camel splitter internally work.
I want to make sure that the Split
I'm using ServiceMix version 4.3.0 and simply trying to send a synchronous
message where I can get access to the MessageOut at the end.
I have tried using the ProducerTemplate as well as the
camelContext.getEndpoint("myendpoint").createProducer().process(exchange);
And nothing seems to fully fi
I think you can enable sync send to have the message rollback if the
queue is full.
http://activemq.apache.org/async-sends.html
Can you post your Camel route? The entire stacktrace. And possible
which version of Camel you are using?
I think that exception is triggered by Spring JMS, and maybe the
On Wed, Oct 26, 2011 at 4:21 PM, rspeter wrote:
> Good day,
>
> I am trying to use only spring config routes to consume message by
> JMSCorrelationID.
> I tried the following option, but it only works when I hardcode the param.
> Is there any workaround to consume and send response to the client b
Good day,
I am trying to use only spring config routes to consume message by
JMSCorrelationID.
I tried the following option, but it only works when I hardcode the param.
Is there any workaround to consume and send response to the client by only
using spring config without injecting a bean?
Hardc
Hi,
I found the problem and the solution! :-)
The problem is the broker connection. In my test, with standard JMS API, I use
only one connection opened before my sending-loop and closed after.
If a create a connection for every message using JMS API, the execution
consumes more or less the sam
17 matches
Mail list logo