date:20120215

 Neither properties, no object type is taken into consideration by ACL plugin 
when ALL is specified for the operation
-

 Key: QPID-3843
 URL: https://issues.apache.org/jira/browse/QPID-3843
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: 0.15
Reporter: Alex Rudyy
 Fix For: 0.15


ACL plugin fails to interpret correctly a rule specified like ACL action 
username ALL ALL properties

Neither , no object type is taken into consideration when ALL specified for the 
operation.

For example, the following rule returns ALLOWED for any component

ACL ALLOW-LOG server ALL METHOD component=MyComponent

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Updated] (QPID-3843) Neither properties, no object type is taken into consideration by ACL plugin when ALL is specified for the operation


 [ 
https://issues.apache.org/jira/browse/QPID-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy updated QPID-3843:
-

Description: 
ACL plugin fails to interpret correctly a rule specified like ACL action 
username ALL ALL properties

Neither properties, no object type is taken into consideration when ALL 
specified for the operation.

For example, the following rule returns ALLOWED for any component

ACL ALLOW-LOG server ALL METHOD component=MyComponent

  was:
ACL plugin fails to interpret correctly a rule specified like ACL action 
username ALL ALL properties

Neither , no object type is taken into consideration when ALL specified for the 
operation.

For example, the following rule returns ALLOWED for any component

ACL ALLOW-LOG server ALL METHOD component=MyComponent


  Neither properties, no object type is taken into consideration by ACL plugin 
 when ALL is specified for the operation
 -

 Key: QPID-3843
 URL: https://issues.apache.org/jira/browse/QPID-3843
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: 0.15
Reporter: Alex Rudyy
 Fix For: 0.15


 ACL plugin fails to interpret correctly a rule specified like ACL action 
 username ALL ALL properties
 Neither properties, no object type is taken into consideration when ALL 
 specified for the operation.
 For example, the following rule returns ALLOWED for any component
 ACL ALLOW-LOG server ALL METHOD component=MyComponent

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Assigned] (QPID-3843) Neither properties, no object type is taken into consideration by ACL plugin when ALL is specified for the operation


 [ 
https://issues.apache.org/jira/browse/QPID-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy reassigned QPID-3843:


Assignee: Alex Rudyy

  Neither properties, no object type is taken into consideration by ACL plugin 
 when ALL is specified for the operation
 -

 Key: QPID-3843
 URL: https://issues.apache.org/jira/browse/QPID-3843
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: 0.15
Reporter: Alex Rudyy
Assignee: Alex Rudyy
 Fix For: 0.15

 Attachments: 
 0001-QPID-3843-Fix-VCL-rule-evaluation-for-ALL-operation.patch


 ACL plugin fails to interpret correctly a rule specified like ACL action 
 username ALL ALL properties
 Neither properties, no object type is taken into consideration when ALL 
 specified for the operation.
 For example, the following rule returns ALLOWED for any component
 ACL ALLOW-LOG server ALL METHOD component=MyComponent

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Updated] (QPID-3843) Neither properties, no object type is taken into consideration by ACL plugin when ALL is specified for the operation


 [ 
https://issues.apache.org/jira/browse/QPID-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy updated QPID-3843:
-

Attachment: 0001-QPID-3843-Fix-VCL-rule-evaluation-for-ALL-operation.patch

Patch with a fix is attached

  Neither properties, no object type is taken into consideration by ACL plugin 
 when ALL is specified for the operation
 -

 Key: QPID-3843
 URL: https://issues.apache.org/jira/browse/QPID-3843
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: 0.15
Reporter: Alex Rudyy
Assignee: Alex Rudyy
 Fix For: 0.15

 Attachments: 
 0001-QPID-3843-Fix-VCL-rule-evaluation-for-ALL-operation.patch


 ACL plugin fails to interpret correctly a rule specified like ACL action 
 username ALL ALL properties
 Neither properties, no object type is taken into consideration when ALL 
 specified for the operation.
 For example, the following rule returns ALLOWED for any component
 ACL ALLOW-LOG server ALL METHOD component=MyComponent

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Assigned] (QPID-3843) Neither properties, no object type is taken into consideration by ACL plugin when ALL is specified for the operation


 [ 
https://issues.apache.org/jira/browse/QPID-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy reassigned QPID-3843:


Assignee: Robbie Gemmell  (was: Alex Rudyy)

Hi Robbie, 

Could you please review and commit the patch with a fix?

  Neither properties, no object type is taken into consideration by ACL plugin 
 when ALL is specified for the operation
 -

 Key: QPID-3843
 URL: https://issues.apache.org/jira/browse/QPID-3843
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: 0.15
Reporter: Alex Rudyy
Assignee: Robbie Gemmell
 Fix For: 0.15

 Attachments: 
 0001-QPID-3843-Fix-VCL-rule-evaluation-for-ALL-operation.patch


 ACL plugin fails to interpret correctly a rule specified like ACL action 
 username ALL ALL properties
 Neither properties, no object type is taken into consideration when ALL 
 specified for the operation.
 For example, the following rule returns ALLOWED for any component
 ACL ALLOW-LOG server ALL METHOD component=MyComponent

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Created] (QPID-3844) Management ACL lacks the ability to perform queryMBean operation for non-admin users

Management ACL lacks the ability to perform queryMBean operation for non-admin 
users


 Key: QPID-3844
 URL: https://issues.apache.org/jira/browse/QPID-3844
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: 0.15
Reporter: Alex Rudyy
 Fix For: 0.15




Existing user accounts with limited rights (non admin uses) cannot login into 
management console due to error: Permission denied: Access queryMBeans.

For example, ACL for the guest account can be configured like following

#Allow 'guest' to perform read operations on the Serverinformation mbean and 
view logger levels
ACL ALLOW-LOG guest ACCESS METHOD component=ServerInformation
ACL ALLOW-LOG guest ACCESS METHOD component=LoggingManagement 
name=viewEffectiveRuntimeLoggerLevels

but guest user still is not be able to login because current implementation 
does not allow invocation of queryMBeans operation for non-admin accounts.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Created] (QPID-3845) User with read access rights on ShutdownMBean is allowed to shutdown broker via JMX

User with read access rights on ShutdownMBean is allowed to shutdown broker via 
JMX
---

 Key: QPID-3845
 URL: https://issues.apache.org/jira/browse/QPID-3845
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: 0.15
Reporter: Alex Rudyy
Priority: Minor
 Fix For: 0.15


User with read (access) rights on ShutdownMBean is allowed to shutdown broker 
via JMX

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Assigned] (QPID-3845) User with read access rights on ShutdownMBean is allowed to shutdown broker via JMX


 [ 
https://issues.apache.org/jira/browse/QPID-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy reassigned QPID-3845:


Assignee: Alex Rudyy

 User with read access rights on ShutdownMBean is allowed to shutdown broker 
 via JMX
 ---

 Key: QPID-3845
 URL: https://issues.apache.org/jira/browse/QPID-3845
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: 0.15
Reporter: Alex Rudyy
Assignee: Alex Rudyy
Priority: Minor
 Fix For: 0.15

 Attachments: 
 0001-QPID-3845-Change-impact-attribute-for-ShutdownMBean-.patch


 User with read (access) rights on ShutdownMBean is allowed to shutdown broker 
 via JMX

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Assigned] (QPID-3845) User with read access rights on ShutdownMBean is allowed to shutdown broker via JMX


 [ 
https://issues.apache.org/jira/browse/QPID-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy reassigned QPID-3845:


Assignee: Robbie Gemmell  (was: Alex Rudyy)

Robbie, 

Could you please review and commit the patch?

 User with read access rights on ShutdownMBean is allowed to shutdown broker 
 via JMX
 ---

 Key: QPID-3845
 URL: https://issues.apache.org/jira/browse/QPID-3845
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: 0.15
Reporter: Alex Rudyy
Assignee: Robbie Gemmell
Priority: Minor
 Fix For: 0.15

 Attachments: 
 0001-QPID-3845-Change-impact-attribute-for-ShutdownMBean-.patch


 User with read (access) rights on ShutdownMBean is allowed to shutdown broker 
 via JMX

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Updated] (QPID-3845) User with read access rights on ShutdownMBean is allowed to shutdown broker via JMX


 [ 
https://issues.apache.org/jira/browse/QPID-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy updated QPID-3845:
-

Attachment: 0001-QPID-3845-Change-impact-attribute-for-ShutdownMBean-.patch

Patch with the fix is attached

 User with read access rights on ShutdownMBean is allowed to shutdown broker 
 via JMX
 ---

 Key: QPID-3845
 URL: https://issues.apache.org/jira/browse/QPID-3845
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: 0.15
Reporter: Alex Rudyy
Assignee: Alex Rudyy
Priority: Minor
 Fix For: 0.15

 Attachments: 
 0001-QPID-3845-Change-impact-attribute-for-ShutdownMBean-.patch


 User with read (access) rights on ShutdownMBean is allowed to shutdown broker 
 via JMX

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Updated] (QPID-3845) User with read access rights on ShutdownMBean is allowed to shutdown broker via JMX


 [ 
https://issues.apache.org/jira/browse/QPID-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy updated QPID-3845:
-

Status: Ready To Review  (was: In Progress)

 User with read access rights on ShutdownMBean is allowed to shutdown broker 
 via JMX
 ---

 Key: QPID-3845
 URL: https://issues.apache.org/jira/browse/QPID-3845
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: 0.15
Reporter: Alex Rudyy
Assignee: Alex Rudyy
Priority: Minor
 Fix For: 0.15

 Attachments: 
 0001-QPID-3845-Change-impact-attribute-for-ShutdownMBean-.patch


 User with read (access) rights on ShutdownMBean is allowed to shutdown broker 
 via JMX

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Created] (QPID-3846) Management console adds empty nodes (connections, exchanges and queue) for the users without access rights on virtual hosts

Management console adds empty nodes (connections, exchanges and queue)  
for the users without access rights on virtual hosts
--

 Key: QPID-3846
 URL: https://issues.apache.org/jira/browse/QPID-3846
 Project: Qpid
  Issue Type: Bug
  Components: Java Management : JMX Console
Affects Versions: 0.15
Reporter: Alex Rudyy
 Fix For: 0.15


Management console adds empty nodes (connections, exchanges and queue)  
for the users without access rights on virtual hosts

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Assigned] (QPID-3846) Management console adds empty nodes (connections, exchanges and queue) for the users without access rights on virtual hosts


 [ 
https://issues.apache.org/jira/browse/QPID-3846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy reassigned QPID-3846:


Assignee: Alex Rudyy

 Management console adds empty nodes (connections, exchanges and queue)  
 for the users without access rights on virtual hosts
 --

 Key: QPID-3846
 URL: https://issues.apache.org/jira/browse/QPID-3846
 Project: Qpid
  Issue Type: Bug
  Components: Java Management : JMX Console
Affects Versions: 0.15
Reporter: Alex Rudyy
Assignee: Alex Rudyy
 Fix For: 0.15

 Attachments: 
 0001-QPID-3846-Stop-adding-empty-nodes-for-connections-ex.patch


 Management console adds empty nodes (connections, exchanges and queue)  
 for the users without access rights on virtual hosts

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Updated] (QPID-3846) Management console adds empty nodes (connections, exchanges and queue) for the users without access rights on virtual hosts


 [ 
https://issues.apache.org/jira/browse/QPID-3846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy updated QPID-3846:
-

Status: Ready To Review  (was: In Progress)

 Management console adds empty nodes (connections, exchanges and queue)  
 for the users without access rights on virtual hosts
 --

 Key: QPID-3846
 URL: https://issues.apache.org/jira/browse/QPID-3846
 Project: Qpid
  Issue Type: Bug
  Components: Java Management : JMX Console
Affects Versions: 0.15
Reporter: Alex Rudyy
Assignee: Alex Rudyy
 Fix For: 0.15

 Attachments: 
 0001-QPID-3846-Stop-adding-empty-nodes-for-connections-ex.patch


 Management console adds empty nodes (connections, exchanges and queue)  
 for the users without access rights on virtual hosts

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Updated] (QPID-3846) Management console adds empty nodes (connections, exchanges and queue) for the users without access rights on virtual hosts


 [ 
https://issues.apache.org/jira/browse/QPID-3846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy updated QPID-3846:
-

Attachment: 0001-QPID-3846-Stop-adding-empty-nodes-for-connections-ex.patch

Patch with the fix is added

 Management console adds empty nodes (connections, exchanges and queue)  
 for the users without access rights on virtual hosts
 --

 Key: QPID-3846
 URL: https://issues.apache.org/jira/browse/QPID-3846
 Project: Qpid
  Issue Type: Bug
  Components: Java Management : JMX Console
Affects Versions: 0.15
Reporter: Alex Rudyy
Assignee: Alex Rudyy
 Fix For: 0.15

 Attachments: 
 0001-QPID-3846-Stop-adding-empty-nodes-for-connections-ex.patch


 Management console adds empty nodes (connections, exchanges and queue)  
 for the users without access rights on virtual hosts

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Assigned] (QPID-3846) Management console adds empty nodes (connections, exchanges and queue) for the users without access rights on virtual hosts


 [ 
https://issues.apache.org/jira/browse/QPID-3846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy reassigned QPID-3846:


Assignee: Robbie Gemmell  (was: Alex Rudyy)

Robbie,

Could you please review and commit the patch attached?

 Management console adds empty nodes (connections, exchanges and queue)  
 for the users without access rights on virtual hosts
 --

 Key: QPID-3846
 URL: https://issues.apache.org/jira/browse/QPID-3846
 Project: Qpid
  Issue Type: Bug
  Components: Java Management : JMX Console
Affects Versions: 0.15
Reporter: Alex Rudyy
Assignee: Robbie Gemmell
 Fix For: 0.15

 Attachments: 
 0001-QPID-3846-Stop-adding-empty-nodes-for-connections-ex.patch


 Management console adds empty nodes (connections, exchanges and queue)  
 for the users without access rights on virtual hosts

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Reopened] (QPID-3840) Automate testing of qpid-passwd script

2012-02-15 Thread Philip Harvey (Reopened) (JIRA)


 [ 
https://issues.apache.org/jira/browse/QPID-3840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Philip Harvey reopened QPID-3840:
-


 Automate testing of qpid-passwd script
 --

 Key: QPID-3840
 URL: https://issues.apache.org/jira/browse/QPID-3840
 Project: Qpid
  Issue Type: Improvement
  Components: Java Broker, Java Tools
Affects Versions: 0.14
Reporter: Philip Harvey
Assignee: Keith Wall
Priority: Trivial
 Fix For: 0.15

 Attachments: 
 0001-QPID-3840-added-automated-tests-for-qpid-passwd-scri.patch


 The qpid-passwd script and its underlying Java class should be automatically 
 tested.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Updated] (QPID-3840) Automate testing of qpid-passwd script

2012-02-15 Thread Philip Harvey (Updated) (JIRA)


 [ 
https://issues.apache.org/jira/browse/QPID-3840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Philip Harvey updated QPID-3840:


Attachment: 0001-QPID-3840-corrected-qpid-passwd-and-qpid-run-to-hand.patch

corrected qpid-passwd and qpid-run to handle paths with spaces in them. 
Modified unit test to capture stderr to aid diagnosis of failures.

 Automate testing of qpid-passwd script
 --

 Key: QPID-3840
 URL: https://issues.apache.org/jira/browse/QPID-3840
 Project: Qpid
  Issue Type: Improvement
  Components: Java Broker, Java Tools
Affects Versions: 0.14
Reporter: Philip Harvey
Assignee: Keith Wall
Priority: Trivial
 Fix For: 0.15

 Attachments: 
 0001-QPID-3840-added-automated-tests-for-qpid-passwd-scri.patch, 
 0001-QPID-3840-corrected-qpid-passwd-and-qpid-run-to-hand.patch


 The qpid-passwd script and its underlying Java class should be automatically 
 tested.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Closed] (QPID-3840) Automate testing of qpid-passwd script

2012-02-15 Thread Keith Wall (Closed) (JIRA)


 [ 
https://issues.apache.org/jira/browse/QPID-3840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Keith Wall closed QPID-3840.


Resolution: Fixed

Patch applied.

 Automate testing of qpid-passwd script
 --

 Key: QPID-3840
 URL: https://issues.apache.org/jira/browse/QPID-3840
 Project: Qpid
  Issue Type: Improvement
  Components: Java Broker, Java Tools
Affects Versions: 0.14
Reporter: Philip Harvey
Assignee: Keith Wall
Priority: Trivial
 Fix For: 0.15

 Attachments: 
 0001-QPID-3840-added-automated-tests-for-qpid-passwd-scri.patch, 
 0001-QPID-3840-corrected-qpid-passwd-and-qpid-run-to-hand.patch


 The qpid-passwd script and its underlying Java class should be automatically 
 tested.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

qpidmc AIX

2012-02-15 Thread gerard

I would like to use qpidmc on AIX 6. Is there an install package for this? Is
it necessaryu to build from source?
thanks

--
View this message in context: 
http://apache-qpid-developers.2158895.n2.nabble.com/qpidmc-AIX-tp7287427p7287427.html
Sent from the Apache Qpid developers mailing list archive at Nabble.com.

-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Assigned] (QPID-3844) Management ACL lacks the ability to perform queryMBean operation for non-admin users


 [ 
https://issues.apache.org/jira/browse/QPID-3844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy reassigned QPID-3844:


Assignee: Alex Rudyy

 Management ACL lacks the ability to perform queryMBean operation for 
 non-admin users
 

 Key: QPID-3844
 URL: https://issues.apache.org/jira/browse/QPID-3844
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: 0.15
Reporter: Alex Rudyy
Assignee: Alex Rudyy
 Fix For: 0.15


 Existing user accounts with limited rights (non admin uses) cannot login into 
 management console due to error: Permission denied: Access queryMBeans.
 For example, ACL for the guest account can be configured like following
 #Allow 'guest' to perform read operations on the Serverinformation mbean and 
 view logger levels
 ACL ALLOW-LOG guest ACCESS METHOD component=ServerInformation
 ACL ALLOW-LOG guest ACCESS METHOD component=LoggingManagement 
 name=viewEffectiveRuntimeLoggerLevels
 but guest user still is not be able to login because current implementation 
 does not allow invocation of queryMBeans operation for non-admin accounts.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Assigned] (QPID-3844) Management ACL lacks the ability to perform queryMBean operation for non-admin users


 [ 
https://issues.apache.org/jira/browse/QPID-3844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy reassigned QPID-3844:


Assignee: Robbie Gemmell  (was: Alex Rudyy)

Robbie,

Could you please review and commit the patch attached?

 Management ACL lacks the ability to perform queryMBean operation for 
 non-admin users
 

 Key: QPID-3844
 URL: https://issues.apache.org/jira/browse/QPID-3844
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: 0.15
Reporter: Alex Rudyy
Assignee: Robbie Gemmell
 Fix For: 0.15

 Attachments: 
 0001-QPID-3844-Operation-queryMBeans-does-not-require-aut.patch


 Existing user accounts with limited rights (non admin uses) cannot login into 
 management console due to error: Permission denied: Access queryMBeans.
 For example, ACL for the guest account can be configured like following
 #Allow 'guest' to perform read operations on the Serverinformation mbean and 
 view logger levels
 ACL ALLOW-LOG guest ACCESS METHOD component=ServerInformation
 ACL ALLOW-LOG guest ACCESS METHOD component=LoggingManagement 
 name=viewEffectiveRuntimeLoggerLevels
 but guest user still is not be able to login because current implementation 
 does not allow invocation of queryMBeans operation for non-admin accounts.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Updated] (QPID-3844) Management ACL lacks the ability to perform queryMBean operation for non-admin users


 [ 
https://issues.apache.org/jira/browse/QPID-3844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy updated QPID-3844:
-

Attachment: 0001-QPID-3844-Operation-queryMBeans-does-not-require-aut.patch

Attached a patch with a fix.

 Management ACL lacks the ability to perform queryMBean operation for 
 non-admin users
 

 Key: QPID-3844
 URL: https://issues.apache.org/jira/browse/QPID-3844
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: 0.15
Reporter: Alex Rudyy
Assignee: Alex Rudyy
 Fix For: 0.15

 Attachments: 
 0001-QPID-3844-Operation-queryMBeans-does-not-require-aut.patch


 Existing user accounts with limited rights (non admin uses) cannot login into 
 management console due to error: Permission denied: Access queryMBeans.
 For example, ACL for the guest account can be configured like following
 #Allow 'guest' to perform read operations on the Serverinformation mbean and 
 view logger levels
 ACL ALLOW-LOG guest ACCESS METHOD component=ServerInformation
 ACL ALLOW-LOG guest ACCESS METHOD component=LoggingManagement 
 name=viewEffectiveRuntimeLoggerLevels
 but guest user still is not be able to login because current implementation 
 does not allow invocation of queryMBeans operation for non-admin accounts.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Updated] (QPID-3844) Management ACL lacks the ability to perform queryMBean operation for non-admin users


 [ 
https://issues.apache.org/jira/browse/QPID-3844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy updated QPID-3844:
-

Status: Ready To Review  (was: In Progress)

 Management ACL lacks the ability to perform queryMBean operation for 
 non-admin users
 

 Key: QPID-3844
 URL: https://issues.apache.org/jira/browse/QPID-3844
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: 0.15
Reporter: Alex Rudyy
Assignee: Alex Rudyy
 Fix For: 0.15

 Attachments: 
 0001-QPID-3844-Operation-queryMBeans-does-not-require-aut.patch


 Existing user accounts with limited rights (non admin uses) cannot login into 
 management console due to error: Permission denied: Access queryMBeans.
 For example, ACL for the guest account can be configured like following
 #Allow 'guest' to perform read operations on the Serverinformation mbean and 
 view logger levels
 ACL ALLOW-LOG guest ACCESS METHOD component=ServerInformation
 ACL ALLOW-LOG guest ACCESS METHOD component=LoggingManagement 
 name=viewEffectiveRuntimeLoggerLevels
 but guest user still is not be able to login because current implementation 
 does not allow invocation of queryMBeans operation for non-admin accounts.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

RE: qpidmc AIX

2012-02-15 Thread Steve Huston

Hi Gerard,

Qpid C++ hasn't been ported to AIX (yet). Much of the hard work has been
done but there's still a fair bit of work and testing to do yet.

If you'd like to help complete this port, that would be great - I'd be
happy to advise. If you'd rather hire some help to complete this, please
let me know that as well.

In the meantime, you could use the Java version of Qpid on AIX.

Best regards,
-Steve

 -Original Message-
 From: gerard [mailto:gerard.sav...@ncr.com]
 Sent: Wednesday, February 15, 2012 8:16 AM
 To: dev@qpid.apache.org
 Subject: qpidmc  AIX
 
 I would like to use qpidmc on AIX 6. Is there an install package for
this? Is it
 necessaryu to build from source?
 thanks
 
 --
 View this message in context: http://apache-qpid-
 developers.2158895.n2.nabble.com/qpidmc-AIX-tp7287427p7287427.html
 Sent from the Apache Qpid developers mailing list archive at Nabble.com.
 
 -
 Apache Qpid - AMQP Messaging Implementation
 Project:  http://qpid.apache.org
 Use/Interact: mailto:dev-subscr...@qpid.apache.org


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Updated] (QPID-3844) Management ACL lacks the ability to perform queryMBean operation for non-admin users


 [ 
https://issues.apache.org/jira/browse/QPID-3844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy updated QPID-3844:
-

Attachment: 0001-QPID-3844-Operation-queryMBeans-does-not-require-aut.patch

 Management ACL lacks the ability to perform queryMBean operation for 
 non-admin users
 

 Key: QPID-3844
 URL: https://issues.apache.org/jira/browse/QPID-3844
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: 0.15
Reporter: Alex Rudyy
Assignee: Robbie Gemmell
 Fix For: 0.15

 Attachments: 
 0001-QPID-3844-Operation-queryMBeans-does-not-require-aut.patch


 Existing user accounts with limited rights (non admin uses) cannot login into 
 management console due to error: Permission denied: Access queryMBeans.
 For example, ACL for the guest account can be configured like following
 #Allow 'guest' to perform read operations on the Serverinformation mbean and 
 view logger levels
 ACL ALLOW-LOG guest ACCESS METHOD component=ServerInformation
 ACL ALLOW-LOG guest ACCESS METHOD component=LoggingManagement 
 name=viewEffectiveRuntimeLoggerLevels
 but guest user still is not be able to login because current implementation 
 does not allow invocation of queryMBeans operation for non-admin accounts.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Updated] (QPID-3843) Neither properties, no object type is taken into consideration by ACL plugin when ALL is specified for the operation


 [ 
https://issues.apache.org/jira/browse/QPID-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy updated QPID-3843:
-

Attachment: 0001-QPID-3843-Fix-VCL-rule-evaluation-for-ALL-operation.patch

  Neither properties, no object type is taken into consideration by ACL plugin 
 when ALL is specified for the operation
 -

 Key: QPID-3843
 URL: https://issues.apache.org/jira/browse/QPID-3843
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: 0.15
Reporter: Alex Rudyy
Assignee: Robbie Gemmell
 Fix For: 0.15

 Attachments: 
 0001-QPID-3843-Fix-VCL-rule-evaluation-for-ALL-operation.patch


 ACL plugin fails to interpret correctly a rule specified like ACL action 
 username ALL ALL properties
 Neither properties, no object type is taken into consideration when ALL 
 specified for the operation.
 For example, the following rule returns ALLOWED for any component
 ACL ALLOW-LOG server ALL METHOD component=MyComponent

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Updated] (QPID-3843) Neither properties, no object type is taken into consideration by ACL plugin when ALL is specified for the operation


 [ 
https://issues.apache.org/jira/browse/QPID-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy updated QPID-3843:
-

Attachment: (was: 
0001-QPID-3843-Fix-VCL-rule-evaluation-for-ALL-operation.patch)

  Neither properties, no object type is taken into consideration by ACL plugin 
 when ALL is specified for the operation
 -

 Key: QPID-3843
 URL: https://issues.apache.org/jira/browse/QPID-3843
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: 0.15
Reporter: Alex Rudyy
Assignee: Robbie Gemmell
 Fix For: 0.15

 Attachments: 
 0001-QPID-3843-Fix-VCL-rule-evaluation-for-ALL-operation.patch


 ACL plugin fails to interpret correctly a rule specified like ACL action 
 username ALL ALL properties
 Neither properties, no object type is taken into consideration when ALL 
 specified for the operation.
 For example, the following rule returns ALLOWED for any component
 ACL ALLOW-LOG server ALL METHOD component=MyComponent

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Updated] (QPID-3845) User with read access rights on ShutdownMBean is allowed to shutdown broker via JMX


 [ 
https://issues.apache.org/jira/browse/QPID-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy updated QPID-3845:
-

Attachment: (was: 
0001-QPID-3845-Change-impact-attribute-for-ShutdownMBean-.patch)

 User with read access rights on ShutdownMBean is allowed to shutdown broker 
 via JMX
 ---

 Key: QPID-3845
 URL: https://issues.apache.org/jira/browse/QPID-3845
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: 0.15
Reporter: Alex Rudyy
Assignee: Robbie Gemmell
Priority: Minor
 Fix For: 0.15


 User with read (access) rights on ShutdownMBean is allowed to shutdown broker 
 via JMX

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Updated] (QPID-3844) Management ACL lacks the ability to perform queryMBean operation for non-admin users


 [ 
https://issues.apache.org/jira/browse/QPID-3844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy updated QPID-3844:
-

Attachment: (was: 
0001-QPID-3844-Operation-queryMBeans-does-not-require-aut.patch)

 Management ACL lacks the ability to perform queryMBean operation for 
 non-admin users
 

 Key: QPID-3844
 URL: https://issues.apache.org/jira/browse/QPID-3844
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: 0.15
Reporter: Alex Rudyy
Assignee: Robbie Gemmell
 Fix For: 0.15

 Attachments: 
 0001-QPID-3844-Operation-queryMBeans-does-not-require-aut.patch


 Existing user accounts with limited rights (non admin uses) cannot login into 
 management console due to error: Permission denied: Access queryMBeans.
 For example, ACL for the guest account can be configured like following
 #Allow 'guest' to perform read operations on the Serverinformation mbean and 
 view logger levels
 ACL ALLOW-LOG guest ACCESS METHOD component=ServerInformation
 ACL ALLOW-LOG guest ACCESS METHOD component=LoggingManagement 
 name=viewEffectiveRuntimeLoggerLevels
 but guest user still is not be able to login because current implementation 
 does not allow invocation of queryMBeans operation for non-admin accounts.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Updated] (QPID-3845) User with read access rights on ShutdownMBean is allowed to shutdown broker via JMX


 [ 
https://issues.apache.org/jira/browse/QPID-3845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy updated QPID-3845:
-

Attachment: 0001-QPID-3845-Change-impact-attribute-for-ShutdownMBean-.patch

 User with read access rights on ShutdownMBean is allowed to shutdown broker 
 via JMX
 ---

 Key: QPID-3845
 URL: https://issues.apache.org/jira/browse/QPID-3845
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: 0.15
Reporter: Alex Rudyy
Assignee: Robbie Gemmell
Priority: Minor
 Fix For: 0.15

 Attachments: 
 0001-QPID-3845-Change-impact-attribute-for-ShutdownMBean-.patch


 User with read (access) rights on ShutdownMBean is allowed to shutdown broker 
 via JMX

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Updated] (QPID-3846) Management console adds empty nodes (connections, exchanges and queue) for the users without access rights on virtual hosts


 [ 
https://issues.apache.org/jira/browse/QPID-3846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy updated QPID-3846:
-

Attachment: (was: 
0001-QPID-3846-Stop-adding-empty-nodes-for-connections-ex.patch)

 Management console adds empty nodes (connections, exchanges and queue)  
 for the users without access rights on virtual hosts
 --

 Key: QPID-3846
 URL: https://issues.apache.org/jira/browse/QPID-3846
 Project: Qpid
  Issue Type: Bug
  Components: Java Management : JMX Console
Affects Versions: 0.15
Reporter: Alex Rudyy
Assignee: Robbie Gemmell
 Fix For: 0.15

 Attachments: 
 0001-QPID-3846-Stop-adding-empty-nodes-for-connections-ex.patch


 Management console adds empty nodes (connections, exchanges and queue)  
 for the users without access rights on virtual hosts

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Updated] (QPID-3846) Management console adds empty nodes (connections, exchanges and queue) for the users without access rights on virtual hosts


 [ 
https://issues.apache.org/jira/browse/QPID-3846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy updated QPID-3846:
-

Attachment: 0001-QPID-3846-Stop-adding-empty-nodes-for-connections-ex.patch

 Management console adds empty nodes (connections, exchanges and queue)  
 for the users without access rights on virtual hosts
 --

 Key: QPID-3846
 URL: https://issues.apache.org/jira/browse/QPID-3846
 Project: Qpid
  Issue Type: Bug
  Components: Java Management : JMX Console
Affects Versions: 0.15
Reporter: Alex Rudyy
Assignee: Robbie Gemmell
 Fix For: 0.15

 Attachments: 
 0001-QPID-3846-Stop-adding-empty-nodes-for-connections-ex.patch


 Management console adds empty nodes (connections, exchanges and queue)  
 for the users without access rights on virtual hosts

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

Re: qpidmc AIX

2012-02-15 Thread Robbie Gemmell

Hi Gerard,

From the title I am going to assume you mean the JMX management
console for the Java broker? We dont currently have an AIX package for
this, as there has never been a demand for it given most users would
tend to run the console from the local desktops.

In theory it should be possible to construct such a package as there
appears to be an eclipse release for AIX using Motif for the version
of Eclipse RCP the console is built around, which could be used as a
reference point, however we dont have access to an AIX box we could
try this on. It isnt just a matter of compiling the current console
plugin code (which is itself platform independant) on AIX however,
there are platform-dependant binary dependencies and configuration
files required for the Eclipse RCP basis of the console that need to
be layed out/configured correctly (e.g the solaris and Mac OS X
variants differ somehwat from the linux and windows verions for this
reason).

Regards,
Robbie

On 15 February 2012 13:15, gerard gerard.sav...@ncr.com wrote:
 I would like to use qpidmc on AIX 6. Is there an install package for this? Is
 it necessaryu to build from source?
 thanks

 --
 View this message in context: 
 http://apache-qpid-developers.2158895.n2.nabble.com/qpidmc-AIX-tp7287427p7287427.html
 Sent from the Apache Qpid developers mailing list archive at Nabble.com.

 -
 Apache Qpid - AMQP Messaging Implementation
 Project:      http://qpid.apache.org
 Use/Interact: mailto:dev-subscr...@qpid.apache.org


-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Resolved] (QPID-3841) Improve batching of writes for outbound messages.

2012-02-15 Thread Ken Giusti (Resolved) (JIRA)


 [ 
https://issues.apache.org/jira/browse/QPID-3841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ken Giusti resolved QPID-3841.
--

Resolution: Fixed

 Improve batching of writes for outbound messages.
 -

 Key: QPID-3841
 URL: https://issues.apache.org/jira/browse/QPID-3841
 Project: Qpid
  Issue Type: Improvement
  Components: C++ Broker
Affects Versions: 0.15
Reporter: Ken Giusti
Assignee: Ken Giusti
Priority: Minor
 Fix For: 0.15


 A patch created by Gordon Sim will allow the connection to batch up outbound 
 messages, resulting in less calls to the socket's write method (as more data 
 is passed with each write).
 This results in a small performance improvement.  For example, given a broker 
 with a single queue (flow control disabled), qpid-send filling it and 
 qpid-receive draining it simultaineously with 300 byte messages:
 Pre-patch:
 qpid-send=77581 msg/sec
 qpid-receive= 77345 msg/sec
 Post-patch:
 qpid-send=84931 msg/sec
 qpid-receive= 84789 msg/sec

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Created] (QPID-3847) Object IDs (in console.py) which are learned via qmfv1 publish are not properly regenerated when they contain recursive references

2012-02-15 Thread Ted Ross (Created) (JIRA)

Object IDs (in console.py) which are learned via qmfv1 publish are not properly 
regenerated when they contain recursive references
--

 Key: QPID-3847
 URL: https://issues.apache.org/jira/browse/QPID-3847
 Project: Qpid
  Issue Type: Bug
  Components: Qpid Managment Framework
Affects Versions: 0.14
Reporter: Ted Ross
Assignee: Ted Ross
Priority: Minor
 Fix For: 0.15


Calling acl:reloadACLFile from qpid-tool does not work properly when the broker 
is using both v1 and v2 qmf publication.

Note that this problem will disappear when qmfv1 is deprecated.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Resolved] (QPID-3842) Java Broker should report platform and memory size on startup


 [ 
https://issues.apache.org/jira/browse/QPID-3842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell resolved QPID-3842.
--

Resolution: Fixed

Looks good to me.

 Java Broker should report platform and memory size on startup
 -

 Key: QPID-3842
 URL: https://issues.apache.org/jira/browse/QPID-3842
 Project: Qpid
  Issue Type: Improvement
  Components: Java Broker
Affects Versions: 0.15
Reporter: Keith Wall
Assignee: Robbie Gemmell
 Fix For: 0.15


 It would be useful if the Java Broker reported its platform (Java version and 
 OS) and maximum memory size on startup.   The existing operational log 
 mechanism could be easily utilised to achieve this.   This information would 
 be useful in a support context and would aid faster problem resolution.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Resolved] (QPID-3847) Object IDs (in console.py) which are learned via qmfv1 publish are not properly regenerated when they contain recursive references

2012-02-15 Thread Ted Ross (Resolved) (JIRA)


 [ 
https://issues.apache.org/jira/browse/QPID-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ted Ross resolved QPID-3847.


Resolution: Fixed

 Object IDs (in console.py) which are learned via qmfv1 publish are not 
 properly regenerated when they contain recursive references
 --

 Key: QPID-3847
 URL: https://issues.apache.org/jira/browse/QPID-3847
 Project: Qpid
  Issue Type: Bug
  Components: Qpid Managment Framework
Affects Versions: 0.14
Reporter: Ted Ross
Assignee: Ted Ross
Priority: Minor
 Fix For: 0.15


 Calling acl:reloadACLFile from qpid-tool does not work properly when the 
 broker is using both v1 and v2 qmf publication.
 Note that this problem will disappear when qmfv1 is deprecated.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Created] (QPID-3848) [Java broker] relax type checking during passive exchange-declares to allow null/empty type values for consistency with the C++ broker/client

2012-02-15 Thread Robbie Gemmell (Created) (JIRA)

[Java broker] relax type checking during passive exchange-declares to allow 
null/empty type values for consistency with the C++ broker/client
-

 Key: QPID-3848
 URL: https://issues.apache.org/jira/browse/QPID-3848
 Project: Qpid
  Issue Type: Improvement
  Components: Java Broker
Reporter: Robbie Gemmell
Assignee: Robbie Gemmell
 Fix For: 0.15


Relax type checking during passive exchange-declares to allow null/empty type 
values for consistency with the C++ broker/client. This will resolve some 
interoperability issues when using the C++ client (swig wrapped or not) with 
the Java broker, e.g this thread from the user list: 
http://mail-archives.apache.org/mod_mbox/qpid-users/201202.mbox/%3CCAAiPYj2_my7j6ox8fo5CoiU2DnK0G3YDsGCfT4RP_GWz9e2fpQ%40mail.gmail.com%3E

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Resolved] (QPID-2292) the Message class is missing some properties, e.g. the redelivered flag


 [ 
https://issues.apache.org/jira/browse/QPID-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell resolved QPID-2292.
--

Resolution: Fixed

Resolving this issue, it has work done to resolve it from over 2 years ago.

 the Message class is missing some properties, e.g. the redelivered flag
 ---

 Key: QPID-2292
 URL: https://issues.apache.org/jira/browse/QPID-2292
 Project: Qpid
  Issue Type: Bug
  Components: Python Client
Affects Versions: 0.6
Reporter: Rafael H. Schloming
Assignee: Rafael H. Schloming
 Fix For: 0.6




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Resolved] (QPID-2285) doc generation picks up installed package instead of source package


 [ 
https://issues.apache.org/jira/browse/QPID-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell resolved QPID-2285.
--

Resolution: Fixed

Resolving this issue, it has work done to resolve it from over 2 years ago.

 doc generation picks up installed package instead of source package
 ---

 Key: QPID-2285
 URL: https://issues.apache.org/jira/browse/QPID-2285
 Project: Qpid
  Issue Type: Bug
  Components: Python Client
Affects Versions: 0.6
Reporter: Rafael H. Schloming
Assignee: Rafael H. Schloming
 Fix For: 0.6


 The doc generation in the python Makefile will pick up the installed package 
 instead of the package from the source tree. This can result in the wrong 
 documentation being generated if there is an installed version of the python 
 client present.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Resolved] (QPID-1956) FailoverExchangeMethod getNextBrokerDetails() loops infinitely after a total cluster failure or if the inital connect node is down


 [ 
https://issues.apache.org/jira/browse/QPID-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell resolved QPID-1956.
--

Resolution: Fixed

 FailoverExchangeMethod getNextBrokerDetails() loops infinitely after a total 
 cluster failure or if the inital connect node is down
 --

 Key: QPID-1956
 URL: https://issues.apache.org/jira/browse/QPID-1956
 Project: Qpid
  Issue Type: Bug
Affects Versions: M4, 0.5
Reporter: Rajith Attapattu
Assignee: Rajith Attapattu
 Fix For: 0.6


 FailoverExchangeMethod getNextBrokerDetails() loops infinitely after a total 
 cluster failure or if the inital node (given in the URL) is down.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Resolved] (QPID-1935) FailoverTest and QueueBrowser*Test fail on persistent builds


 [ 
https://issues.apache.org/jira/browse/QPID-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell resolved QPID-1935.
--

   Resolution: Won't Fix
Fix Version/s: (was: Future)

Resolving this issue, tests no longer fail/exist.

 FailoverTest and QueueBrowser*Test fail on persistent builds
 

 Key: QPID-1935
 URL: https://issues.apache.org/jira/browse/QPID-1935
 Project: Qpid
  Issue Type: Bug
  Components: Java Tests
Affects Versions: 0.6
Reporter: Aidan Skinner

 The failover and queuebrowser tests do weird things that cause them to fail 
 when run persistently. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Resolved] (QPID-2160) msTool.sh does not cleanly exit with quit command.


 [ 
https://issues.apache.org/jira/browse/QPID-2160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell resolved QPID-2160.
--

Resolution: Won't Fix

Resolving issue, script no longer exists to fix.

 msTool.sh does not cleanly exit with quit command.
 --

 Key: QPID-2160
 URL: https://issues.apache.org/jira/browse/QPID-2160
 Project: Qpid
  Issue Type: Bug
Affects Versions: 0.5, 0.6
Reporter: Martin Ritchie

 When exiting from the msTool.sh the process hangs: 
 bdb$ quit
 ...exiting
 To get the process to fully exit you must press 'ctrl-c' 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Resolved] (QPID-1915) CommitRollbackTest fails when run with bdb store loaded


 [ 
https://issues.apache.org/jira/browse/QPID-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell resolved QPID-1915.
--

Resolution: Fixed

Resolving this issue, test no longer failing.

 CommitRollbackTest fails when run with bdb store loaded
 ---

 Key: QPID-1915
 URL: https://issues.apache.org/jira/browse/QPID-1915
 Project: Qpid
  Issue Type: Bug
Reporter: Aidan Skinner
 Attachments: 
 TEST-org.apache.qpid.test.unit.transacted.CommitRollbackTest.testCommitWhithinOnMessage.out


 TestName: testCommitWhithinOnMessage Duration: 37.755
 Did not received message
 junit.framework.AssertionFailedError: Did not received message
   at 
 org.apache.qpid.test.unit.transacted.CommitRollbackTest.testCommitWhithinOnMessage(CommitRollbackTest.java:526)
   at 
 org.apache.qpid.test.utils.QpidTestCase.runBare(QpidTestCase.java:204)
   at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:249)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Resolved] (QPID-2047) Remove a few IDE complaints


 [ 
https://issues.apache.org/jira/browse/QPID-2047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell resolved QPID-2047.
--

Resolution: Fixed

Resolving this issue, it has work done to resolve it from over 2 years ago, adn 
the component no longer exists.

 Remove a few IDE complaints
 ---

 Key: QPID-2047
 URL: https://issues.apache.org/jira/browse/QPID-2047
 Project: Qpid
  Issue Type: Task
Reporter: Martin Ritchie

 Summary:
 Idea complains about two issues with the command objects.
 1) They call the method ObjectNames in class ObjectNames. This looks like a 
 constructor but it is not.
  - Replace method with better constructor use.
 2) AllObjects returnedObjects removes the generic discriminator.
  - the return should be SetObjetName not just Set

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Resolved] (QPID-3326) Modify ant build scripts to work with Maven


 [ 
https://issues.apache.org/jira/browse/QPID-3326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell resolved QPID-3326.
--

Resolution: Won't Fix

Resolving this issue, the recommended path is for maven users to specify the 
required property in the maven build.

 Modify ant build scripts to work with Maven
 ---

 Key: QPID-3326
 URL: https://issues.apache.org/jira/browse/QPID-3326
 Project: Qpid
  Issue Type: Bug
Reporter: Danushka Menikkumbura
Assignee: Robbie Gemmell
 Attachments: QPID-3326.patch




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Resolved] (QPID-1427) [Java] QueueBrowserDupsOKTest Failure


 [ 
https://issues.apache.org/jira/browse/QPID-1427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell resolved QPID-1427.
--

Resolution: Fixed

Test has been passing for some time, resolving issue.

 [Java] QueueBrowserDupsOKTest Failure
 -

 Key: QPID-1427
 URL: https://issues.apache.org/jira/browse/QPID-1427
 Project: Qpid
  Issue Type: Bug
Affects Versions: M3, M4
Reporter: Marnie McCormack
Assignee: Martin Ritchie
Priority: Minor
 Attachments: 
 TEST-org.apache.qpid.test.client.QueueBrowserClientAckTest.testQueueBrowserMsgsRemainOnQueue.out


 Test: testQueueBrowserMsgsRemainOnQueue
 Class:org.apache.qpid.test.client.QueueBrowserDupsOkTest
   
 junit.framework.AssertionFailedError: Message 0 not retrieved from queue  
 at 
 org.apache.qpid.test.client.QueueBrowserAutoAckTest.validate(QueueBrowserAutoAckTest.java:334)
   
 at 
 org.apache.qpid.test.client.QueueBrowserAutoAckTest.testQueueBrowserMsgsRemainOnQueue(QueueBrowserAutoAckTest.java:379)
   
 at org.apache.qpid.test.utils.QpidTestCase.runBare(QpidTestCase.java:186)  
 at org.apache.qpid.test.utils.QpidTestCase.run(QpidTestCase.java:220)
   

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Commented] (QPID-3461) A SessionException is thrown (instead of a JMSException) when an error occurs during a commit.

2012-02-15 Thread Alex Rudyy (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/QPID-3461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13208870#comment-13208870
 ] 

Alex Rudyy commented on QPID-3461:
--

Hi Rajith,

I might be wrong but I believe that this bug was fixed in 0.14 release.
Are you still able to reproduce it?

 A SessionException is thrown (instead of a JMSException) when an error occurs 
 during a commit.
 --

 Key: QPID-3461
 URL: https://issues.apache.org/jira/browse/QPID-3461
 Project: Qpid
  Issue Type: Bug
  Components: Java Client
Affects Versions: 0.10, 0.12
Reporter: Rajith Attapattu
Assignee: Rajith Attapattu
 Fix For: 0.15

 Attachments: TxFailover.java


 If the broker throws a session level exception, during or just before the 
 client invokes a commit on a transaction, the JMS client throws a 
 SessionException instead of a JMSException.
 This is due to the AMQSession_0_10.java not handing the SessionException.
 (Please note this issue is only present in the 0-10 code path).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Resolved] (QPID-1686) Configuration Update removes ability ot have multiple distinct InVM brokers.


 [ 
https://issues.apache.org/jira/browse/QPID-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell resolved QPID-1686.
--

Resolution: Won't Fix

The ability to use multiple brokers in the same JVM was eventually fully 
removed, a new feature JIRA will be raised if this is to be restored in future.

 Configuration Update removes ability ot have multiple distinct InVM brokers.
 

 Key: QPID-1686
 URL: https://issues.apache.org/jira/browse/QPID-1686
 Project: Qpid
  Issue Type: Bug
Reporter: Martin Ritchie
Priority: Minor

 Before the change creating a new ApplicationRegistry with an id would result 
 in a distinct AR.
 Now the code is littered with ApplicationRegistry.getInstance() calls which 
 returns the AR with id 1.
 This prevents us having InVM brokers with their own config.
 The problem can be removed if the new Configuration objects form a tree so 
 you can do:
 QueueConfig.getVHostConfig().getServerConfig() 
 This could then replace the short cut of using AR.getInstance().

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Resolved] (QPID-53) Create Project Logo


 [ 
https://issues.apache.org/jira/browse/QPID-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell resolved QPID-53.


Resolution: Fixed

Resolving this JIRA, its well over 5 years old and the logo in use has been 
about for just over 3.

 Create Project Logo
 ---

 Key: QPID-53
 URL: https://issues.apache.org/jira/browse/QPID-53
 Project: Qpid
  Issue Type: Task
Reporter: Debbie Moynihan
Priority: Minor
 Attachments: MoreAMQPLogos.pdf, QpidLOGOS1023.pdf, qpid-logo.jpg, 
 qpid-logo.png, qpidLogo.png, qpid_logo_medium.png, qpid_logo_medium2.png, 
 qpid_logo_medium3.png, qpid_logo_medium4.png, qpid_logo_small.png, 
 qpid_logo_small2.png, qpid_logo_small3.png, qpid_logo_small4.png, 
 qpid_logo_test10.png, qpid_logo_test11.png, qpid_logo_test12.png, 
 qpid_logo_test13.png, qpid_logo_test5.png, qpid_logo_test6.png, 
 qpid_logo_test7.png, qpid_logo_test8.png, qpid_logo_test9.png, 
 qpid_logo_test9_resized.png, qpid_logo_test9_resized_padded.png


 Create a logo for the project.  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Resolved] (QPID-1627) Three T-Shirt Alternatives


 [ 
https://issues.apache.org/jira/browse/QPID-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell resolved QPID-1627.
--

Resolution: Not A Problem

Closing out, over 3 years have passed.

 Three T-Shirt Alternatives
 --

 Key: QPID-1627
 URL: https://issues.apache.org/jira/browse/QPID-1627
 Project: Qpid
  Issue Type: Wish
Reporter: michael j. goulish
Priority: Trivial
 Attachments: qpid_shirts.jpg


 All three are based on the I'm with Qpid!  idea.
 Just different shapes for the arrow.
 Original,  Manta,  and  Chevron.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Resolved] (QPID-1624) t-shirt image concept


 [ 
https://issues.apache.org/jira/browse/QPID-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell resolved QPID-1624.
--

Resolution: Not A Problem

Closing out, over 3 years have passed.

 t-shirt image concept
 -

 Key: QPID-1624
 URL: https://issues.apache.org/jira/browse/QPID-1624
 Project: Qpid
  Issue Type: Wish
Reporter: michael j. goulish
Priority: Trivial
 Attachments: im_with_qpid.jpg


 Here's a concept for a t-shirt logo based on the I'm with Qpid! slogan.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Resolved] (QPID-2316) 0.6RC2 C++ Build fails if ruby-dev and swig installed


 [ 
https://issues.apache.org/jira/browse/QPID-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell resolved QPID-2316.
--

   Resolution: Won't Fix
Fix Version/s: (was: 0.11)

Resolving in line with Justins thoughts and Teds comment.

 0.6RC2 C++ Build fails if ruby-dev and swig installed
 -

 Key: QPID-2316
 URL: https://issues.apache.org/jira/browse/QPID-2316
 Project: Qpid
  Issue Type: Bug
  Components: Build Tools
Affects Versions: 0.6, 0.7
Reporter: Rob Godfrey
Assignee: Ted Ross

 When attempting to build the C++ contained in the artefact at 
 http://qpid.apache.org/dist/qpid-0.6rc2/qpid-0.6rc2.tar.gz
 I got the following error on my machine:
 Making all in ruby
 make[2]: Entering directory `/home/rob/qpidc-0.6/bindings/qmf/ruby'
 make[2]: *** No rule to make target `ruby.i', needed by `qmfengine.cpp'.  
 Stop.
 Further investigation showed that the build succeeded on a separate machine, 
 however on this machine the qmfengine.cpp target was commented out in the 
 buildfile.  This was as a result of the fact that the second machine did not 
 have ruby development and SWIG packages installed.  After installing these 
 packages the second machine failed in the same way as the first

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Resolved] (QPID-3848) [Java broker] relax type checking during passive exchange-declares to allow null/empty type values for consistency with the C++ broker/client


 [ 
https://issues.apache.org/jira/browse/QPID-3848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell resolved QPID-3848.
--

Resolution: Fixed

Applied patch from Gordon.

 [Java broker] relax type checking during passive exchange-declares to allow 
 null/empty type values for consistency with the C++ broker/client
 -

 Key: QPID-3848
 URL: https://issues.apache.org/jira/browse/QPID-3848
 Project: Qpid
  Issue Type: Improvement
  Components: Java Broker
Reporter: Robbie Gemmell
Assignee: Robbie Gemmell
 Fix For: 0.15


 Relax type checking during passive exchange-declares to allow null/empty type 
 values for consistency with the C++ broker/client. This will resolve some 
 interoperability issues when using the C++ client (swig wrapped or not) with 
 the Java broker, e.g this thread from the user list: 
 http://mail-archives.apache.org/mod_mbox/qpid-users/201202.mbox/%3CCAAiPYj2_my7j6ox8fo5CoiU2DnK0G3YDsGCfT4RP_GWz9e2fpQ%40mail.gmail.com%3E

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Resolved] (QPID-3143) session.createQueue is neither spec compliant nor backwards compatible

[
https://issues.apache.org/jira/browse/QPID-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robbie Gemmell resolved QPID-3143.
--

Resolution: Fixed

Resolving, patch applied from a year ago.

session.createQueue is neither spec compliant nor backwards compatible
--

Key: QPID-3143
URL: https://issues.apache.org/jira/browse/QPID-3143
Project: Qpid
Issue Type: Bug
Components: Java Client
Affects Versions: 0.8
Reporter: Rajith Attapattu
Assignee: Rajith Attapattu
Priority: Minor
Fix For: 0.11

Attachments: QPID-3143.patch, QPID-3143.test.patch

According to the JMS API documentation, the createQueue method should not
create a physical queue in the broker.
Currently if just a queue name is passed, then the current implementation
will create a queue if the destination is used by a consumer or producer.
Before this change was made in rev 964984, an AMQQueue object was created
with durable true and a queue was created in the broker when the destination
object was used by a consumer.
Therefore current behaviour is neither spec complaint nor backwards
compatible.
Suggested improvement would be to just create a destination object with
create set to never. When a producer or consumer is created using this
destination it will try to resolve if the queue is present, and if not will
throw an exception.
Therefore the default behaviour would be spec compliant.
If a user needs to override this behaviour they could easily do so by
specifying the correct create option (i.e one of receiver/sender/always).
A user could also use any valid addressing string to create a more customized
destination as well.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Resolved] (QPID-3583) 0.14 release tasks


 [ 
https://issues.apache.org/jira/browse/QPID-3583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell resolved QPID-3583.
--

Resolution: Fixed

Resolving, seems like the release tasks should be complete now.

 0.14 release tasks
 --

 Key: QPID-3583
 URL: https://issues.apache.org/jira/browse/QPID-3583
 Project: Qpid
  Issue Type: Task
  Components: Packaging
Affects Versions: 0.14
Reporter: Justin Ross
Assignee: Justin Ross
 Fix For: 0.14


 A bug to track various release tasks.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Resolved] (QPID-2795) broker is unable to disconnect unresponsive 0-8/0-9 clients when attempting to once heartbeating timeout is detected


 [ 
https://issues.apache.org/jira/browse/QPID-2795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell resolved QPID-2795.
--

Resolution: Won't Fix

Closing this out, the code leading to this JIRA no longer exists, and as per 
QPID-2796 we actually now need to implement heartbeating entirely.

 broker is unable to disconnect unresponsive 0-8/0-9 clients when attempting 
 to once heartbeating timeout is detected
 

 Key: QPID-2795
 URL: https://issues.apache.org/jira/browse/QPID-2795
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: M2.1, M3, M4, 0.5, 0.6
Reporter: Robbie Gemmell

 The broker is notified that no data has been recieved from the client after 
 the appropriate heartbeating time delay, however at this point it is unable 
 to disconnect the client. On trunk, the relevant method has no implementation 
 and the notifiation is discarded. On the 0.5.x-dev branch it throws an 
 IOException which is then caught by mina and provided to exception handling 
 callback in the broker. This handler makes the assumption that the Mina 
 session will be closed because it is an IOException since this is the 
 behaviour Mina stipulates for the method, however it would seem that does not 
 apply when the exception is raised from within the sessionIdle handler, as 
 the sessionClosed handler is never called. 
 As a result of the above the broker simply sits with Mina periodically firing 
 the idle events and them effectively getting dropped. The idle handlers 
 should be updated to explicitly close the mina session at this point and 
 allow the broker to disconnect the client.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Commented] (QPID-3173) add support for specifying a maximum for message number of delivery attempts before moving messages to a dead letter queue

2012-02-15 Thread Robbie Gemmell (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/QPID-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13208898#comment-13208898
 ] 

Robbie Gemmell commented on QPID-3173:
--

Resolving, this work was undertaken in a slightly different manner via newer 
JIRA QPID-3642

 add support for specifying a maximum for message number of delivery attempts 
 before moving messages to a dead letter queue
 --

 Key: QPID-3173
 URL: https://issues.apache.org/jira/browse/QPID-3173
 Project: Qpid
  Issue Type: New Feature
  Components: Java Broker, Java Client
Reporter: Robbie Gemmell

 add support for specifying a maximum for message delivery attempts before 
 moving messages to a dead letter queue.
 At a basic level, the features will work as follows: the consumer track the 
 number of times it has seen a message without successful delivery, and when 
 this count is met/exceeded then during session rollback or recover it will 
 cause the message to be rejected with request not to be requeued. The broker 
 will be able to be configured when creating a queue as to whether or not it 
 need support such dead-lettering and set up the requisite alternate exchange 
 to route the messages to when they are rejected in this way. If enabled, then 
 a fanout exchange will be created as the alternate exchange for the queue 
 with a single queue bound, such that there is a 1:1 mapping of original queue 
 and DLQ.
 See QPID-2970 and children for reference and implementation work for older 
 codebase.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Commented] (QPID-3827) FirewallConfigTests fail on FreeBSD Jenkins CI due to peer IP reported as non-loopback

2012-02-15 Thread Robbie Gemmell (Commented) (JIRA)


[ 
https://issues.apache.org/jira/browse/QPID-3827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13208901#comment-13208901
 ] 

Robbie Gemmell commented on QPID-3827:
--

Might be worth asking if its considered a config problem on the box, but coding 
round it doesn't seems like it would be a bad idea for test robustness.

 FirewallConfigTests fail on FreeBSD Jenkins CI due to peer IP reported as 
 non-loopback
 --

 Key: QPID-3827
 URL: https://issues.apache.org/jira/browse/QPID-3827
 Project: Qpid
  Issue Type: Bug
  Components: Java Tests
Affects Versions: 0.15
Reporter: Keith Wall
Priority: Trivial

 The firewall tests fail because the tests assume that the client will be 
 connecting to the loopback address.  When the tests run on the Apache FreeBSD 
 box, the peer's actual IP is reported to the Broker (140.211.166.131).  This 
 means the network firewall rules configured by FirewallConfigTest don't fire 
 correctly. When we run the tests on other hosts, the Broker sees the loopback 
 address.
 I'm not sure if the problem is the test making a bad assumption, or a config 
 problem on the FreeBSD box.
 We *could* code around this in FirewallConfigTest by using 
 {code}
 InetAddress.getByName(localhost).getHostAddress();
 {code}
 rather than assuming 127.0.0.1.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Resolved] (QPID-1749) Create c++ client example package


 [ 
https://issues.apache.org/jira/browse/QPID-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell resolved QPID-1749.
--

Resolution: Won't Fix

 Create c++ client example package
 -

 Key: QPID-1749
 URL: https://issues.apache.org/jira/browse/QPID-1749
 Project: Qpid
  Issue Type: Sub-task
  Components: Build Tools
Reporter: Martin Ritchie



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Resolved] (QPID-1750) Create Single c# client package


 [ 
https://issues.apache.org/jira/browse/QPID-1750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell resolved QPID-1750.
--

Resolution: Not A Problem

The old clients no longer exist, resolving issue.

 Create Single c# client package
 ---

 Key: QPID-1750
 URL: https://issues.apache.org/jira/browse/QPID-1750
 Project: Qpid
  Issue Type: Sub-task
  Components: Build Tools
Reporter: Martin Ritchie



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Resolved] (QPID-1754) Create QMF Command line tools package


 [ 
https://issues.apache.org/jira/browse/QPID-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell resolved QPID-1754.
--

Resolution: Fixed

This was done some time ago.

 Create QMF Command line tools package
 -

 Key: QPID-1754
 URL: https://issues.apache.org/jira/browse/QPID-1754
 Project: Qpid
  Issue Type: Sub-task
  Components: Build Tools
Reporter: Martin Ritchie



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Resolved] (QPID-1751) Create c# example package


 [ 
https://issues.apache.org/jira/browse/QPID-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell resolved QPID-1751.
--

Resolution: Not A Problem

The old clients no longer exist, resolving issue.

 Create c# example package
 -

 Key: QPID-1751
 URL: https://issues.apache.org/jira/browse/QPID-1751
 Project: Qpid
  Issue Type: Sub-task
  Components: Build Tools
Reporter: Martin Ritchie



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Resolved] (QPID-1756) Create Ruby Example package


 [ 
https://issues.apache.org/jira/browse/QPID-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell resolved QPID-1756.
--

Resolution: Not A Problem

The old ruby client was removed, resolving.

 Create Ruby Example package
 ---

 Key: QPID-1756
 URL: https://issues.apache.org/jira/browse/QPID-1756
 Project: Qpid
  Issue Type: Sub-task
  Components: Build Tools
Reporter: Martin Ritchie



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Resolved] (QPID-3647) Type-o on Building Qpid page


 [ 
https://issues.apache.org/jira/browse/QPID-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell resolved QPID-3647.
--

Resolution: Fixed

Resolving as per comment.

 Type-o on Building Qpid page
 

 Key: QPID-3647
 URL: https://issues.apache.org/jira/browse/QPID-3647
 Project: Qpid
  Issue Type: Improvement
  Components: website
Reporter: Gordon Dickens
Priority: Trivial

 Python is misspelled on the page: https://cwiki.apache.org/qpid/building.html 
  - I tried to edit, but I do not have permission.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Resolved] (QPID-3740) add the client version string to the connection establishment logging


 [ 
https://issues.apache.org/jira/browse/QPID-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell resolved QPID-3740.
--

   Resolution: Duplicate
Fix Version/s: (was: Future)

Resolving, work was done on newer JIRA QPID-3816

 add the client version string to the connection establishment logging
 -

 Key: QPID-3740
 URL: https://issues.apache.org/jira/browse/QPID-3740
 Project: Qpid
  Issue Type: Improvement
  Components: Java Broker
Affects Versions: 0.14
Reporter: Robbie Gemmell

 It would be useful if the connection establishment logging included the 
 version string for the client in use, to facilitate identifying client 
 versions in use for support reasons (e.g. to enable tracking of which people 
 are using outdated client versions, or identifying what code version to 
 examine when debugging issues).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Updated] (QPID-3530) Unify the QueueBrowsers behavior on 0-8/0-9/0-10 code paths when failover happens.


 [ 
https://issues.apache.org/jira/browse/QPID-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell updated QPID-3530:
-

Fix Version/s: (was: 0.13)
   Future

 Unify the QueueBrowsers behavior on  0-8/0-9/0-10 code paths when failover 
 happens.
 ---

 Key: QPID-3530
 URL: https://issues.apache.org/jira/browse/QPID-3530
 Project: Qpid
  Issue Type: Improvement
  Components: Java Client
Reporter: Alex Rudyy
 Fix For: Future


 The current functionality of QueueBrowser on 0-8/0-9/0-10 code paths behaves 
 differently when failover happens. QueueBrowsers on 0-10 path invoke 
 receiveNoWait() in order to browse the queue while QueueBrowsers on 0-9 path 
 invoke receive() method. When failover happens 0-8/0-9/0-9-1 QueueBrowsers 
 block and restart the browsing of the queue from the beginning after failover 
 is finished while 0-10 QueueBrowsers return null when invoked during 
 failover. 
 QueueBrowser functionality should be changed to throw NoSuchElementException 
 on iteration through the queue messages when falover happens.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Updated] (QPID-3531) Report the failover occurrence to the client application via ExceptionListener


 [ 
https://issues.apache.org/jira/browse/QPID-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell updated QPID-3531:
-

Fix Version/s: (was: 0.13)
   Future

 Report the failover occurrence to the client application via ExceptionListener
 --

 Key: QPID-3531
 URL: https://issues.apache.org/jira/browse/QPID-3531
 Project: Qpid
  Issue Type: Improvement
  Components: Java Client
Reporter: Alex Rudyy
 Fix For: Future


 With current JMS client implementation when failover happens the client 
 application is not notified about it. In order to report failover occurrence 
 to the client application a special JMS exception needs to be sent into 
 connection ExceptionListener (if such is registered with connection).
 In this case the JMS client application code can decide what approach to 
 take: whether call connection.close() etc, or take advantage of their 
 configured failover reconnect feature.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Updated] (QPID-2476) Complete ACL implementation for 0-10 code path


 [ 
https://issues.apache.org/jira/browse/QPID-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell updated QPID-2476:
-

Fix Version/s: (was: 0.13)
   Future

 Complete ACL implementation for 0-10 code path
 --

 Key: QPID-2476
 URL: https://issues.apache.org/jira/browse/QPID-2476
 Project: Qpid
  Issue Type: New Feature
  Components: Java Broker
Affects Versions: 0.7, 0.9
Reporter: Andrew Kennedy
  Labels: qpid, security
 Fix For: Future

 Attachments: acl.txt, method-considered-harmful.txt, method-redux.txt

   Original Estimate: 336h
  Remaining Estimate: 336h

 Complete ACL implementation for 0-10 code path, providing an ACLv2 
 implementation that covers the following features/requirements:
 - Best practice security design
 - Support for roles/groups
 - Appropriate for standard stores for authorisation credentials (e.g. LDAP, 
 Kerberos)
 - Expressable as XML
 - Easy to store/backup/extract ACL config
 - Exception handling catching at point of ACL application and return to 
 client via Connection ExceptionListener with correct error code, log failure 
 in broker
 - No significant performance cost on publish, permissions to be cached
 - Security handled at correct level of abstraction internally
 - Interoperability with existing ACLv2

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Assigned] (QPID-3052) Java test profiles do not effectively test all AMQP protocol versions

2012-02-15 Thread Robbie Gemmell (Assigned) (JIRA)


 [ 
https://issues.apache.org/jira/browse/QPID-3052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell reassigned QPID-3052:


Assignee: Robbie Gemmell  (was: Andrew Kennedy)

 Java test profiles do not effectively test all AMQP protocol versions
 -

 Key: QPID-3052
 URL: https://issues.apache.org/jira/browse/QPID-3052
 Project: Qpid
  Issue Type: Bug
  Components: Java Tests
Affects Versions: 0.9, 0.10, 0.11, 0.12
Reporter: Andrew Kennedy
Assignee: Robbie Gemmell
Priority: Minor
 Fix For: 0.15


 The Java test profiles assume that, particularly default one for InVm 
 transports, the 0-10 protocol will fail, causing renegotiation. If 0-10 InVm 
 support is added then the default protocol will use this. It seems to make 
 more sense to specify exactly the version the client and the broker should 
 announce, and force renegotiation explicitly by disabling various protocol 
 versions on the command line when starting an external Java broker. Note that 
 this is not possible to specify for the InVm profiles anyway. Also, the only 
 protocol that is ever tested will be the highest supported by both broker and 
 client, therefore this is AMQP 0-9-1. In order for the tests not to do 
 surprising things when new protocol versions are added, I think that setting 
 versions explicitly is the best idea. I woulsd also like to add an explicit 
 0-8 test profile for both InVM and external Java brokers, in order to 
 exercise and get coverage on this code.
 In future, I recommend that some form of combinatorial profile system be 
 investigated for the test subsystem, allowing the required protocol, broker 
 type and so on to be specified separately.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Updated] (QPID-3052) Java test profiles do not effectively test all AMQP protocol versions


 [ 
https://issues.apache.org/jira/browse/QPID-3052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell updated QPID-3052:
-

Fix Version/s: (was: 0.13)
   0.15

 Java test profiles do not effectively test all AMQP protocol versions
 -

 Key: QPID-3052
 URL: https://issues.apache.org/jira/browse/QPID-3052
 Project: Qpid
  Issue Type: Bug
  Components: Java Tests
Affects Versions: 0.9, 0.10, 0.11, 0.12
Reporter: Andrew Kennedy
Assignee: Andrew Kennedy
Priority: Minor
 Fix For: 0.15


 The Java test profiles assume that, particularly default one for InVm 
 transports, the 0-10 protocol will fail, causing renegotiation. If 0-10 InVm 
 support is added then the default protocol will use this. It seems to make 
 more sense to specify exactly the version the client and the broker should 
 announce, and force renegotiation explicitly by disabling various protocol 
 versions on the command line when starting an external Java broker. Note that 
 this is not possible to specify for the InVm profiles anyway. Also, the only 
 protocol that is ever tested will be the highest supported by both broker and 
 client, therefore this is AMQP 0-9-1. In order for the tests not to do 
 surprising things when new protocol versions are added, I think that setting 
 versions explicitly is the best idea. I woulsd also like to add an explicit 
 0-8 test profile for both InVM and external Java brokers, in order to 
 exercise and get coverage on this code.
 In future, I recommend that some form of combinatorial profile system be 
 investigated for the test subsystem, allowing the required protocol, broker 
 type and so on to be specified separately.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Updated] (QPID-3271) The toString() representation of the JMSDestination of a received message is different from the toString() representation on the sender side

[
https://issues.apache.org/jira/browse/QPID-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robbie Gemmell updated QPID-3271:
-

Fix Version/s: (was: 0.11)
Future

The toString() representation of the JMSDestination of a received message is
different from the toString() representation on the sender side

Key: QPID-3271
URL: https://issues.apache.org/jira/browse/QPID-3271
Project: Qpid
Issue Type: Bug
Components: Java Client
Affects Versions: 0.8, 0.10
Reporter: Rajith Attapattu
Assignee: Rajith Attapattu
Priority: Minor
Fix For: Future

The value of toString() on the JMS Destination of a message being sent is
different from to the toString() value of JMS Destination of the same message
on the receiver side.
Ex for clients using the BURL syntax.
Sender side
The JMSDestination on the sent message is
direct://amq.direct//testQueue?routingkey='key1'
Receiver side
The JMSDestination on the recvd message is
direct://amq.direct/key1/key1?routingkey='key1'
Ex for client using the ADDR syntax.
Sender side
JMS Destination: 'amq.direct'/'test'; None
Receiver side
JMS Destination: direct://amq.direct/test/test?routingkey='test'
How reproducible:
Always
Steps to Reproduce:
1. Use spout to send a message and observe the JMS Destination printed on the
screen.
2. Use drain to receive that message and observe the same.
3. Note that they are represented differently.
Actual results:
The toString representations are different.
(However they contain the correct exchange and routing key information).
Expected results:
The toString representations should be the same.

-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Updated] (QPID-3272) Allow JMS messages originated from another vendor to be sent through Qpid with the Message ID intact.


 [ 
https://issues.apache.org/jira/browse/QPID-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell updated QPID-3272:
-

Fix Version/s: (was: 0.11)
   Future

 Allow JMS messages originated from another vendor to be sent through Qpid 
 with the Message ID intact.
 -

 Key: QPID-3272
 URL: https://issues.apache.org/jira/browse/QPID-3272
 Project: Qpid
  Issue Type: Bug
  Components: Java Client
Affects Versions: 0.6, 0.8, 0.10
Reporter: Rajith Attapattu
Assignee: Rajith Attapattu
Priority: Minor
 Fix For: Future


 A message bridge it forwards messages between two different messaging 
 providers.
 However when attempting to send a message from another vendor through Qpid, 
 the send method throws an exception if the message ID is not a UUID. 
 javax.jms.JMSException: MessageId
 'ID:dhcp209-12.gsslab.pnq.redhat.com-45266-1305237148981-3:0:3:1:1' is not of
 the correct format, it must be ID: followed by a UUID
  at
 org.apache.qpid.client.message.AMQMessageDelegate_0_10.setJMSMessageID(AMQMessageDelegate_0_10.java:165)
  at
 org.apache.qpid.client.message.AbstractJMSMessage.setJMSMessageID(AbstractJMSMessage.java:92)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Resolved] (QPID-3505) Improve failover implementation and testing


 [ 
https://issues.apache.org/jira/browse/QPID-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell resolved QPID-3505.
--

Resolution: Fixed

Resolving, additional tests etc were added via other JIRAs. Any future work 
will be via new JIRAs.

 Improve failover implementation and testing
 ---

 Key: QPID-3505
 URL: https://issues.apache.org/jira/browse/QPID-3505
 Project: Qpid
  Issue Type: Improvement
  Components: Java Client
Affects Versions: 0.5, 0.6, 0.7, 0.8, 0.9, 0.10, 0.11, 0.12
Reporter: Alex Rudyy
Assignee: Alex Rudyy
 Fix For: 0.13

 Attachments: 0001-New-failover-tests.patch


 As it has been discussed on the mailing list there are several issues with 
 implementation of failover on the client.
 Expected failover behaviour of the client is being discussed on following 
 WIKI page 
 https://cwiki.apache.org/confluence/display/qpid/Client+Failover+Behaviour 
 This JIRA will capture improvements and testing related to this work.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Updated] (QPID-2720) enable setting an alternative BundleContext to allow the broker to use an existing OSGi container


 [ 
https://issues.apache.org/jira/browse/QPID-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell updated QPID-2720:
-

Summary: enable setting an alternative BundleContext to allow the broker to 
use an existing OSGi container  (was: Qpid broker can not run inside an OSGi 
container)

 enable setting an alternative BundleContext to allow the broker to use an 
 existing OSGi container
 -

 Key: QPID-2720
 URL: https://issues.apache.org/jira/browse/QPID-2720
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Reporter: Danushka Menikkumbura
Assignee: Danushka Menikkumbura
 Fix For: 0.13

 Attachments: QPID-2720-V2.patch, QPID-2720-V3.patch, QPID-2720.patch




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Resolved] (QPID-2720) enable setting an alternative BundleContext to allow the broker to use an existing OSGi container


 [ 
https://issues.apache.org/jira/browse/QPID-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell resolved QPID-2720.
--

Resolution: Fixed
  Assignee: Robbie Gemmell  (was: Danushka Menikkumbura)

Resolving this as it was included in the last release, any updates will be via 
new JIRAs.

 enable setting an alternative BundleContext to allow the broker to use an 
 existing OSGi container
 -

 Key: QPID-2720
 URL: https://issues.apache.org/jira/browse/QPID-2720
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Reporter: Danushka Menikkumbura
Assignee: Robbie Gemmell
 Fix For: 0.13

 Attachments: QPID-2720-V2.patch, QPID-2720-V3.patch, QPID-2720.patch




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Resolved] (QPID-2693) Broker instability with the topic exchange


 [ 
https://issues.apache.org/jira/browse/QPID-2693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell resolved QPID-2693.
--

   Resolution: Fixed
Fix Version/s: (was: 0.13)

Resolving this old JIRA, original issue was with use of the underlying 
transport impl and any additional work will be via new JIRAs.

 Broker instability with the topic exchange
 --

 Key: QPID-2693
 URL: https://issues.apache.org/jira/browse/QPID-2693
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: 0.7, 0.8, 0.9, 0.10, 0.11, 0.12
 Environment: java version 1.6.0_12
 Java(TM) SE Runtime Environment (build 1.6.0_12-b04)
 Java HotSpot(TM) 64-Bit Server VM (build 11.2-b01, mixed mode)
 Linux 2.6.24-11-pve #1 SMP PREEMPT Fri May 14 09:28:08 CEST 2010 x86_64 
 GNU/Linux
Reporter: Emmanuel Bourg
Assignee: Robbie Gemmell
Priority: Critical
 Attachments: qpid-dump.txt, qpid-log.txt


 I've noticed an instability of the Java broker when sending a high volume of 
 messages to the topic exchange. The messages are non acked, non durable. 
 After about 15 minutes the messages can no longer be dispatched and the 
 client gets this exception:
 org.apache.qpid.transport.SessionException: timed out waiting for sync: 
 complete = 77824, point = 77825
 at org.apache.qpid.transport.Session.sync(Session.java:743)
 at org.apache.qpid.transport.Session.sync(Session.java:712)
 at org.apache.qpid.transport.Session.invoke(Session.java:672)
 at org.apache.qpid.transport.Session.invoke(Session.java:518)
 at 
 org.apache.qpid.transport.SessionInvoker.messageTransfer(SessionInvoker.java:96)
 at org.apache.qpid.transport.Session.messageTransfer(Session.java:880)
 And in the server log I get these exceptions:
 2010-06-25 02:48:48,005 [ERROR] Exception thrown and no ProtocolEngine to 
 handle it
 org.apache.qpid.transport.SessionException: timed out waiting for completion
 at org.apache.qpid.transport.Session.invoke(Session.java:635)
 at 
 org.apache.qpid.server.transport.ServerSession.sendMessage(ServerSession.java:180)
 at 
 org.apache.qpid.server.subscription.Subscription_0_10.send(Subscription_0_10.java:573)
 at 
 org.apache.qpid.server.queue.SimpleAMQQueue.deliverMessage(SimpleAMQQueue.java:715)
 at 
 org.apache.qpid.server.queue.SimpleAMQQueue.deliverToSubscription(SimpleAMQQueue.java:658)
 at 
 org.apache.qpid.server.queue.SimpleAMQQueue.enqueue(SimpleAMQQueue.java:611)
 at 
 org.apache.qpid.server.queue.SimpleAMQQueue.enqueue(SimpleAMQQueue.java:536)
 at 
 org.apache.qpid.server.transport.ServerSession$1.postCommit(ServerSession.java:157)
 at 
 org.apache.qpid.server.txn.AutoCommitTransaction.enqueue(AutoCommitTransaction.java:151)
 at 
 org.apache.qpid.server.transport.ServerSession.enqueue(ServerSession.java:146)
 at 
 org.apache.qpid.server.transport.ServerSessionDelegate.messageTransfer(ServerSessionDelegate.java:287)
 at 
 org.apache.qpid.server.transport.ServerSessionDelegate.messageTransfer(ServerSessionDelegate.java:96)
 at 
 org.apache.qpid.transport.MessageTransfer.dispatch(MessageTransfer.java:103)
 at 
 org.apache.qpid.transport.SessionDelegate.command(SessionDelegate.java:46)
 at 
 org.apache.qpid.server.transport.ServerSessionDelegate.command(ServerSessionDelegate.java:110)
 at 
 org.apache.qpid.server.transport.ServerSessionDelegate.command(ServerSessionDelegate.java:96)
 at org.apache.qpid.transport.Method.delegate(Method.java:159)
 at org.apache.qpid.transport.Session.received(Session.java:487)
 at org.apache.qpid.transport.Connection.dispatch(Connection.java:377)
 at 
 org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:64)
 at 
 org.apache.qpid.transport.ConnectionDelegate.handle(ConnectionDelegate.java:40)
 at 
 org.apache.qpid.transport.MethodDelegate.messageTransfer(MethodDelegate.java:113)
 at 
 org.apache.qpid.transport.MessageTransfer.dispatch(MessageTransfer.java:103)
 at 
 org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:54)
 at 
 org.apache.qpid.transport.ConnectionDelegate.command(ConnectionDelegate.java:40)
 at org.apache.qpid.transport.Method.delegate(Method.java:159)
 at org.apache.qpid.transport.Connection.received(Connection.java:342)
 at org.apache.qpid.transport.Connection.received(Connection.java:55)
 at org.apache.qpid.transport.network.Assembler.emit(Assembler.java:98)
 at 
 org.apache.qpid.transport.network.Assembler.assemble(Assembler.java:220)
 at

[jira] [Resolved] (QPID-3450) Client.session() method in the python client always pick 1 as the channel id


 [ 
https://issues.apache.org/jira/browse/QPID-3450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell resolved QPID-3450.
--

Resolution: Fixed
  Assignee: Robbie Gemmell  (was: Rafael H. Schloming)

Resolving this, it was included in the last release, and Keith looked it over 
at the time with me.

 Client.session() method in the python client always pick 1 as the channel id
 

 Key: QPID-3450
 URL: https://issues.apache.org/jira/browse/QPID-3450
 Project: Qpid
  Issue Type: Bug
  Components: Python Client
Affects Versions: M4, 0.5, 0.6, 0.7, 0.8, 0.9, 0.10, 0.11, 0.12
Reporter: Robbie Gemmell
Assignee: Robbie Gemmell
 Fix For: 0.13


 the Client.session() method in the python client always pick 1 as the channel 
 id, due to using the defaulted id variable instead of the loop counter whilst 
 iterating the session list for the first unused id number.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Updated] (QPID-3822) Manual pages needed for all qpid tools in tools directory


 [ 
https://issues.apache.org/jira/browse/QPID-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell updated QPID-3822:
-

Fix Version/s: (was: 0.13)
   0.15

Updating fix-for to an unreleased version.

 Manual pages needed for all qpid tools in tools directory
 -

 Key: QPID-3822
 URL: https://issues.apache.org/jira/browse/QPID-3822
 Project: Qpid
  Issue Type: New Feature
  Components: Tools
Affects Versions: 0.13
 Environment: all
Reporter: Ken Giusti
Priority: Minor
 Fix For: 0.15


 All the tools used to manage the qpid broker - qpid-config, qpid-route, 
 qpid-stat, etc - should have man pages, and have them installed as part of 
 the installation step.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Updated] (QPID-3265) Can't subscribe to headers exchange using address (rather than BURL)


 [ 
https://issues.apache.org/jira/browse/QPID-3265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robbie Gemmell updated QPID-3265:
-

Fix Version/s: (was: 0.13)
   0.15

Updating fix-for to an unreleased version.

 Can't subscribe to headers exchange using address (rather than BURL)
 

 Key: QPID-3265
 URL: https://issues.apache.org/jira/browse/QPID-3265
 Project: Qpid
  Issue Type: Bug
  Components: Java Client
Affects Versions: 0.10
 Environment: java 0.10 client
Reporter: Gordon Sim
Assignee: Rajith Attapattu
 Fix For: 0.15


 Creating a receiver for the following address works from python and c++, but 
 not from JMS (using drain example in each case):
   my-headers-exchange; 
 {link:{x-bindings:[{arguments:{'x-match':all,a:b,c:d}}]}}
 The problem with JMS seems to be that though it correctly interprets the 
 arguments and issues a bind with them in it, it issues another bind to the 
 exchange with no arguments that fails with an error.
 Also, the following also doesn't work:
   my-subscription-queue; {create:always, node:{x-declare:{auto-delete:True}}, 
 link:{x-bindings:[{queue:my-subscription-queue, exchange:my-headers-exchange, 
 arguments:{'x-match':all,a:b,c:d}}]}}
 Here the x-bindings in the link don't seem to get interpreted. However if 
 instead they are moved to the node, that works.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



-
Apache Qpid - AMQP Messaging Implementation
Project:  http://qpid.apache.org
Use/Interact: mailto:dev-subscr...@qpid.apache.org

[jira] [Updated] (QPID-3389) Provide more descriptive error text when sasl config. file is malformed