updated activemq from 5.12.0 to 5.13.3
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 monitor it with nagios. -- View this message in context: http://activemq.2283324.n4.nabble.com/updated-activemq-from-5-12-0-to-5-13-3-tp4713349.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
slow consumers
ActiveMQ version 5.11.3 No producer flow control. I've noticed the following issue: - Consumers are consuming at a consistent rate. - Producer starts sending burst of messages - Queue starts growing - Once queue depth is around 400K+, ActiveMQ stops delivering messages to the consumers. - Eventually, Memory usage reaches to 100%, and it starts impacting other queues, and producers/consumers. To come out of this situation, I enable consumers to drop certain kind of messages (to trigger faster consumption). After this change, ActiveMQ starts delivering messages, and queue gets drained. Looks like to me, ActiveMQ detects the slow consumers for a growing queue, and stops delivering messages. Is it possible to configure ActiveMQ to deliver to all the consumers at an equal rate? i.e. do not smartly balance based on the consumption rate? Trying to avoid the system freeze.
Re: [Artemis] Replication error with static connectors
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.
Re: [Artemis] Replication error with static connectors
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 setup. If you don't see ERROR messages in your log then no error was detected. Justin - Original Message - From: "abhijith"To: users@activemq.apache.org Sent: Friday, June 24, 2016 12:25:28 PM Subject: [Artemis] Replication error with static connectors 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.core.impl.ChannelImpl] Invocation of interceptor org.apache.activemq.artemis.core.server.impl.ReplicationError on PACKET(Ping)[type=10, channelID=0, packetObject=Ping, connectionTTL=6] returned true 00:01:54,801 DEBUG [org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl] Invocation of interceptor org.apache.activemq.artemis.core.server.impl.ReplicationError on PACKET(Ping)[type=10, channelID=0, packetObject=Ping, connectionTTL=6] returned true 00:01:54,802 DEBUG [org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl] Invocation of interceptor org.apache.activemq.artemis.core.server.impl.ReplicationError on PACKET(Ping)[type=10, channelID=0, packetObject=Ping, connectionTTL=6] returned true Any help is appreciated. Thanks. Abhi -- View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-Replication-error-with-static-connectors-tp4713332.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
[Artemis] Replication error with static connectors
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.core.impl.ChannelImpl] Invocation of interceptor org.apache.activemq.artemis.core.server.impl.ReplicationError on PACKET(Ping)[type=10, channelID=0, packetObject=Ping, connectionTTL=6] returned true 00:01:54,801 DEBUG [org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl] Invocation of interceptor org.apache.activemq.artemis.core.server.impl.ReplicationError on PACKET(Ping)[type=10, channelID=0, packetObject=Ping, connectionTTL=6] returned true 00:01:54,802 DEBUG [org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl] Invocation of interceptor org.apache.activemq.artemis.core.server.impl.ReplicationError on PACKET(Ping)[type=10, channelID=0, packetObject=Ping, connectionTTL=6] returned true Any help is appreciated. Thanks. Abhi -- View this message in context: http://activemq.2283324.n4.nabble.com/Artemis-Replication-error-with-static-connectors-tp4713332.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: Help with Camel Config routing using a custom ActiveMQ Message Property
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
Re: Zero consumers on some brokers after reboot
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.
Re: Performance Issues with Failover URL
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 anybody encountered this type of issues before? Your help will be highly appreciated. It is impacting our production instance so kindly revert asap. -- View this message in context: http://activemq.2283324.n4.nabble.com/Performance-Issues-with-Failover-URL-tp4713311.html Sent from the ActiveMQ - User mailing list archive at Nabble.com. Generally it's a good idea to elaborate on what the issue really is, "performance issues" could be just about anything. Also good to document what exactly you tried, and note what the outcome of the things you tried were. -- Tim Bish twitter: @tabish121 blog: http://timbish.blogspot.com/
Performance Issues with Failover URL
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 before? Your help will be highly appreciated. It is impacting our production instance so kindly revert asap. -- View this message in context: http://activemq.2283324.n4.nabble.com/Performance-Issues-with-Failover-URL-tp4713311.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Zero consumers on some brokers after reboot
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, then they check the consumer counts for the queues and topics. They found that sometimes, the consumer counts on a few queues are inconsistent between brokers. The client has connected to the broker without error (a local connection), and that broker shows a consumer. But the broker with a producer connection has a consumer count of 0. In this situation, the producer is still trying to send messages, but they never get to the consumer. Does anyone have advice on how to debug this? We've turned on debug, but its really noisy and we are not sure if there are specific messages or loggers that we should be looking for. We have seen some errors on other brokers when a rebooted system comes back and tries to connect again (this was when the broker wasn't shut down nicely). They other brokers seem to think they still have a connection to that broker (no TCP SYN sent from rebooted broker I assume?). I'm wondering, could it be that there is some sort of race condition when the original connection is cleaned up while a new one is created, and perhaps the new advertisement for consumer interest is cleaned up with it? A few things we have noticed that seem to contribute to the problem: * The AMQ service was not setup correctly to stop nicely on reboot, so it was likely just killed. When this was corrected, we had difficulty reproducing the problem. * It seems limited to queues the consumer creates manually using an ActiveMQConnectionFactory. The camel queues don't seem affected (sorry, not too familiar with camel yet). The ActiveMQConnectionFactory is created like this: Then a connection pool is created with it ("rawFactory" is the factory created above): This is a broker config from one of the servers. They are all the same, except for the tweak to the networkConnectors list. Any hints or tips would be greatly appreciated! Thank you, Frank -- View this message in context: http://activemq.2283324.n4.nabble.com/Zero-consumers-on-some-brokers-after-reboot-tp4713319.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: sample running artemis configs
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 mentioned the examples directory. It contains the best collection of running configs I know of (including clustered configs). Regarding mcollective...I know it has connectors for ActiveMQ and RabbitMQ, but I'm not sure it's been vetted with Artemis. I'd love to hear how it works for you and what issues you run into. Justin - Original Message - From: "Christopher Wood"To: users@activemq.apache.org Sent: Friday, June 24, 2016 8:10:04 AM Subject: sample running artemis configs 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 authorizationPlugin. A hint here would be very welcome. Also, do any of you know of sample running configs anywhere? The examples directory is good but I think seeing how people have clustered their setups might help me as well. I would have brokers clustered together with mcollective using them for stomp.
sample running artemis configs
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 authorizationPlugin. A hint here would be very welcome. Also, do any of you know of sample running configs anywhere? The examples directory is good but I think seeing how people have clustered their setups might help me as well. I would have brokers clustered together with mcollective using them for stomp.
Re: Help with Camel Config routing using a custom ActiveMQ Message Property
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 message is automatically acknowledged when it is first delivered to you (before you have processed it), and that's the mode it sounds like your Camel route is using. So the message is acknowledged when it exits your from tag, and if you want to drop it, you just need to not route it onward to the second queue. So you should test the message for your criteria of which messages you want to process, and conditionally route to the to tag (if the message passes) or end the route without routing the message anywhere (if it fails). Or instead do what Quinn suggested and route to a new topic with no consumers in the second case, so you can wiretap in when necessary. Tim On Jun 24, 2016 6:03 AM, "daelliott"wrote: > 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. > > The DLQ is currently used if the message can't process so we can do some > root analysis on it and fix it. > > The consuming executable application of the local queue is set to > Individual > ACKs of messages. > How the messages are ACK'ed from the remote server I don't know as there is > only the "from" and "to" tags. > You mentioned to ACK the message after consuming it. I'm guessing you meant > in the consuming executable application. > If you did, I was hoping to get the message from the remote server and > filter it out before having it hit the persistent > storage in ActiveMQ and that way the consuming application doesn't have to > deal with it at all. > > From some of the responses and what I have found online, the following seem > to be true > * There is no /dev/null or anything remotely related - I have to route > the > message somewhere I create > * I have to create something to process that queue in some fashion to > clear it out > > Could someone address the retrieving of the property? > Does that look right? >${in.header.FirstProperty}='msgType1' > > Thanks > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Help-with-Camel-Config-routing-using-a-custom-ActiveMQ-Message-Property-tp4713278p4713313.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
Re: Help with Camel Config routing using a custom ActiveMQ Message Property
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. The DLQ is currently used if the message can't process so we can do some root analysis on it and fix it. The consuming executable application of the local queue is set to Individual ACKs of messages. How the messages are ACK'ed from the remote server I don't know as there is only the "from" and "to" tags. You mentioned to ACK the message after consuming it. I'm guessing you meant in the consuming executable application. If you did, I was hoping to get the message from the remote server and filter it out before having it hit the persistent storage in ActiveMQ and that way the consuming application doesn't have to deal with it at all. >From some of the responses and what I have found online, the following seem to be true * There is no /dev/null or anything remotely related - I have to route the message somewhere I create * I have to create something to process that queue in some fashion to clear it out Could someone address the retrieving of the property? Does that look right? ${in.header.FirstProperty}='msgType1' Thanks -- View this message in context: http://activemq.2283324.n4.nabble.com/Help-with-Camel-Config-routing-using-a-custom-ActiveMQ-Message-Property-tp4713278p4713313.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.