Hello
Le 10/01/2010 09:43, Claus Ibsen a écrit :
The tracer works on the routes only. So it gets activated when any
Exchange gets routed to a Camel route.
So if you custom code send the Exchange to a direct:foo endpoint
which then has a route then it should get traced
Hi,
I have this rourte:
route id=route1
from uri=direct:start /
to uri=bean:compAImpl /
to uri=jms:compB /
to uri=bean:compBImpl /
Hi
Ah the issue is that you are doing request/reply over HTTP and send to
a JMS queue which then also would use request/reply.
But I bet you want to just send the message to the queue and then
continue. For that you must use correct MEP patterns, eg InOnly
See this unit test I added
On Mon, Jan 11, 2010 at 9:01 AM, S. Ali Tokmen
savas-ali.tok...@bull.net wrote:
Hello
Le 10/01/2010 09:43, Claus Ibsen a écrit :
The tracer works on the routes only. So it gets activated when any
Exchange gets routed to a Camel route.
So if you custom code send the Exchange to a direct:foo
On Mon, Jan 11, 2010 at 10:31 AM, yaog yairo...@gmail.com wrote:
InOnly indeed solved my problem, however why doesn't InOut work if my beans
return an Objet and Camel creates a temp replyTo queue?
--
request/reply over JMS requires 2 queues: 1 for request, 1 for reply.
And it also require a
Maybe I am missing something? I know for sure that Camel creates for me a
temp reply queue. as far as I understand from the documentation, the fact
that my listeners attempts a return of an Object should cause Camel to send
that response via the reply queue.
Where am I wrong?
--
View this
On Mon, Jan 11, 2010 at 12:17 PM, yaog yairo...@gmail.com wrote:
Maybe I am missing something? I know for sure that Camel creates for me a
temp reply queue. as far as I understand from the documentation, the fact
that my listeners attempts a return of an Object should cause Camel to send
that
well, If I have;
route id=route1
from uri=direct:start /
to uri=bean:compAImpl /
to uri=jms:compB /
to uri=bean:compBImpl /
/route
and compBImpl returns a
It's a stream caching issue, Camel 2.x disable it by default for better
performance.
You can more information here[1]
[1] http://camel.apache.org/stream-caching.html
Willem
ext2 wrote:
Use .convertBodyTo(String.class) after the from. This will store the HTTP
data
as a String which can be
On Mon, Jan 11, 2010 at 2:29 PM, yaog yairo...@gmail.com wrote:
If I define a route like this:
route id=route1
from uri=direct:start /
to uri=bean:compAImpl /
loadBalance
Adding this option still does not work. Looks like the problematic request
get's lost.
Here is a snippet from the log:
[DefaultErrorHandler] [DefaultMessageListenerContainer-1]: DEBUG: Failed
delivery for exchangeId: ID:yogenLT1-4138-1263218053203-2:7:1:1:1. On
delivery attempt: 0 caught:
Hi
You *must* set some exception the failover should loadbalance
http://camel.apache.org/load-balancer.html
loadBalance
failover
exceptionjava.io.IOException/exception
exceptioncom.mycompany.MyOtherException/exception
/failover
to
Hi
Please always write which version of Camel you are using?
Each new version is greatly improved over the previous.
On Mon, Jan 11, 2010 at 2:29 PM, yaog yairo...@gmail.com wrote:
If I define a route like this:
route id=route1
from uri=direct:start /
From what I understood from the docs the exception list is not mandatory (it
says explicitly: If you do not specify any exceptions it will failover over
any exceptions).
To support the above, please note:
1. After adding exception in the spring file, still doesn't work.
2. Worked with regular
Claus Ibsen-2 wrote:
Hi
Please always write which version of Camel you are using?
Each new version is greatly improved over the previous.
Using latest Camel - 2.1.0
--
View this message in context:
http://old.nabble.com/fail-over-does-not-work-with-jmstp27110432p2704.html
First you should know camel using a Pipeline[1] to connect all the
endpoints and processors together.
If the MEP is InOut, if Pipeline can't get the response from jms:compB
endpoint, the Pipeline will not send the message to the next endpoint or
processor.
For the to endpoint, camel will
+1 for this requirement. Please feel free to create a JIRA[1] for it.
[1] https://issues.apache.org/activemq/browse/CAMEL
Claus Ibsen wrote:
Hi
No there is currently no such end marker, but I do think its possible
to add such one in the Splitter.
Could you create a ticket and attach a small
2010/1/11 yaog yairo...@gmail.com:
well, If I have;
route id=route1
from uri=direct:start /
to uri=bean:compAImpl /
to uri=jms:compB /
to uri=bean:compBImpl /
/route
and compBImpl returns a
Basically, I am evaluating Camel at the moment.
It is desired by our architecture to have routes that activate different
beans (through different queues) and be able to get their responses back to
the caller thread.
So that is what I am trying to do. If I define different routes I will not
be
2010/1/11 yaog yairo...@gmail.com:
Basically, I am evaluating Camel at the moment.
It is desired by our architecture to have routes that activate different
beans (through different queues) and be able to get their responses back to
the caller thread.
So to activate your two beans when a
On Mon, Jan 11, 2010 at 3:35 PM, yaog yairo...@gmail.com wrote:
Basically, I am evaluating Camel at the moment.
It is desired by our architecture to have routes that activate different
beans (through different queues) and be able to get their responses back to
the caller thread.
You need a
Claus Ibsen-2 wrote:
You need a consumer on the JMS queue to send back the reply on the
temporary JMS queue.
If you do not use Camel for that then you need some other stuff to do
that.
If you want to use Camel for that then you need to create a 2nd route
which I posted to you
2010/1/11 yaog yairo...@gmail.com:
Claus Ibsen-2 wrote:
You need a consumer on the JMS queue to send back the reply on the
temporary JMS queue.
If you do not use Camel for that then you need some other stuff to do
that.
If you want to use Camel for that then you need to create a 2nd
For the sake of others. This now works. Thanks for your help:
route id=route1
from uri=direct:start /
to uri=bean:compAImpl /
to uri=jms:compB /
to uri=jms:compC /
On Mon, Jan 11, 2010 at 3:15 PM, yaog yairo...@gmail.com wrote:
From what I understood from the docs the exception list is not mandatory (it
says explicitly: If you do not specify any exceptions it will failover over
any exceptions).
To support the above, please note:
1. After adding
Hi
I have developed a message processing system based on Apache Camel. I use
the file and jetty component to receive incoming messages. The system is
started through the camel spring container.
Now I also want to receive incoming messages over a SOAP web service.
There are many articles about
You can really use either, there's an older tutorial on how to
integrate Axis and Camel here -
http://camel.apache.org/tutorial-axis-camel.html
It was written against Camel 1.5 so there's bound to be some changes
here and there if you're using 2.x. I would say though that it might
be easier to
Hi:
I haven't create a JIRA yet, I thinks I should illustrate my
question more clearly to see if the end-marker is worth to add.
My question could be illustrated by a simplified application:
consume a very large file which store record , and save all the record of
the file to
Sorry, in my previous mail , I call the strategy as release Strategy. The
name is wrong, it should changed as exit strategy. The exit strategy
provide a mechanism to do some cleanup things when a pattern exist;
Ext2 wrote:
Hi:
I haven't create a JIRA yet, I thinks I should illustrate my
I think your first solution is a more easy way to understand and you can
do what you want in your customer bean. It also can handle the exception
of splitting.
What you try to do is wrapping the file-to-db solution in on split tag,
That is not we want camel to do.
Even we provide a
30 matches
Mail list logo
