I'm using the TransactionErrorHandler of Camel 2.0.0 and observe an
unexpected transaction-outcome for handled errors. Using the
TransactionErrorHandler with the route
onException(Exception.class).handled(true).process(...);
from(direct:test).transacted().processRef('myFailureProcessor');
On Fri, Nov 20, 2009 at 10:20 AM, Martin Krasser d...@martin-krasser.de wrote:
I'm using the TransactionErrorHandler of Camel 2.0.0 and observe an
unexpected transaction-outcome for handled errors. Using the
TransactionErrorHandler with the route
I know that when I don't declare the local exception handler a rollback
will occur. But how can I handle the exception for returning a custom
response to the sender AND rollback the transaction? Maybe I'm missing
something obvious (?).
Claus Ibsen schrieb:
On Fri, Nov 20, 2009 at 10:20 AM,
On Fri, Nov 20, 2009 at 10:35 AM, Martin Krasser d...@martin-krasser.de wrote:
I know that when I don't declare the local exception handler a rollback will
occur. But how can I handle the exception for returning a custom response to
the sender AND rollback the transaction? Maybe I'm missing
On Fri, Nov 20, 2009 at 10:36 AM, Claus Ibsen claus.ib...@gmail.com wrote:
On Fri, Nov 20, 2009 at 10:35 AM, Martin Krasser d...@martin-krasser.de
wrote:
I know that when I don't declare the local exception handler a rollback will
occur. But how can I handle the exception for returning a
Hi,
I tired to run the following camel configuration:
route
from uri=jms:queue:InQueue/
to uri=direct:d1?allowMultipleConsumers=true/
/route
route
from uri=direct:d1?allowMultipleConsumers=true/
to uri=jms:queue:OutQueue/
/route
My OutQueue is receiving two messages.
If i set
Using
setProperty(Exchange.ROLLBACK_ONLY, Boolean.TRUE)
isn't enough for 2.0.0. This causes the TransactionErrorHandler in this
version to throw an exception too. In 2-1.SNAPSHOT everything works as
expected because of additional logic added to the TransactionErrorHandler.
For getting it
On Fri, Nov 20, 2009 at 11:01 AM, hanuman satyaminto...@gmail.com wrote:
Hi,
I tired to run the following camel configuration:
route
from uri=jms:queue:InQueue/
to uri=direct:d1?allowMultipleConsumers=true/
/route
route
from uri=direct:d1?allowMultipleConsumers=true/
to
On Fri, Nov 20, 2009 at 11:13 AM, Martin Krasser d...@martin-krasser.de wrote:
Using
setProperty(Exchange.ROLLBACK_ONLY, Boolean.TRUE)
isn't enough for 2.0.0. This causes the TransactionErrorHandler in this
version to throw an exception too. In 2-1.SNAPSHOT everything works as
expected
If I add markRollbackOnly() to this router instead of rollback(), I am
getting another error (Transaction exception):
Transaction rolled back because it has been marked as rollback-only
Any idea why this error is coming?
Thanks,
Trivedi
Claus Ibsen-2 wrote:
On Thu, Nov 19, 2009 at 8:40
On Fri, Nov 20, 2009 at 12:34 PM, trivedi kumar b
trivedi.bodlap...@ge.com wrote:
If I add markRollbackOnly() to this router instead of rollback(), I am
getting another error (Transaction exception):
Transaction rolled back because it has been marked as rollback-only
Camel does not set this
Hello
Are there any plans for Camel 2.1 milestone and/or candidate releases?
Cheers
--
S. Ali Tokmen
savas-ali.tok...@bull.net
Office: +33 4 76 29 76 19
GSM:+33 66 43 00 555
Bull, Architect of an Open World TM
http://www.bull.com
On Fri, Nov 20, 2009 at 1:44 PM, S. Ali Tokmen
savas-ali.tok...@bull.net wrote:
Hello
Are there any plans for Camel 2.1 milestone and/or candidate releases?
See more here
http://davsclaus.blogspot.com/2009/11/apache-camel-21-update-on-releaseplan.html
Cheers
--
S. Ali Tokmen
http://davsclaus.blogspot.com/2009/11/apache-camel-21-update-on-releaseplan.html
Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer
*
blog : http://cmoulliard.blogspot.com
twitter : http://twitter.com/cmoulliard
Linkedlin :
Great
Thank you
S. Ali Tokmen
savas-ali.tok...@bull.net
Office: +33 4 76 29 76 19
GSM:+33 66 43 00 555
Bull, Architect of an Open World TM
http://www.bull.com
Charles Moulliard a écrit :
http://davsclaus.blogspot.com/2009/11/apache-camel-21-update-on-releaseplan.html
Charles
Hi,
Thanks Ibsen, it worked.
Anto
On Fri, Nov 20, 2009 at 11:25 AM, Claus Ibsen claus.ib...@gmail.com wrote:
On Fri, Nov 20, 2009 at 5:18 AM, Anto Paul antopaul.l...@gmail.com
wrote:
Hi,
As an example take an FTP poller that has to connect to a server when
a
particular event
the problem, when i look of the attributes of this queue, i found
ConsumerCount 0 and the route of camel is started.
What can you explain this ?
Thank you in advance,
titexe
dulanov wrote:
Do you just write to db or read/write? May be the problem would be solved
by
creating indexes for
Hello,
there's a possibility to schedule a move of messages from one queue to
another, every 1 hour?
If yes, how;)? Thank you for giving me an example:)
Thank you in advance
titexe
--
View this message in context:
May be it's a bug. If you stop camel via JMX, after restart queue
subscriptions aren't restored. Clause, do you know anything about it?
On Fri, Nov 20, 2009 at 6:31 PM, titexe tit...@yahoo.fr wrote:
the problem, when i look of the attributes of this queue, i found
ConsumerCount 0 and the
new Thread(new Runnable() {
@Override public void run() {
try {
PollingConsumer consumer =
getContext().getEndpoint(activemq:queue1).createPollingConsumer();
Producer
Sorry for my example, just see Timer based polling consumer paragraph on
http://camel.apache.org/polling-consumer.html.
On Fri, Nov 20, 2009 at 6:40 PM, Dmitry Ulanov dula...@gmail.com wrote:
new Thread(new Runnable() {
@Override public void run() {
Hi,
You could do the following
from(timer://foo?period=360).
process (new Processor(Exchange exchange) {
exchange.getOut().setBody(My FooBar Message);
}).
to(activemq:MyQueue);
Hi,
You could do the following
from(timer://foo?period=360).
process (new Processor(Exchange exchange) {
exchange.getOut().setBody(My FooBar Message);
}).
to(activemq:MyQueue);
I am looking for a simple method to define (in Spring XML) a route which is
deployed but disabled at startup time. Something like this:
route id=error.queue.to.input.queue enabled=false
from uri=activemq:error.queue/
to uri=activemq:input.queue/
/route
I don't see a way how to do that.
Hi,
Looks like there is something wrong with your route. There is no consumer
established on the queue (i.e (consumer count is zero)...
This can be a problem if there is no message expiry set and you each the
memory and persistence limits set for the broker at broker start-up. You
will max out
I have a transacted route and onException clause that tells Camel to use
original body on redelivery.
If I modify body somewhere in the route, I am expecting to still receive
original body on redelivery.
That works fine if I do something like setBody(constant(xyz)), but if
I use
Hi,
I have the dead letter channel set up to catch errors:
errorHandler(deadLetterChannel(bean:DeadLetterChannelProcessor?method=handleError).maximumRedeliveries(1));
I am getting the incoming object that is causing the error, but I would also
like to get the error/exception this is thrown. Is
On Sat, Nov 21, 2009 at 4:57 AM, sub3 st...@subwest.com wrote:
Hi,
I have the dead letter channel set up to catch errors:
errorHandler(deadLetterChannel(bean:DeadLetterChannelProcessor?method=handleError).maximumRedeliveries(1));
I am getting the incoming object that is causing the error,
On Fri, Nov 20, 2009 at 10:41 AM, Martin Krasser d...@martin-krasser.de wrote:
... not part of the Camel 2.0.0 Javadocs ...
Ah my bad. I missed your obvious statement about using 2.0.0. And the
new markRollbackOnly() was added in 2.1. And hence its of course not
mentioned in the javadoc.
Sorry
On Sat, Nov 21, 2009 at 7:18 AM, Ming Fang mingf...@mac.com wrote:
Does anyone know of a fix for this?
This is a critical problem for us, and for many I would think since this is a
very typical configuration.
Have you asked /searched at the AMQ forum also?
Try creating a small application
Hi,
I think you need to ask the configuration question on ActiveMQ mailing
list.
As camel-jms nothing about about the underlay MQ's protocol. it can't be
configured from camel :(
Willem
Ming Fang wrote:
Does anyone know of a fix for this?
This is a critical problem for us, and for many I
Hi
Your problem is that you defined a route as
onException(Exception.class)
.handled(true)
.useOriginalBody()
.maximumRedeliveries(2)
.to(mock:error);
from(activemq:broken)
32 matches
Mail list logo
