[jira] Resolved: (QPID-652) Correctly handle version mismatches on connection
[ https://issues.apache.org/jira/browse/QPID-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carl Trieloff resolved QPID-652. Resolution: Fixed patch applied Committed revision 799348. > Correctly handle version mismatches on connection > - > > Key: QPID-652 > URL: https://issues.apache.org/jira/browse/QPID-652 > Project: Qpid > Issue Type: Bug > Components: C++ Broker, C++ Client >Affects Versions: M4 >Reporter: Gordon Sim >Assignee: Gordon Sim > -- 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] Resolved: (QPID-1942) create a new queue / exchange / connection selection view
[ https://issues.apache.org/jira/browse/QPID-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1942. - Resolution: Fixed > create a new queue / exchange / connection selection view > - > > Key: QPID-1942 > URL: https://issues.apache.org/jira/browse/QPID-1942 > Project: Qpid > Issue Type: Sub-task > Components: Java Management : JMX Console >Reporter: Robbie Gemmell >Assignee: Aidan Skinner > > create a new queue / exchange / connection selection view, allowing users to > directly open queues etc without adding them to the navigation tree first, > and showing any additional attribute information in a more obvious manner, eg > in a table. -- 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] Resolved: (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 ] Aidan Skinner resolved QPID-1941. - Resolution: Fixed > 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: Aidan Skinner > 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] Resolved: (QPID-1934) Add CPU/GC monitoring to broker test suite
[ https://issues.apache.org/jira/browse/QPID-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1934. - Resolution: Fixed > Add CPU/GC monitoring to broker test suite > -- > > Key: QPID-1934 > URL: https://issues.apache.org/jira/browse/QPID-1934 > Project: Qpid > Issue Type: Improvement > Components: Java Broker, Java Performance Tests >Reporter: Martin Ritchie >Assignee: Aidan Skinner > Fix For: 0.6 > > > Summary: > To get a better idea of how changes are affecting the broker it would be > helpful to be able to track more details during the performance test runs. > Things such as CPU usage and GC statistics could benefit in improving > performance in the system. -- 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] Resolved: (QPID-1937) add an admin user to the example password file
[ https://issues.apache.org/jira/browse/QPID-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1937. - Resolution: Fixed > add an admin user to the example password file > -- > > Key: QPID-1937 > URL: https://issues.apache.org/jira/browse/QPID-1937 > Project: Qpid > Issue Type: Sub-task > Components: Java Broker >Affects Versions: 0.5 >Reporter: Robbie Gemmell >Assignee: Aidan Skinner >Priority: Minor > Fix For: 0.6 > > > Some of the mbeans are only accessible by admin level users. The JMX > management console hides these by default for non-admin users, so it would > helpful if the default plain-text included an admin user like the MD5 hashed > file does to save having to add it. -- 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] Resolved: (QPID-1932) create a new view for the Queue mbeans
[ https://issues.apache.org/jira/browse/QPID-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1932. - Resolution: Fixed > create a new view for the Queue mbeans > -- > > Key: QPID-1932 > URL: https://issues.apache.org/jira/browse/QPID-1932 > Project: Qpid > Issue Type: Sub-task > Components: Java Management : JMX Console >Reporter: Robbie Gemmell >Assignee: Aidan Skinner > > create a new view for the Queue mbeans -- 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] Resolved: (QPID-1931) create a new view for the Logging Management mbean
[ https://issues.apache.org/jira/browse/QPID-1931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1931. - Resolution: Fixed > create a new view for the Logging Management mbean > -- > > Key: QPID-1931 > URL: https://issues.apache.org/jira/browse/QPID-1931 > Project: Qpid > Issue Type: Sub-task > Components: Java Management : JMX Console >Reporter: Robbie Gemmell >Assignee: Aidan Skinner > > create a new view for the Logging Management mbean -- 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-1992) [Logging] Create Operational logging framework
[ https://issues.apache.org/jira/browse/QPID-1992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marnie McCormack updated QPID-1992: --- Attachment: QPID-1992-review.txt > [Logging] Create Operational logging framework > -- > > Key: QPID-1992 > URL: https://issues.apache.org/jira/browse/QPID-1992 > Project: Qpid > Issue Type: New Feature > Components: Java Broker >Reporter: Martin Ritchie >Assignee: Marnie McCormack > Attachments: QPID-1992-review.txt > > > Summary: > As a first step in improving the Java broker's logging operation this work > will provide a new abstraction layer for logging. > Full Design and Technical Details can be found on confluence: > http://cwiki.apache.org/confluence/display/qpid/Status+Update+Design > http://cwiki.apache.org/confluence/display/qpid/Operational+Logging+-+Status+Update+-+Technical+Specification -- 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] Commented: (QPID-1992) [Logging] Create Operational logging framework
[ https://issues.apache.org/jira/browse/QPID-1992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737145#action_12737145 ] Marnie McCormack commented on QPID-1992: Initial review feedback for discussion attached in QPID-1992-review.txt, moving on to run & review associated tests. Hope input useful. > [Logging] Create Operational logging framework > -- > > Key: QPID-1992 > URL: https://issues.apache.org/jira/browse/QPID-1992 > Project: Qpid > Issue Type: New Feature > Components: Java Broker >Reporter: Martin Ritchie >Assignee: Marnie McCormack > Attachments: QPID-1992-review.txt > > > Summary: > As a first step in improving the Java broker's logging operation this work > will provide a new abstraction layer for logging. > Full Design and Technical Details can be found on confluence: > http://cwiki.apache.org/confluence/display/qpid/Status+Update+Design > http://cwiki.apache.org/confluence/display/qpid/Operational+Logging+-+Status+Update+-+Technical+Specification -- 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] Resolved: (QPID-1930) create a new view for the User Management mbean
[ https://issues.apache.org/jira/browse/QPID-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1930. - Resolution: Fixed > create a new view for the User Management mbean > --- > > Key: QPID-1930 > URL: https://issues.apache.org/jira/browse/QPID-1930 > Project: Qpid > Issue Type: Sub-task > Components: Java Management : JMX Console >Reporter: Robbie Gemmell >Assignee: Aidan Skinner > > create a new view for the User Management mbean -- 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] Resolved: (QPID-1929) create a factory class to generate the views for the various MBeans
[ https://issues.apache.org/jira/browse/QPID-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1929. - Resolution: Fixed > create a factory class to generate the views for the various MBeans > --- > > Key: QPID-1929 > URL: https://issues.apache.org/jira/browse/QPID-1929 > Project: Qpid > Issue Type: Sub-task > Components: Java Management : JMX Console >Reporter: Robbie Gemmell >Assignee: Aidan Skinner > > Currently the Eclipse View used in the console to display the operations etc > for each MBean includes all required methods to generate the generic view. > With the introduction of specific view designs for each MBean type this will > be better conducted seperately and handed back to the View for display. -- 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] Resolved: (QPID-1928) remove Queue MBean reliance on AMQException for unused throws clause
[ https://issues.apache.org/jira/browse/QPID-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1928. - Resolution: Fixed > remove Queue MBean reliance on AMQException for unused throws clause > > > Key: QPID-1928 > URL: https://issues.apache.org/jira/browse/QPID-1928 > Project: Qpid > Issue Type: Sub-task >Affects Versions: M2.1, M3, M4, 0.5 >Reporter: Robbie Gemmell >Assignee: Aidan Skinner > Fix For: 0.6 > > > The Queue MBean interface indicates in some methods that it throws > AMQException, but it unused as the AMQE is caught within the implementation -- 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] Resolved: (QPID-1927) move JMX MBean interface definitions to management-common
[ https://issues.apache.org/jira/browse/QPID-1927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1927. - Resolution: Fixed > move JMX MBean interface definitions to management-common > - > > Key: QPID-1927 > URL: https://issues.apache.org/jira/browse/QPID-1927 > Project: Qpid > Issue Type: Sub-task > Components: Java Broker, Java Management : JMX Console >Reporter: Robbie Gemmell >Assignee: Aidan Skinner > > To facilitate making use of the MBean interfaces for generating proxy > objects, the relevant interfaces are to be moved to the management-common > module to break reliance on the complete broker libs. -- 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] Created: (QPID-2016) Reload Log4J configuration file
Reload Log4J configuration file --- Key: QPID-2016 URL: https://issues.apache.org/jira/browse/QPID-2016 Project: Qpid Issue Type: Improvement Components: Java Broker, Java Management : JMX Console Affects Versions: 0.6 Reporter: Aidan Skinner Assignee: Robbie Gemmell Fix For: 0.6 After changing the log4j configuration file through the management console it would be good to be able to force a reload of the file without having to have the watch interval configured. -- 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-2015) Add ability to configure attributes shown on queue list
[ https://issues.apache.org/jira/browse/QPID-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner updated QPID-2015: Component/s: Java Management : JMX Console > Add ability to configure attributes shown on queue list > --- > > Key: QPID-2015 > URL: https://issues.apache.org/jira/browse/QPID-2015 > Project: Qpid > Issue Type: Improvement > Components: Java Management : JMX Console >Affects Versions: 0.6 >Reporter: Aidan Skinner >Assignee: Robbie Gemmell > Fix For: 0.6 > > > The information about a queue displayed on the VirtualHost queue list view > that a user would find useful varies by use case. It would be good to provide > a means for any queue attribute to be added or removed from this view. > The list of attributes should be persisted between invocations of the > management console and should be shared across all instances of the queue > view, not just per virtualhost or per broker. -- 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-2013) Previous/Next N Message button in queue browser should take current size as step size
[ https://issues.apache.org/jira/browse/QPID-2013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner updated QPID-2013: Component/s: (was: Java Broker) Java Management : JMX Console > Previous/Next N Message button in queue browser should take current size as > step size > - > > Key: QPID-2013 > URL: https://issues.apache.org/jira/browse/QPID-2013 > Project: Qpid > Issue Type: Improvement > Components: Java Management : JMX Console >Affects Versions: 0.6 >Reporter: Aidan Skinner >Assignee: Robbie Gemmell > Fix For: 0.6 > > > It would be clearer to calculate the size of the currently displayed range of > messages and use that for the size of messages the next/previous buttons step > through. So if you displayed messages 20-30 you'd have "previous 10" and > "next 10" buttons. -- 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-2014) Clear notifications should prompt when clearing all of them
[ https://issues.apache.org/jira/browse/QPID-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner updated QPID-2014: Component/s: Java Management : JMX Console > Clear notifications should prompt when clearing all of them > --- > > Key: QPID-2014 > URL: https://issues.apache.org/jira/browse/QPID-2014 > Project: Qpid > Issue Type: Improvement > Components: Java Management : JMX Console >Affects Versions: 0.6 >Reporter: Aidan Skinner >Assignee: Robbie Gemmell > Fix For: 0.6 > > > The clear notifications button removes all the notifications if none are > selected. This is a good choice of behaviour, but could be made safer with a > "are you sure? yes/no" prompt in case of user error. -- 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] Created: (QPID-2015) Add ability to configure attributes shown on queue list
Add ability to configure attributes shown on queue list --- Key: QPID-2015 URL: https://issues.apache.org/jira/browse/QPID-2015 Project: Qpid Issue Type: Improvement Affects Versions: 0.6 Reporter: Aidan Skinner Assignee: Robbie Gemmell Fix For: 0.6 The information about a queue displayed on the VirtualHost queue list view that a user would find useful varies by use case. It would be good to provide a means for any queue attribute to be added or removed from this view. The list of attributes should be persisted between invocations of the management console and should be shared across all instances of the queue view, not just per virtualhost or per broker. -- 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] Created: (QPID-2014) Clear notifications should prompt when clearing all of them
Clear notifications should prompt when clearing all of them --- Key: QPID-2014 URL: https://issues.apache.org/jira/browse/QPID-2014 Project: Qpid Issue Type: Improvement Affects Versions: 0.6 Reporter: Aidan Skinner Assignee: Robbie Gemmell Fix For: 0.6 The clear notifications button removes all the notifications if none are selected. This is a good choice of behaviour, but could be made safer with a "are you sure? yes/no" prompt in case of user error. -- 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] Created: (QPID-2013) Previous/Next N Message button in queue browser should take current size as step size
Previous/Next N Message button in queue browser should take current size as step size - Key: QPID-2013 URL: https://issues.apache.org/jira/browse/QPID-2013 Project: Qpid Issue Type: Improvement Components: Java Broker Affects Versions: 0.6 Reporter: Aidan Skinner Assignee: Robbie Gemmell Fix For: 0.6 It would be clearer to calculate the size of the currently displayed range of messages and use that for the size of messages the next/previous buttons step through. So if you displayed messages 20-30 you'd have "previous 10" and "next 10" buttons. -- 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
