Hi,
is there already in 3.x another way to get this route id to avoid doing the
next?
exchange.getUnitOfWork().getRouteContext().getRoute().getId()
Thanks in advance
Ana
--
View this message in context:
http://camel.465427.n5.nabble.com/Get-routeId-from-Exchange-in-Processor-tp5594662p574308
Hi all,
in my Camel project we are using ActiveMQ queues in a synchronous way. The
basic idea is that we send messages to a queue, adding replyTo=xxx.REPLY to
have a shared fixed reply queue where receive the response.
I´ve started using JMeter to see how reacts the project with not only 1
consum
Hi Claus,
thank you for your quick answer.
With the option to do more frequent polling, do you mean the receiveTimeout
option?
We are using this option to 250, so this should poll messages every 250 ms.
I don´t understand why some messages are always stuck on the reply queue if
the next message
> The messages should be consumed if its JMSCorrelationID matches a id
> that was sent from a request.
Where is this checking done? I could take a look at the code.
> It uses JMSSelector to match which messages to pickup as reply
> messages, that matches JMSCorrelationID set on sending the req
Hi Christian,
> Could you check whether this issue also exists with ActiveMQ 5.7.0!?
I´ve changed to ActiveMQ 5.7.0. I´ve been testing again with JMeter and the
error "The OUT message was not received..." is still happening with messages
that I see they are stuck in the reply queue. They should
This problem only happens with shared fixed reply queues, and not with
exclusive queues.
But we are using a cluster environment, and the Camel documentation says
that exclusive queues are not good for this kind of environments.
--
View this message in context:
http://camel.465427.n5.nabble.c
> Do you have consumers on other boxes that also consume from this
> shared reply queue?
Yes, we have consumers on different cluster nodes for the same reply queue.
So we have to use shared reply queues but there´s still the "stuck messages"
problem :(
Any idea why this problem happens?
-
> Can you try setting prefetch = 1 for the consumers
I´ve added queuePrefetch="1" to the reply queue configuration but there´s
still the same problem.
Depending if we use shared or exclusive reply queues in Camel, do we have to
change the activemq configuration also? If using exclusive reply qu
The problem seems solved if I use cacheConsumer="false" in the
CachingConnectionFactory in the ActiveMQ configuration:
...
cacheConsumers*" value="false" />
Anyone knows why this can solve the problem of the fixed reply queues?
Thanks.
--
View this message in context:
http://came
Hi,
> What version of Camel are you using?
2.10.2
> And how have you configured the JMS component
...
> and the route where you do request/reply?
.to(ExchangePattern.InOut,
"activemq:ActiveMQ.DLQ?replyTo=xxx.
> You can configure this in the endpoint uri directly also
?replyToCacheLevelName=CACHE_NONE
Thanks! I prefer more your solution. Then i don´t need to change the
activemq configuration with cacheConsumers="false" :)
--
View this message in context:
http://camel.465427.n5.nabble.com/JMS-Shar
The replyToCacheLevelName parameter doesn´t solve the problem.
I´ve added the parameter in the configuration:
I´ve also tried adding it to the endpoint:
"activemq:ActiveMQ.DLQ?replyTo=xxx.REPLY&requestTimeout=255000&receiveTimeout=250&timeToLive=51&replyToCacheLevelName=CAC
> Why are you reading from the built-in DLQ queue of the broker? That
seems odd/wrong.
I agree, i don´t like it. But this was there and i don´t know if there is
any weird reason to have that. I would change the queue. Could this cause
any problem?
--
View this message in context:
http://camel
I´ve created a dummy unit test that checks that with fixed shared reply
queues and CachingConnectionFactory, the parameter replyToCacheLevelName
doesn´t solve the stuck messages in the reply queue problem.
In this test, I send 3 messages (at almost the same time) to one queue that
uses the replyTo
nothing about this replyToCacheLevelName problem? ;)
--
View this message in context:
http://camel.465427.n5.nabble.com/JMS-Shared-fixed-reply-queue-doesn-t-consume-all-the-messages-tp5721700p5722393.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi Christian,
thank you for your answers :)
I´ve changed:
new ActiveMQConnectionFactory("tcp://localhost:61616")
to:
new ActiveMQConnectionFactory("vm://myBroker")
With this change i can still reproduce the problem, but if you cannot do it
then I´m missing something...
--
View this message i
I´ve changed the unit test. Now i´m using the CamelJmsTestHelper for the
JmsComponent (now there´s no external broker) and i´ve added setAssertPeriod
to the mock.
/**
* @author anacortes
*/
public class JmsReplyToCacheLevelNameTest extends CamelTestSupport {
protected CamelContext
Do you recommend using PooledConnectionFactory instead of
CachingConnectionFactory?
Because if the replyToCacheLevelName doesn´t solve the problem, maybe we
should change to PooledConnectionFactory...
--
View this message in context:
http://camel.465427.n5.nabble.com/JMS-Shared-fixed-reply-qu
PooledConnectionFactory seems not to cache MessageConsumers. Then, the next
configuration would be the same idea?
PooledConnectionFactory == CachingConnectionFactory+cacheConsumers=false
--
View this message in context:
http://camel.465427.n5.nabble.com/JMS-Shared-fixed-reply-queue-doesn-t-con
Hi all,
does anyone have this problem before? Do you know why is this happening?
Caused by: java.lang.VerifyError: (class:
org/codehaus/groovy/runtime/ArrayUtil, method: createArray signature:
()[Ljava/lang/Object;) Illegal type in constant pool
at
org.codehaus.groovy.runtime.callsite.Ab
Thanks all for your answers :)
The problem is that i´m not using any groovy expression, this is something
that Camel does internally. I´m using Camel 2.10.1.
By default, -XX:ReservedCodeCacheSize was 32, and now it has be changed to
64. Should be 64 enough, or it would be better 128?
Thanks
B
Hi,
my problematic configuration had CachingConnectionFactory (with
cacheConsumers true by default) and not PooledConnectionFactory.
--
View this message in context:
http://camel.465427.n5.nabble.com/JMS-Shared-fixed-reply-queue-doesn-t-consume-all-the-messages-tp5721700p5723546.html
Sent from
Hi Claus,
we are having a similar problem.
Our configuration is:
- Camel 2.10.1
- ActiveMQ 5.5.1
> In Camel 2.9 you can use replyToType=Exclusive, which would then not
have this leak.
We cannot use replyToType=Exclusive because we are using a cluster
environment, so we have to use shared rep
Have you tried also with ActiveMQ 5.5.1? Right now, we are using this version
and we are not allowed to upgrade the AMQ version.
In the end, we should do this because 5.5.1 has a memory leaks bug that has
occasioned us some pain ;)
Best regards,
Ana
--
View this message in context:
http://cam
Hi Scott,
thank you for your answer, it´s really interesting :)
Then we should use PooledConnectionFactory and for that we need to upgrade
also AMQ to 5.7.0.
--
View this message in context:
http://camel.465427.n5.nabble.com/JMS-Shared-fixed-reply-queue-doesn-t-consume-all-the-messages-tp572
PooledConnectionFactory is in 5.5.1 but with the bug:
https://issues.apache.org/jira/browse/CAMEL-4657 and this was affecting us.
For that, i said it would be good for us if we can upgrade to AMQ 5.7 :)
If we cannot do it, we will see the Claus´ idea about using FuseSource
ActiveMQ
distributions
> The test works also with CachingConnectionFactory and ActiveMQ 5.5.1.
> Could you update the test so that it will show your issue? Otherwise I'm
> not sure whether we can find and resolve your issue.
Using cacheConsumers=false with CachingConnectionFactory solved our problem,
and if we can cha
Hi all,
i´m using the spring-ws component to send a request:
because this would affect all the spring-ws .
I´ve added the endpointMapping to the producer parameters
(endpointMapping=#xxx), but this seems it´s not working, the endointMapping
is not being set.
Checking the SpringWebserviceComp
any idea about how to add an endpointMapping to a spring-ws producer? ;)
--
View this message in context:
http://camel.465427.n5.nabble.com/Spring-ws-producer-endpointMapping-tp5728172p5728223.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi all,
I´m working with the Camel LDAP component. As we can read in the
http://camel.apache.org/ldap.html LDAP page "The result is returned in the
Out body".
I´ve seen in the code of LdapProducer.java (process method), that we only
have this line related to the Out message:
exchange.getOut().s
Ok :) i´ve already created a JIRA ticket
https://issues.apache.org/jira/browse/CAMEL-5260
--
View this message in context:
http://camel.465427.n5.nabble.com/LDAP-Component-lose-headers-tp5696602p5696862.html
Sent from the Camel - Users mailing list archive at Nabble.com.
31 matches
Mail list logo
