[jira] Updated: (QPID-1941) moved messages remain listed on original queue when viewing messages using JMX, but are not actually considered to still be on the queue
[ https://issues.apache.org/jira/browse/QPID-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-1941: - Status: Ready To Review (was: In Progress) moved messages remain listed on original queue when viewing messages using JMX, but are not actually considered to still be on the queue Key: QPID-1941 URL: https://issues.apache.org/jira/browse/QPID-1941 Project: Qpid Issue Type: Bug Components: Java Broker Reporter: Robbie Gemmell Assignee: Robbie Gemmell Fix For: 0.6 Using trunk r787701 When moving messages from one queue to another using the JMX interfaces, the messages moved remain listed in the viewMessage(from, to) results of the original queue, despite the message count being decremented and the deleteFromTop() and clearQueue() methods not acting on them as they are actually no longer considered part of the queue. As such, someone attempting to 'delete from top' may not be deleting the message they are expecting, if it has previously been moved. Steps to reproduce: Start broker. Start JMS Direct Consumer example. Stop JMS Direct Consumer example. Start JMS Direct Producer example, resulting in 11 messages being left on the queue 'message_queue' on the 'test' virtualhost. Using JMX (via RCP management console, or JConsole), view messages 1 to 11 on 'message_queue', which will return 11 messages as expected. Now move messages 1 to 5 to queue 'ping'. The attributes for 'message_queue' now indicate it contains 6 messages, and 'ping' contains 5, as expected. However, viewing messages 1 to 11 on 'message_queue' again returns all 11 messages when it should only return messages with AMQ ID 6 to 11. Using the DeleteFromTop operation deletes message with AMQ ID 6, which can be verified by viewing messages 1 to 11 and discovering 6 is no longer present. Clearing 'message_queue' at this point removes messages with AMQ ID 7-11 as would normally be expected. However, viewing messages 1 to 11 on 'message_queue' again returns messages with AMQ ID 1 to 5 which it should not. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:dev-subscr...@qpid.apache.org
[jira] Updated: (QPID-1941) moved messages remain listed on original queue when viewing messages using JMX, but are not actually considered to still be on the queue
[ https://issues.apache.org/jira/browse/QPID-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-1941: - Description: Using trunk r787701 When moving messages from one queue to another using the JMX interfaces, the messages moved remain listed in the viewMessage(from, to) results of the original queue, despite the message count being decremented and the deleteFromTop() and clearQueue() methods not acting on them as they are actually no longer considered part of the queue. As such, someone attempting to 'delete from top' may not be deleting the message they are expecting, if it has previously been moved. Steps to reproduce: Start broker. Start JMS Direct Consumer example. Stop JMS Direct Consumer example. Start JMS Direct Producer example, resulting in 11 messages being left on the queue 'message_queue' on the 'test' virtualhost. Using JMX (via RCP management console, or JConsole), view messages 1 to 11 on 'message' queue, which will return 11 messages as expected. Now move messages 1 to 5 to queue 'ping'. The attributes for 'message_queue' now indicate it contains 6 messages, and 'ping' contains 5, as expected. However, viewing messages 1 to 11 on 'message_queue' again returns all 11 messages when it should only return messages with AMQ ID 6 to 11. Using the DeleteFromTop operation deletes message with AMQ ID 6, which can be verified by viewing messages 1 to 11 and discovering 6 is no longer present. Clearing 'message_queue' at this point removes messages with AMQ ID 7-11 as would normally be expected. However, viewing messages 1 to 11 on 'message_queue' again returns messages with AMQ ID 1 to 5 which it should not. was: When moving messages from one queue to another using the JMX interfaces, the messages moved remain listed in the viewMessage(from, to) results of the original queue, despite the message count being decremented and the deleteFromTop() and clearQueue() methods not acting on them as they are actually no longer considered part of the queue. As such, someone attempting to 'delete from top' may not be deleting the message they are expecting, if it has previously been moved. Steps to reproduce: Start broker. Start JMS Direct Consumer example. Stop JMS Direct Consumer example. Start JMS Direct Producer example, resulting in 11 messages being left on the queue 'message_queue' on the 'test' virtualhost. Using JMX (via RCP management console, or JConsole), view messages 1 to 11 on 'message' queue, which will return 11 messages as expected. Now move messages 1 to 5 to queue 'ping'. The attributes for 'message_queue' now indicate it contains 6 messages, and 'ping' contains 5, as expected. However, viewing messages 1 to 11 on 'message_queue' again returns all 11 messages when it should only return messages with AMQ ID 6 to 11. Using the DeleteFromTop operation deletes message with AMQ ID 6, which can be verified by viewing messages 1 to 11 and discovering 6 is no longer present. Clearing 'message_queue' at this point removes messages with AMQ ID 7-11 as would normally be expected. However, viewing messages 1 to 11 on 'message_queue' again returns messages with AMQ ID 1 to 5 which it should not. moved messages remain listed on original queue when viewing messages using JMX, but are not actually considered to still be on the queue Key: QPID-1941 URL: https://issues.apache.org/jira/browse/QPID-1941 Project: Qpid Issue Type: Bug Components: Java Broker Reporter: Robbie Gemmell Fix For: 0.6 Using trunk r787701 When moving messages from one queue to another using the JMX interfaces, the messages moved remain listed in the viewMessage(from, to) results of the original queue, despite the message count being decremented and the deleteFromTop() and clearQueue() methods not acting on them as they are actually no longer considered part of the queue. As such, someone attempting to 'delete from top' may not be deleting the message they are expecting, if it has previously been moved. Steps to reproduce: Start broker. Start JMS Direct Consumer example. Stop JMS Direct Consumer example. Start JMS Direct Producer example, resulting in 11 messages being left on the queue 'message_queue' on the 'test' virtualhost. Using JMX (via RCP management console, or JConsole), view messages 1 to 11 on 'message' queue, which will return 11 messages as expected. Now move messages 1 to 5 to queue 'ping'. The attributes for 'message_queue' now indicate it contains 6 messages, and 'ping' contains 5, as expected. However, viewing messages 1 to 11 on 'message_queue' again returns all 11 messages when it should only return messages with
[jira] Updated: (QPID-1941) moved messages remain listed on original queue when viewing messages using JMX, but are not actually considered to still be on the queue
[ https://issues.apache.org/jira/browse/QPID-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-1941: - Description: Using trunk r787701 When moving messages from one queue to another using the JMX interfaces, the messages moved remain listed in the viewMessage(from, to) results of the original queue, despite the message count being decremented and the deleteFromTop() and clearQueue() methods not acting on them as they are actually no longer considered part of the queue. As such, someone attempting to 'delete from top' may not be deleting the message they are expecting, if it has previously been moved. Steps to reproduce: Start broker. Start JMS Direct Consumer example. Stop JMS Direct Consumer example. Start JMS Direct Producer example, resulting in 11 messages being left on the queue 'message_queue' on the 'test' virtualhost. Using JMX (via RCP management console, or JConsole), view messages 1 to 11 on 'message_queue', which will return 11 messages as expected. Now move messages 1 to 5 to queue 'ping'. The attributes for 'message_queue' now indicate it contains 6 messages, and 'ping' contains 5, as expected. However, viewing messages 1 to 11 on 'message_queue' again returns all 11 messages when it should only return messages with AMQ ID 6 to 11. Using the DeleteFromTop operation deletes message with AMQ ID 6, which can be verified by viewing messages 1 to 11 and discovering 6 is no longer present. Clearing 'message_queue' at this point removes messages with AMQ ID 7-11 as would normally be expected. However, viewing messages 1 to 11 on 'message_queue' again returns messages with AMQ ID 1 to 5 which it should not. was: Using trunk r787701 When moving messages from one queue to another using the JMX interfaces, the messages moved remain listed in the viewMessage(from, to) results of the original queue, despite the message count being decremented and the deleteFromTop() and clearQueue() methods not acting on them as they are actually no longer considered part of the queue. As such, someone attempting to 'delete from top' may not be deleting the message they are expecting, if it has previously been moved. Steps to reproduce: Start broker. Start JMS Direct Consumer example. Stop JMS Direct Consumer example. Start JMS Direct Producer example, resulting in 11 messages being left on the queue 'message_queue' on the 'test' virtualhost. Using JMX (via RCP management console, or JConsole), view messages 1 to 11 on 'message' queue, which will return 11 messages as expected. Now move messages 1 to 5 to queue 'ping'. The attributes for 'message_queue' now indicate it contains 6 messages, and 'ping' contains 5, as expected. However, viewing messages 1 to 11 on 'message_queue' again returns all 11 messages when it should only return messages with AMQ ID 6 to 11. Using the DeleteFromTop operation deletes message with AMQ ID 6, which can be verified by viewing messages 1 to 11 and discovering 6 is no longer present. Clearing 'message_queue' at this point removes messages with AMQ ID 7-11 as would normally be expected. However, viewing messages 1 to 11 on 'message_queue' again returns messages with AMQ ID 1 to 5 which it should not. moved messages remain listed on original queue when viewing messages using JMX, but are not actually considered to still be on the queue Key: QPID-1941 URL: https://issues.apache.org/jira/browse/QPID-1941 Project: Qpid Issue Type: Bug Components: Java Broker Reporter: Robbie Gemmell Fix For: 0.6 Using trunk r787701 When moving messages from one queue to another using the JMX interfaces, the messages moved remain listed in the viewMessage(from, to) results of the original queue, despite the message count being decremented and the deleteFromTop() and clearQueue() methods not acting on them as they are actually no longer considered part of the queue. As such, someone attempting to 'delete from top' may not be deleting the message they are expecting, if it has previously been moved. Steps to reproduce: Start broker. Start JMS Direct Consumer example. Stop JMS Direct Consumer example. Start JMS Direct Producer example, resulting in 11 messages being left on the queue 'message_queue' on the 'test' virtualhost. Using JMX (via RCP management console, or JConsole), view messages 1 to 11 on 'message_queue', which will return 11 messages as expected. Now move messages 1 to 5 to queue 'ping'. The attributes for 'message_queue' now indicate it contains 6 messages, and 'ping' contains 5, as expected. However, viewing messages 1 to 11 on 'message_queue' again returns all 11 messages when it should only
