We have updated activemq from 5.12.0 to 5.13.3 and it doesnt show queues in
web console.
we were able to find all list of queues at
http://servername:8161/admin/index.jsp in version 5.12.0 but since we
updated it to 5.13.3 it just gives us error that it cant be reached and
since that we cannot mon
ActiveMQ version 5.11.3
No producer flow control.
I've noticed the following issue:
- Consumers
Thanks for the confirmation. Will ignore the message
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Artemis-Replication-error-with-static-connectors-tp4713332p4713347.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Couple of things...
1) This is a DEBUG level message which means you can safely ignore it.
2) The message itself is just saying that the interceptor class
org.apache.activemq.artemis.core.server.impl.ReplicationError is being
executed. This interceptor checks for errors during replication
Hi,
We have a master/slave setup with static connectors. Setup itself is
working fine but we see below message in log files whenever we send message.
Not sure why this message is being logged and anything we need to concerned
off.
00:01:44,801 DEBUG
[org.apache.activemq.artemis.core.protocol.co
No - Camel don’t have a “/dev/null” endpoint. However, if you don’t want the
message to go anywhere, just don’t send it (i.e. bypass the to). If you really
need the to, you can always send it to a log uri - something like
I forgot to mention, we are using (and are currently limited to) version
5.10.2
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Zero-consumers-on-some-brokers-after-reboot-tp4713319p4713328.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
On 06/24/2016 02:14 AM, Gulwinder wrote:
Hi Team,
We are facing performance issues with
failover(tcp://primary,tcp://secondary) url but it was working fine when we
are using a single Url i.e. tcp://primary. I have also tried setting
parameters like randomize,trackmessages etc but no hope.
Has a
Hi Team,
We are facing performance issues with
failover(tcp://primary,tcp://secondary) url but it was working fine when we
are using a single Url i.e. tcp://primary. I have also tried setting
parameters like randomize,trackmessages etc but no hope.
Has anybody encountered this type of issues befo
Hello,
I am working on a project that uses a network of ActiveMQ brokers. We use a
fixed set of network connectors. The test team has been performing outage
tests by shutting down services, killing services, and rebooting servers.
After the outage test, they give the system a moment to recover,
I think most of what's configured in a destinationPolicy is taken care of by
address-settings, and security-settings takes care of a lot of what
authorizationPlugin does. There will probably be details here and there that
need clarification so don't hesitate to ask specific questions.
You ment
I've been digging into the artemis docs and example broker.xml in the binary
distribution. So far I think I understand most of what I would do to migrate
from activemq to artemis.
I'm not entirely clear on what would replace the activemq destinationPolicy,
though. Or other elements like authori
A JMS message has to be acked to remove it from its queue or topic. Since
you have two queues, if a message goes to both queues you need to ack the
copy from each queue. If it only goes to the first queue, you only need to
ack it there.
The default acknowledgement mode is AUTO_ACK, where the mes
Currently the configuration is just pulling from a remote queue to a local
queue and that is it.
The Camel XML config file just has a FROM and TO XML tag.
Some changes are being made upstream that will send messages to my system
that I may not want.
That is the reason for wanting this filtering.
T
14 matches
Mail list logo
