[jira] Commented: (QPID-1899) --require-encryption doesn't work unless cyrus sasl authentication is turned on

[ https://issues.apache.org/jira/browse/QPID-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756388#action_12756388 ] Gordon Sim commented on QPID-1899: -- the external ssf also looks interesting; would that all

[jira] Commented: (QPID-1899) --require-encryption doesn't work unless cyrus sasl authentication is turned on

[ https://issues.apache.org/jira/browse/QPID-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756386#action_12756386 ] Gordon Sim commented on QPID-1899: -- looks good to me > --require-encryption doesn't work u

[jira] Commented: (QPID-1899) --require-encryption doesn't work unless cyrus sasl authentication is turned on

[ https://issues.apache.org/jira/browse/QPID-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756217#action_12756217 ] Ken Giusti commented on QPID-1899: -- I've modified the OutputControl objects to export a enc

[jira] Issue Comment Edited: (QPID-1676) Management access to client process name and PID

[ https://issues.apache.org/jira/browse/QPID-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756106#action_12756106 ] Steve Huston edited comment on QPID-1676 at 9/16/09 10:02 AM: --

[jira] Commented: (QPID-1676) Management access to client process name and PID

[ https://issues.apache.org/jira/browse/QPID-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756106#action_12756106 ] Steve Huston commented on QPID-1676: Excellent - works great, Ted - thanks! > Manageme

[jira] Resolved: (QPID-2077) ManagementActorLoggingTest fails to tearDown cleanly

[ https://issues.apache.org/jira/browse/QPID-2077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2077. - Resolution: Fixed > ManagementActorLoggingTest fails to tearDown cleanly > ---

[jira] Resolved: (QPID-2055) failed rename may leave the broker without a log4j configuration when manipulating its contents with the LoggingManagement MBean

[ https://issues.apache.org/jira/browse/QPID-2055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2055. - Resolution: Fixed > failed rename may leave the broker without a log4j configuration when > manip

[jira] Resolved: (QPID-2075) the disconnection process may fail to remove all NotificationListeners and does not close the JMXConnector

[ https://issues.apache.org/jira/browse/QPID-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2075. - Resolution: Fixed > the disconnection process may fail to remove all NotificationListeners and >

[jira] Resolved: (QPID-2051) ensure the expected log4j configuration is used, and check the validity of the Log4J XML configuration file before applying it

[ https://issues.apache.org/jira/browse/QPID-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2051. - Resolution: Fixed > ensure the expected log4j configuration is used, and check the validity of >

[jira] Resolved: (QPID-2052) allow setting a Log4J logger to inherit its level from an ancestor

[ https://issues.apache.org/jira/browse/QPID-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2052. - Resolution: Fixed > allow setting a Log4J logger to inherit its level from an ancestor > -

[jira] Resolved: (QPID-2043) create a new JMX management console testing spec

[ https://issues.apache.org/jira/browse/QPID-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2043. - Resolution: Fixed > create a new JMX management console testing spec > ---

[jira] Resolved: (QPID-2044) create a new JMX management console user guide

[ https://issues.apache.org/jira/browse/QPID-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2044. - Resolution: Fixed > create a new JMX management console user guide > -

[jira] Resolved: (QPID-2042) update to the management access rights may not be saved to disk, but still report success

[ https://issues.apache.org/jira/browse/QPID-2042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2042. - Resolution: Fixed > update to the management access rights may not be saved to disk, but still >

[jira] Resolved: (QPID-2039) the JMX ConnectorServer is not closed during shutdown of the JMXManagedObjectRegistry

[ https://issues.apache.org/jira/browse/QPID-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2039. - Resolution: Fixed > the JMX ConnectorServer is not closed during shutdown of the > JMXManagedObje

[jira] Resolved: (QPID-2040) failed update to the PlainPasswordFilePrincipalDatabase on disk may go unnoticed, preventing broker restart

[ https://issues.apache.org/jira/browse/QPID-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2040. - Resolution: Fixed > failed update to the PlainPasswordFilePrincipalDatabase on disk may go > unno

[jira] Resolved: (QPID-2037) navigation tree node doesnt auto-expand upon connection when adding a new server

[ https://issues.apache.org/jira/browse/QPID-2037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2037. - Resolution: Fixed > navigation tree node doesnt auto-expand upon connection when adding a new > s

[jira] Resolved: (QPID-2036) SimpleAMQQueue getMessagesRangeOnTheQueue(from,to) incorrectly shows the last message on a queue following its deletion

[ https://issues.apache.org/jira/browse/QPID-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2036. - Resolution: Fixed > SimpleAMQQueue getMessagesRangeOnTheQueue(from,to) incorrectly shows the last

[jira] Resolved: (QPID-2032) AddUser operation in the new UserManagement UI does not MD5 hash the password when connected to pre-0.5 brokers

[ https://issues.apache.org/jira/browse/QPID-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2032. - Resolution: Fixed > AddUser operation in the new UserManagement UI does not MD5 hash the password

[jira] Resolved: (QPID-2021) provide new icons to distinguish the various 'manager' mbeans

[ https://issues.apache.org/jira/browse/QPID-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2021. - Resolution: Fixed > provide new icons to distinguish the various 'manager' mbeans > --

[jira] Resolved: (QPID-2018) Clear queue doesn't clear acquired messages which is a little confusing if that's all there is.

[ https://issues.apache.org/jira/browse/QPID-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2018. - Resolution: Fixed > Clear queue doesn't clear acquired messages which is a little confusing if >

[jira] Resolved: (QPID-2016) Reload Log4J configuration file

[ https://issues.apache.org/jira/browse/QPID-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2016. - Resolution: Fixed > Reload Log4J configuration file > --- > >

[jira] Resolved: (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 resolved QPID-2015. - Resolution: Fixed > Add ability to configure attributes shown on queue list >

[jira] Resolved: (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 resolved QPID-2014. - Resolution: Fixed > Clear notifications should prompt when clearing all of them >

[jira] Resolved: (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 resolved QPID-2013. - Resolution: Fixed > Previous/Next N Message button in queue browser should take current size as >

[jira] Resolved: (QPID-2007) new UI dialogs open in the upper left corner of the screen on Windows

[ https://issues.apache.org/jira/browse/QPID-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2007. - Resolution: Fixed > new UI dialogs open in the upper left corner of the screen on Windows > --

[jira] Resolved: (QPID-2009) password fields are not masked in the new UserManagement UI

[ https://issues.apache.org/jira/browse/QPID-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2009. - Resolution: Fixed > password fields are not masked in the new UserManagement UI >

[jira] Resolved: (QPID-2008) queue names are not sorted when presented for user selection in some new UI dialogs

[ https://issues.apache.org/jira/browse/QPID-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2008. - Resolution: Fixed > queue names are not sorted when presented for user selection in some new UI >

[jira] Resolved: (QPID-2000) retrieving attributes for the queue selection list takes excessively long with large numbers of queues

[ https://issues.apache.org/jira/browse/QPID-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2000. - Resolution: Fixed > retrieving attributes for the queue selection list takes excessively long > w

[jira] Resolved: (QPID-2005) change the Fanout Exchange JMX bindings() results to return a single binding entry with all bound queues

[ https://issues.apache.org/jira/browse/QPID-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2005. - Resolution: Fixed > change the Fanout Exchange JMX bindings() results to return a single binding

[jira] Resolved: (QPID-2003) Coverage report is unable to show generated files

[ https://issues.apache.org/jira/browse/QPID-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2003. - Resolution: Fixed > Coverage report is unable to show generated files > --

[jira] Resolved: (QPID-1995) Notification tabs all start a thread on creation, and never halt them

[ https://issues.apache.org/jira/browse/QPID-1995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1995. - Resolution: Fixed > Notification tabs all start a thread on creation, and never halt them > --

[jira] Resolved: (QPID-1999) the Clear button in each VirtualHost Notifications area still clears all server-wide Notifications

[ https://issues.apache.org/jira/browse/QPID-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1999. - Resolution: Fixed > the Clear button in each VirtualHost Notifications area still clears all > se

[jira] Resolved: (QPID-1991) remove the containing Type folders for the top-level single mbeans in the server navigation tree

[ https://issues.apache.org/jira/browse/QPID-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1991. - Resolution: Fixed > remove the containing Type folders for the top-level single mbeans in the > s

[jira] Resolved: (QPID-1994) auto-refresh mechanism can generate NPE during application shutdown

[ https://issues.apache.org/jira/browse/QPID-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1994. - Resolution: Fixed > auto-refresh mechanism can generate NPE during application shutdown >

[jira] Resolved: (QPID-2056) the Add To Favourites and Open Queue buttons stop working after changing the attribute selection on the Queues selection view

[ https://issues.apache.org/jira/browse/QPID-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2056. - Resolution: Fixed > the Add To Favourites and Open Queue buttons stop working after changing the

[jira] Resolved: (QPID-1980) Java broker does not parse protection I/O configuration with expected XML structure

[ https://issues.apache.org/jira/browse/QPID-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1980. - Resolution: Fixed > Java broker does not parse protection I/O configuration with expected XML > s

[jira] Resolved: (QPID-1990) provide ability to determine queue order of messages when viewing via JMX

[ https://issues.apache.org/jira/browse/QPID-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1990. - Resolution: Fixed > provide ability to determine queue order of messages when viewing via JMX > --

[jira] Resolved: (QPID-2059) SubscriptionLoggingTest fails intermittently

[ https://issues.apache.org/jira/browse/QPID-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2059. - Resolution: Fixed > SubscriptionLoggingTest fails intermittently > ---

[jira] Resolved: (QPID-1981) Expose message copying ability through JMX

[ https://issues.apache.org/jira/browse/QPID-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1981. - Resolution: Fixed > Expose message copying ability through JMX > -

[jira] Resolved: (QPID-2068) add a key-value based dialog for creating headers exchange bindings

[ https://issues.apache.org/jira/browse/QPID-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2068. - Resolution: Fixed > add a key-value based dialog for creating headers exchange bindings >

[jira] Resolved: (QPID-2060) LogMonitorTest.testWaitForMessage_Found fails

[ https://issues.apache.org/jira/browse/QPID-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2060. - Resolution: Fixed > LogMonitorTest.testWaitForMessage_Found fails > --

[jira] Resolved: (QPID-2069) Headers Exchange MBean rejects new bindings that contains keys with an empty value

[ https://issues.apache.org/jira/browse/QPID-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2069. - Resolution: Fixed > Headers Exchange MBean rejects new bindings that contains keys with an empty

[jira] Resolved: (QPID-2070) open the default queue mbean when double clicking a channel entry

[ https://issues.apache.org/jira/browse/QPID-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2070. - Resolution: Fixed > open the default queue mbean when double clicking a channel entry > --

[jira] Resolved: (QPID-2071) JMX connections properly closed by the server are not cleaned up by the console

[ https://issues.apache.org/jira/browse/QPID-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2071. - Resolution: Fixed > JMX connections properly closed by the server are not cleaned up by the > con

[jira] Resolved: (QPID-2072) some tables in the new UI are missing default sort indicators

[ https://issues.apache.org/jira/browse/QPID-2072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2072. - Resolution: Fixed > some tables in the new UI are missing default sort indicators > --

[jira] Resolved: (QPID-2073) reduce the minimum vertical footprint of the QueueOperations tab to better suit use with a 1024x768 screen resolution

[ https://issues.apache.org/jira/browse/QPID-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2073. - Resolution: Fixed > reduce the minimum vertical footprint of the QueueOperations tab to better >

Re: New messaging API - base on AMQP 1.0, or on Java JMS?

Gordon Sim wrote: On 09/15/2009 10:42 PM, Andrew Wright wrote: The main need we've run across for a lower level java api comes from performing administrative functions from code - a standardised admin api would certainly be useful (cf. MQSeries PCF). I'm not sure there would be much benefit from

[jira] Updated: (QPID-942) Introduce client flow control and broker overflow protection

[ https://issues.apache.org/jira/browse/QPID-942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey updated QPID-942: - Fix Version/s: 0.6 > Introduce client flow control and broker overflow protection > ---

[jira] Commented: (QPID-942) Introduce client flow control and broker overflow protection

[ https://issues.apache.org/jira/browse/QPID-942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755961#action_12755961 ] Rob Godfrey commented on QPID-942: -- I am working on a patch to implement channel level flow

[jira] Assigned: (QPID-942) Introduce client flow control and broker overflow protection

[ https://issues.apache.org/jira/browse/QPID-942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey reassigned QPID-942: Assignee: Rob Godfrey > Introduce client flow control and broker overflow protection > --

[jira] Created: (QPID-2106) Broker viciously closes connections when a client is asked to close a channel

Broker viciously closes connections when a client is asked to close a channel - Key: QPID-2106 URL: https://issues.apache.org/jira/browse/QPID-2106 Project: Qpid Iss

[jira] Created: (QPID-2105) Client should use NetworkDriver/ProtocolEngine interfaces

Client should use NetworkDriver/ProtocolEngine interfaces - Key: QPID-2105 URL: https://issues.apache.org/jira/browse/QPID-2105 Project: Qpid Issue Type: Improvement Component

Re: New messaging API - base on AMQP 1.0, or on Java JMS?

On 09/15/2009 10:42 PM, Andrew Wright wrote: The main need we've run across for a lower level java api comes from performing administrative functions from code - a standardised admin api would certainly be useful (cf. MQSeries PCF). I'm not sure there would be much benefit from shoehorning this i

[jira] Commented: (QPID-2104) Improved LVQ implementation

[ https://issues.apache.org/jira/browse/QPID-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755921#action_12755921 ] Gordon Sim commented on QPID-2104: -- >From Andrew Wright: "The only other use case I can ima

[jira] Created: (QPID-2104) Improved LVQ implementation

Improved LVQ implementation --- Key: QPID-2104 URL: https://issues.apache.org/jira/browse/QPID-2104 Project: Qpid Issue Type: Improvement Components: C++ Broker Affects Versions: 0.5 Reporter