Hi Ephemeris-
Seeing a RemoveInfo and ShutdownInfo sounds like something (ie Spring JMS or
Camel) called consumer.close() explicitly
The Spring JMS Template (used by Camel) has a lot of settings that impact how
Consumers get closed — cacheLevel esp and behavior varies with ACK mode.
I’d revie
Hello Matt !
I've executed a tcpdump in the karaf pod, and I observe very strange
things (see attached png file). After the initial connection the
client and server periodically use KeepAliveInfo messages. That seems
to be a normal openWire dialog. But later, the client (10.153.50.183)
changes and
Hello Matt.
Perhaps you've seen my last mail where I said that "failover" and
"keepAlice" do not fix my "consumer is closed"... I've also joined my
pax configuration.
I've reduced my Camel application to get only one consumer. Now logs
are simpler, and I can see that the unique consumer on a queu
Hi Ephemeris-
1. Yes, you should use failover:() even with one URL (esp if using load
balancer)
2. These Camel errors are trick to troubleshoot without seeing all the
settings. Camel JMS uses Spring JMS under the covers, and understanding how
that works in combination with Connection Pooling i
Hello again.
Perhaps you've already seen my previous mail... I've tried some
options and none of them seems to fix my connection issues.
I've tried first adding "failover" over my tcp URL, and then
"keekAlice=true" on the tcp transport, and then the two changes
together, and I have exactly the sa
Hello.
Thanks for your answer.
Do you mean that even if we use a single instance we should use a
failover protocol in our clients configurations like that :
"failover:(tcp:activemq-service:61616)" ?
Do you know if other connection options may actually help (keepAlive,
useKeepAlive, ...) ?
As we
Hi Ephermeris-
Recommendations when running in the cloud is to be sure to enable a lot of
self-healing features. Networking (esp in kubernetes) can be inconsistent when
compared to local developer desktop.
1. Use failover:( .. ) transport in client urls
2. Use PooledConnectionFactory (esp w/ Ca
Hello.
We observe strange messages in our logs about ActiveMQ consumers.
17:33:29.684 WARN [Camel (_context) thread #452 -
JmsConsumer[.internal.queue]] Setup of JMS message listener
invoker failed for destination '.internal.queue' - trying to
recover. Cause: The Consumer is closed
T
