On Fri, Jan 28, 2011 at 7:43 PM, rxm0203 wrote:
>
> I have following route with dead letter error handler attached to it.
>
>
>
>
>
>
> My Dead Letter Error Handler definition is as follows. Please note that I
> have 5 minutes delay between retries.
>
> class="org.apache
Hi,
Clearly this is a problem in OpenMQ based on the error you have listed in
your note. The origin of which seems to be in the OpenMQ broker and the
Transaction Manager. The CONSUMER-ACKS transactions are not being recognized
by the OpenMQ Broker. Please make sure that the TransactionManager wir
Ashwin,
The issue clearly wasn't configuration.
I got the same configuration to work with ActiveMQ.
The main issue seems to be something to do with the Open MQ broker
that we're using in testing and production.
I have been able to get the transactions to work locally with ActiveMQ
and now even wit
I have following route with dead letter error handler attached to it.
My Dead Letter Error Handler definition is as follows. Please note that I
have 5 minutes delay between retries.
My fault. The end of the working day.
Everything works just fine.
Best Regards,
Sergey Zhemzhitsky
Sergey Zhemzhitsky/TRD
28.01.2011 18:43
To
users@camel.apache.org
cc
Subject
Error handler: log handled exception
Hi there,
Is it possible to log exception handled by means of errorHan
Hi there,
Is it possible to log exception handled by means of errorHandler.
Consider I have the following configuration
Here logHandled attribute is true.
There is the following piece of code in the
RedeliveryErrorHandler.logFailedDelivery method
if (handled && !data.currentRedelive
Thanks for your explanation.
I am understanding bit by bit of it...
If I have a rest service in different server (http://someserver:9090/rest)
and If I want to use the service
as an endpoint in my routing (using as both consumer and producer endpoint).
Since I dont know the serviceClass I gu
You are using very complicated message exchange pattern. I don't think
current InOut, and InOnly exchange pattern can meet you need.
Maybe you need to do more work yourself to wrap these complicated
interaction into a component :)
On 1/27/11 11:05 PM, Brian wrote:
We are using camel as our c
On 1/28/11 4:17 PM, ghosh wrote:
I could have noticed that.. ..Thanks for the help.
Please help me understand below points
1. why do we need two different bean with same config.. given below...
The camel route just work as a Proxy, it redirect the request to the
real CXF RS server and send
I have found an improvement and created a ticket
https://issues.apache.org/jira/browse/CAMEL-3598
On Wed, Jan 26, 2011 at 5:40 PM, Christian Schneider
wrote:
> I think the options to not have this effect are there in any case. The
> problem is that the default is causing the hang.
> Probably thi
I could have noticed that.. ..Thanks for the help.
Please help me understand below points
1. why do we need two different bean with same config.. given below...
http://localhost:9000/route";
serviceClass="org.apache.camel.component.cxf.jaxrs.testbean.CustomerService"
/>
http://
11 matches
Mail list logo