[jira] [Commented] (ARTEMIS-4719) Artemis Metrics plugin reports wrong data
[ https://issues.apache.org/jira/browse/ARTEMIS-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17844214#comment-17844214 ] Mohanavalli A commented on ARTEMIS-4719: Attaching the source code for your reference.[^broker-metrics-plugin.zip] > Artemis Metrics plugin reports wrong data > - > > Key: ARTEMIS-4719 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4719 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Reporter: Mohanavalli A >Priority: Minor > Attachments: 6m peak.png, broker-metrics-plugin.zip, > image-2024-04-10-12-46-10-394.png > > > We are using an Artemis broker metrics plugin to monitor the message count on > each address of the broker. Recently we have noticed that the plugin reported > values which were not realistic and not matching with any of our other > monitoring information available. > !6m peak.png|width=502,height=471! > For a particular address, the plugin reported below values every minute. The > messages count increase from 437k to 5million and 451K to 6million and a fall > from 6M to 462 K are not realistic considering the producer/consumers > capacity. From the values 5M and 6M look to be fake values. > !image-2024-04-10-12-46-10-394.png|width=211,height=429! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4719) Artemis Metrics plugin reports wrong data
[ https://issues.apache.org/jira/browse/ARTEMIS-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohanavalli A updated ARTEMIS-4719: --- Attachment: broker-metrics-plugin.zip > Artemis Metrics plugin reports wrong data > - > > Key: ARTEMIS-4719 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4719 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Reporter: Mohanavalli A >Priority: Minor > Attachments: 6m peak.png, broker-metrics-plugin.zip, > image-2024-04-10-12-46-10-394.png > > > We are using an Artemis broker metrics plugin to monitor the message count on > each address of the broker. Recently we have noticed that the plugin reported > values which were not realistic and not matching with any of our other > monitoring information available. > !6m peak.png|width=502,height=471! > For a particular address, the plugin reported below values every minute. The > messages count increase from 437k to 5million and 451K to 6million and a fall > from 6M to 462 K are not realistic considering the producer/consumers > capacity. From the values 5M and 6M look to be fake values. > !image-2024-04-10-12-46-10-394.png|width=211,height=429! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4719) Artemis Metrics plugin reports wrong data
[ https://issues.apache.org/jira/browse/ARTEMIS-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17838023#comment-17838023 ] Mohanavalli A commented on ARTEMIS-4719: We have a custom metrics plugin implementing ActiveMQMetricsPlugin. This plugin only reads the `artemis.message.count` metric, renames to `eesb.message.count` and add a few tags for monitoring purpose. There is no aggregation and its single value per address. There is no way to reproduce this as of now. > Artemis Metrics plugin reports wrong data > - > > Key: ARTEMIS-4719 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4719 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Reporter: Mohanavalli A >Priority: Minor > Attachments: 6m peak.png, image-2024-04-10-12-46-10-394.png > > > We are using an Artemis broker metrics plugin to monitor the message count on > each address of the broker. Recently we have noticed that the plugin reported > values which were not realistic and not matching with any of our other > monitoring information available. > !6m peak.png|width=502,height=471! > For a particular address, the plugin reported below values every minute. The > messages count increase from 437k to 5million and 451K to 6million and a fall > from 6M to 462 K are not realistic considering the producer/consumers > capacity. From the values 5M and 6M look to be fake values. > !image-2024-04-10-12-46-10-394.png|width=211,height=429! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (ARTEMIS-4719) Artemis Metrics plugin reports wrong data
[ https://issues.apache.org/jira/browse/ARTEMIS-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837138#comment-17837138 ] Mohanavalli A edited comment on ARTEMIS-4719 at 4/15/24 9:32 AM: - Sorry the broker version is 2.32.1. There is no aggregation of any other metrics, its just the `artemis.message.count`. was (Author: JIRAUSER300906): Sorry the broker version is 2.32.1 > Artemis Metrics plugin reports wrong data > - > > Key: ARTEMIS-4719 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4719 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.23.1 >Reporter: Mohanavalli A >Priority: Minor > Attachments: 6m peak.png, image-2024-04-10-12-46-10-394.png > > > Hi Team, > > We are using the Artemis broker metrics plugin to monitor the message count > on each address of the broker. Recently we have noticed that the plugin > reported values which were not realistic and not matching with any of our > other monitoring information available. > !6m peak.png|width=502,height=471! > > For a particular address, the plugin reported below values every minute. The > messages count increase from 437k to 5million and 451K to 6million and a fall > from 6M to 462 K are not realistic considering the producer/consumers > capacity. From the values 5M and 6M look to be fake values. > > !image-2024-04-10-12-46-10-394.png|width=211,height=429! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (ARTEMIS-4719) Artemis Metrics plugin reports wrong data
[ https://issues.apache.org/jira/browse/ARTEMIS-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17837138#comment-17837138 ] Mohanavalli A commented on ARTEMIS-4719: Sorry the broker version is 2.32.1 > Artemis Metrics plugin reports wrong data > - > > Key: ARTEMIS-4719 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4719 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.23.1 >Reporter: Mohanavalli A >Priority: Minor > Attachments: 6m peak.png, image-2024-04-10-12-46-10-394.png > > > Hi Team, > > We are using the Artemis broker metrics plugin to monitor the message count > on each address of the broker. Recently we have noticed that the plugin > reported values which were not realistic and not matching with any of our > other monitoring information available. > !6m peak.png|width=502,height=471! > > For a particular address, the plugin reported below values every minute. The > messages count increase from 437k to 5million and 451K to 6million and a fall > from 6M to 462 K are not realistic considering the producer/consumers > capacity. From the values 5M and 6M look to be fake values. > > !image-2024-04-10-12-46-10-394.png|width=211,height=429! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4719) Artemis Metrics plugin reports wrong data
[ https://issues.apache.org/jira/browse/ARTEMIS-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohanavalli A updated ARTEMIS-4719: --- Description: Hi Team, We are using the Artemis broker metrics plugin to monitor the message count on each address of the broker. Recently we have noticed that the plugin reported values which were not realistic and not matching with any of our other monitoring information available. !6m peak.png|width=502,height=471! For a particular address, the plugin reported below values every minute. The messages count increase from 437k to 5million and 451K to 6million and a fall from 6M to 462 K are not realistic considering the producer/consumers capacity. From the values 5M and 6M look to be fake values. !image-2024-04-10-12-46-10-394.png|width=211,height=429! > Artemis Metrics plugin reports wrong data > - > > Key: ARTEMIS-4719 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4719 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.23.1 >Reporter: Mohanavalli A >Priority: Minor > Attachments: 6m peak.png, image-2024-04-10-12-46-10-394.png > > > Hi Team, > > We are using the Artemis broker metrics plugin to monitor the message count > on each address of the broker. Recently we have noticed that the plugin > reported values which were not realistic and not matching with any of our > other monitoring information available. > !6m peak.png|width=502,height=471! > > For a particular address, the plugin reported below values every minute. The > messages count increase from 437k to 5million and 451K to 6million and a fall > from 6M to 462 K are not realistic considering the producer/consumers > capacity. From the values 5M and 6M look to be fake values. > > !image-2024-04-10-12-46-10-394.png|width=211,height=429! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4719) Artemis Metrics plugin reports wrong data
[ https://issues.apache.org/jira/browse/ARTEMIS-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohanavalli A updated ARTEMIS-4719: --- Attachment: image-2024-04-10-12-46-10-394.png > Artemis Metrics plugin reports wrong data > - > > Key: ARTEMIS-4719 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4719 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.23.1 >Reporter: Mohanavalli A >Priority: Minor > Attachments: 6m peak.png, image-2024-04-10-12-46-10-394.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4719) Artemis Metrics plugin reports wrong data
[ https://issues.apache.org/jira/browse/ARTEMIS-4719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohanavalli A updated ARTEMIS-4719: --- Attachment: 6m peak.png > Artemis Metrics plugin reports wrong data > - > > Key: ARTEMIS-4719 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4719 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: Broker >Affects Versions: 2.23.1 >Reporter: Mohanavalli A >Priority: Minor > Attachments: 6m peak.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4719) Artemis Metrics plugin reports wrong data
Mohanavalli A created ARTEMIS-4719: -- Summary: Artemis Metrics plugin reports wrong data Key: ARTEMIS-4719 URL: https://issues.apache.org/jira/browse/ARTEMIS-4719 Project: ActiveMQ Artemis Issue Type: Bug Components: Broker Affects Versions: 2.23.1 Reporter: Mohanavalli A -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (ARTEMIS-4470) Headers loss in message sent from AMQP producer to AMQP consumer
[ https://issues.apache.org/jira/browse/ARTEMIS-4470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohanavalli A updated ARTEMIS-4470: --- Description: Hi Team, Our message flow involves a AMQP Producer, Broker (with custom plugin) and a AMQP Consumer. The message is sent by Producer to TEST queue with few headers, the broker plugin adds few more headers on BeforeSend event on the TEST queue. When the message is consumed by the consumer from TEST we see loss of certain headers. We started facing this after the recent migration of the consumer from Openwire to AMQP protocol. There is no loss of header when the Producer/Consumer is on openwire. Scenario1 -- Producer(AMQP) to TEST Header1:String, Header2:long Plugin on BeforeSend event on TEST Adds two new headers PluginHeader1(String), PluginHeader2(long) Consumer(AMQP) from TEST Headers : Header1,Header2 (PluginHeader1, PluginHeader2 missing) Additional info: If browsing message in console on TEST: Headers : Header1,Header2,PluginHeader1, PluginHeader2 (All headers are present) If the message is moved from TEST to TEST1 queue directly on the Web Console, the headers PluginHeader1, PluginHeader2 are lost on TEST1 queue. Scenario2 -- Producer(AMQP) Header1:String, Header2:long Plugin Adds two new headers PluginHeader1(String), PluginHeader2(long) Consumer(Openwire) Headers : Header1,Header2,PluginHeader1, PluginHeader2 (All headers are present) Additional info: If browsing message in console on TEST: Headers : Header1,Header2,PluginHeader1, PluginHeader2 (All headers are present) If the message is moved from TEST to TEST1 queue directly on the Web Console, the headers PluginHeader1, PluginHeader2 are lost on TEST1 queue. Scenario3 -- Producer(Openwire) Header1:String, Header2:long Plugin Adds two new headers PluginHeader1(String), PluginHeader2(long) Consumer(AMQP) Headers : Header1,Header2,PluginHeader1, PluginHeader2 (All headers are present) Additional info: If browsing message in console on TEST: Headers : Header1,Header2,PluginHeader1, PluginHeader2 (All headers are present) If the message is moved from TEST to TEST1 queue directly on the Web Console, all headers are present TEST1 queue. Thanks, Mohanavalli A was: Hi Team, Our message flow involves a AMQP Producer, Broker (with custom plugin) and a AMQP Consumer. The message is sent by Producer to TEST queue with few headers, the broker plugin adds few more headers on event on the TEST queue. When the message is consumed by the consumer from TEST we see loss of certain headers. We started facing this after the recent migration of the consumer from Openwire to AMQP protocol. There is no loss of header when the Producer/Consumer is on openwire. Scenario1 -- Producer(AMQP) to TEST Header1:String, Header2:long Plugin on -- event on TEST Adds two new headers PluginHeader1(String), PluginHeader2(long) Consumer(AMQP) from TEST Headers : Header1,Header2 (PluginHeader1, PluginHeader2 missing) Additional info: If browsing message in console on TEST: Headers : Header1,Header2,PluginHeader1, PluginHeader2 (All headers are present) If the message is moved from TEST to TEST1 queue directly on the Web Console, the headers PluginHeader1, PluginHeader2 are lost on TEST1 queue. Scenario2 -- Producer(AMQP) Header1:String, Header2:long Plugin Adds two new headers PluginHeader1(String), PluginHeader2(long) Consumer(Openwire) Headers : Header1,Header2,PluginHeader1, PluginHeader2 (All headers are present) Additional info: If browsing message in console on TEST: Headers : Header1,Header2,PluginHeader1, PluginHeader2 (All headers are present) If the message is moved from TEST to TEST1 queue directly on the Web Console, the headers PluginHeader1, PluginHeader2 are lost on TEST1 queue. Scenario3 -- Producer(Openwire) Header1:String, Header2:long Plugin Adds two new headers PluginHeader1(String), PluginHeader2(long) Consumer(AMQP) Headers : Header1,Header2,PluginHeader1, PluginHeader2 (All headers are present) Additional info: If browsing message in console on TEST: Headers : Header1,Header2,PluginHeader1, PluginHeader2 (All headers are present) If the message is moved from TEST to TEST1 queue directly on the Web Console, all headers are present TEST1 queue. Thanks, Mohanavalli A > Headers loss in message sent from AMQP producer to AMQP consumer > > > Key: ARTEMIS-4470 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4470 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: AMQP, Broker >Affects Versions: 2.31.0 >Reporter: Mohanavalli A >Priority: Major > > Hi Team, > Our message flow involves a AMQP Producer, Broker (with custom plugin) and a > AMQP
[jira] [Created] (ARTEMIS-4470) Headers loss in message sent from AMQP producer to AMQP consumer
Mohanavalli A created ARTEMIS-4470: -- Summary: Headers loss in message sent from AMQP producer to AMQP consumer Key: ARTEMIS-4470 URL: https://issues.apache.org/jira/browse/ARTEMIS-4470 Project: ActiveMQ Artemis Issue Type: Bug Components: AMQP, Broker Affects Versions: 2.31.0 Reporter: Mohanavalli A Hi Team, Our message flow involves a AMQP Producer, Broker (with custom plugin) and a AMQP Consumer. The message is sent by Producer to TEST queue with few headers, the broker plugin adds few more headers on event on the TEST queue. When the message is consumed by the consumer from TEST we see loss of certain headers. We started facing this after the recent migration of the consumer from Openwire to AMQP protocol. There is no loss of header when the Producer/Consumer is on openwire. Scenario1 -- Producer(AMQP) to TEST Header1:String, Header2:long Plugin on -- event on TEST Adds two new headers PluginHeader1(String), PluginHeader2(long) Consumer(AMQP) from TEST Headers : Header1,Header2 (PluginHeader1, PluginHeader2 missing) Additional info: If browsing message in console on TEST: Headers : Header1,Header2,PluginHeader1, PluginHeader2 (All headers are present) If the message is moved from TEST to TEST1 queue directly on the Web Console, the headers PluginHeader1, PluginHeader2 are lost on TEST1 queue. Scenario2 -- Producer(AMQP) Header1:String, Header2:long Plugin Adds two new headers PluginHeader1(String), PluginHeader2(long) Consumer(Openwire) Headers : Header1,Header2,PluginHeader1, PluginHeader2 (All headers are present) Additional info: If browsing message in console on TEST: Headers : Header1,Header2,PluginHeader1, PluginHeader2 (All headers are present) If the message is moved from TEST to TEST1 queue directly on the Web Console, the headers PluginHeader1, PluginHeader2 are lost on TEST1 queue. Scenario3 -- Producer(Openwire) Header1:String, Header2:long Plugin Adds two new headers PluginHeader1(String), PluginHeader2(long) Consumer(AMQP) Headers : Header1,Header2,PluginHeader1, PluginHeader2 (All headers are present) Additional info: If browsing message in console on TEST: Headers : Header1,Header2,PluginHeader1, PluginHeader2 (All headers are present) If the message is moved from TEST to TEST1 queue directly on the Web Console, all headers are present TEST1 queue. Thanks, Mohanavalli A -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (ARTEMIS-4317) Invisible/Unreleased Openwire consumers in Artemis 2.27.x broker queues
Mohanavalli A created ARTEMIS-4317: -- Summary: Invisible/Unreleased Openwire consumers in Artemis 2.27.x broker queues Key: ARTEMIS-4317 URL: https://issues.apache.org/jira/browse/ARTEMIS-4317 Project: ActiveMQ Artemis Issue Type: Bug Components: OpenWire Affects Versions: 2.27.0 Reporter: Mohanavalli A We have a Spring boot + Camel JMS + Activemq Client based consumer connecting to the Artemis 2.27.x broker and consuming messages. When there is a high inflow of messages to the queue where the openwire consumer is connected, the consumer count on the queue increases more than the actual number of consumers connected to the queue, and these invisible or unreleased consumers block the actual consumers from consuming the message. The issue can be replicated on Artemis 2.28.0 as well. There was no issue in Artemis 2.26.0. When then same application with a similar load is tested on Redhat AMQ 7.11.0, the issue does not occur. -- This message was sent by Atlassian Jira (v8.20.10#820010)
