Hello everyone,
It seems that there might be a problem with retrieving the value from
Exchange.REDELIVERY_EXHAUSTED header.
I have a custom defined RedeliveryProcessor which implements Processor and
overrides the public void process(Exchange exchange) method. Within that
method I make a call to:
I also tried
boolean exhausted =
exchange.getIn().getHeader(Exchange.REDELIVERY_EXHAUSTED, Boolean.class);
but that throws a NullPointerException.
--
View this message in context:
http://camel.465427.n5.nabble.com/Unable-to-retrieve-Exchange-REDELIVERY-EXHAUSTED-header-tp3313157p3313158.html
Hi,
Thank you for your reply! That sure makes sense and explains why I wasn't
able to get the header.
However, is there any other way to tell whether it's the last redelivery
from within the redelivery processor? You suggested to retrieve the
REDELIVERY_COUNTER header. Is there a way to retriev
Hi,
Thanks for that!
Regards and Merry Christmas!
Franjo
--
View this message in context:
http://camel.465427.n5.nabble.com/Unable-to-retrieve-Exchange-REDELIVERY-EXHAUSTED-header-tp3313157p3317470.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi everyone!
I'm having this problem with synchronous routes and passing objects back to
the caller.
The route is defined as:
public static final String BEAN = "bean:";
public static final String METHOD = "?method=";
from("activemq:queue:start")
.inOut()
.to(BEAN + "handler" + METHOD +
Hi Ashwin,
thank you for your reply. I looked at the example you gave me and saw that
the route contains only a single queue. When I ran my JUnit test using only
a single queue (activemq:queue:start), I did get a proper reply back. The
timeout only happens when I try to pass something onto the oth
Hi All,
I have an issue with returning an object back to the caller while using the
ProducerTemplate.requestBody() method and ActiveMQ since I upgraded to more
recent versions of Camel (2.9.2) and ActiveMQ (5.5.1). I didn't have such
problems earlier when using Camel 2.5.0 and ActiveMQ 5.4.2, but
Hi,
Thank you both for your replies! I managed to get it running using the
.setExchangePattern(ExchangePattern.InOut) instead of .inOut().
Regards,
Franjo
--
View this message in context:
http://camel.465427.n5.nabble.com/ExchangePattern-InOut-ActiveMQ-problem-tp5680362p5682604.html
Sent from t
