[jira] Resolved: (QPID-1849) createObjectMessage doesn't add payload to message

2009-11-11 Thread Aidan Skinner (JIRA)
[ https://issues.apache.org/jira/browse/QPID-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-1849. - Resolution: Fixed fixed in r835135 > createObjectMessage doesn't add payload to message > ---

[jira] Resolved: (QPID-2184) updated ip whitelisting / firewall config doesnt take effect after SIGHUP or reloadSecurityConfiguration() JMX method

2009-11-11 Thread Aidan Skinner (JIRA)
[ https://issues.apache.org/jira/browse/QPID-2184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aidan Skinner resolved QPID-2184. - Resolution: Fixed Fixed in r835115 > updated ip whitelisting / firewall config doesnt take effect

Re: Reorganized Documentation Pages

2009-11-11 Thread Robert Greig
2009/11/10 Jonathan Robie : > I have reorganized the documentation pages: > > http://cwiki.apache.org/confluence/display/qpid/Documentation Looks good. I have one question that isn't really related to the reorganisation per se. Looking at the "AMQP C++ Messaging Client" page, I don't see any lin

Re: New SASL capability for the Python client

2009-11-11 Thread Ted Ross
On 11/11/2009 04:29 PM, Andrew Stitcher wrote: On Wed, 2009-11-11 at 15:50 -0500, Ted Ross wrote: Full SASL authentication/encryption capability for the Python client was added to the trunk at revision 834975. A new Python module "qpidsasl" implemented in C++ and wrapped for Python using Sw

Re: New SASL capability for the Python client

2009-11-11 Thread Carl Trieloff
Andrew Stitcher wrote: On Wed, 2009-11-11 at 16:29 -0500, Andrew Stitcher wrote: On Wed, 2009-11-11 at 15:50 -0500, Ted Ross wrote: Full SASL authentication/encryption capability for the Python client was added to the trunk at revision 834975. A new Python module "qpidsasl" implemente

Re: New SASL capability for the Python client

2009-11-11 Thread Andrew Stitcher
On Wed, 2009-11-11 at 16:29 -0500, Andrew Stitcher wrote: > On Wed, 2009-11-11 at 15:50 -0500, Ted Ross wrote: > > Full SASL authentication/encryption capability for the Python client was > > added to the trunk at revision 834975. > > > > A new Python module "qpidsasl" implemented in C++ and wrap

RE: New SASL capability for the Python client

2009-11-11 Thread Riggs, Rob
> From: Ted Ross [mailto:tr...@redhat.com] > > Full SASL authentication/encryption capability for the Python client > was added to the trunk at revision 834975. > > A new Python module "qpidsasl" implemented in C++ and wrapped for > Python Swig was introduced. This wrapper provides a generalized

Re: New SASL capability for the Python client

2009-11-11 Thread Andrew Stitcher
On Wed, 2009-11-11 at 15:50 -0500, Ted Ross wrote: > Full SASL authentication/encryption capability for the Python client was > added to the trunk at revision 834975. > > A new Python module "qpidsasl" implemented in C++ and wrapped for Python > using Swig was introduced. This wrapper provides

New SASL capability for the Python client

2009-11-11 Thread Ted Ross
Full SASL authentication/encryption capability for the Python client was added to the trunk at revision 834975. A new Python module "qpidsasl" implemented in C++ and wrapped for Python using Swig was introduced. This wrapper provides a generalized binding to the Cyrus SASL library. The Pytho

Re: xqilla-dev

2009-11-11 Thread Rodrigo K. Ferreira
Thanks Gordon, I did that and other packages was fine. On Tue, Nov 10, 2009 at 8:14 AM, Gordon Sim wrote: > On 11/07/2009 11:40 AM, Rodrigo K. Ferreira wrote: > >> Hi, >> >> I'm trying to compile qpidc on rhel 4, but I stopped at xqilla and >> xqilla-dev dependencie, anyone have pre-compiled rp

[jira] Updated: (QPID-2193) Allow deleting the first message on a queue through the JMX Management Console when connected to older brokers

2009-11-11 Thread Robbie Gemmell (JIRA)
[ https://issues.apache.org/jira/browse/QPID-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-2193: - Status: Ready To Review (was: In Progress) > Allow deleting the first message on a queue through

[jira] Commented: (QPID-2193) Allow deleting the first message on a queue through the JMX Management Console when connected to older brokers

2009-11-11 Thread Robbie Gemmell (JIRA)
[ https://issues.apache.org/jira/browse/QPID-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12776461#action_12776461 ] Robbie Gemmell commented on QPID-2193: -- Ive added a warning note to the confirmation di

[jira] Updated: (QPID-2196) JMX Management Console may try to auto-refresh between recieving notification of JMXConnector failure/closure and the server view actually being closed

2009-11-11 Thread Robbie Gemmell (JIRA)
[ https://issues.apache.org/jira/browse/QPID-2196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-2196: - Status: Ready To Review (was: In Progress) > JMX Management Console may try to auto-refresh betwe

Re: Store tests

2009-11-11 Thread Martin Ritchie
2009/11/11 Ján Sáreník : > Hello! > > On Wed, Nov 11, 2009 at 02:45:25AM +, James Birdsall wrote: >> + clicking on the "Qpid Testing" link gets me a login page, then after >> I log in I get "You cannot view this page", "Page level restrictions >> have been applied that limit access to this page

Re: Store tests

2009-11-11 Thread Ján Sáreník
Hello! On Wed, Nov 11, 2009 at 02:45:25AM +, James Birdsall wrote: > + clicking on the "Qpid Testing" link gets me a login page, then after > I log in I get "You cannot view this page", "Page level restrictions > have been applied that limit access to this page." > I am experiencing all the

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

2009-11-11 Thread Gordon Sim (JIRA)
[ https://issues.apache.org/jira/browse/QPID-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12776385#action_12776385 ] Gordon Sim commented on QPID-1899: -- Sorry Steve, that was my fault! I forgot to consider th

[jira] Updated: (QPID-2190) enable the updated jmx management console to connect to very old brokers

2009-11-11 Thread Robbie Gemmell (JIRA)
[ https://issues.apache.org/jira/browse/QPID-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-2190: - Status: Ready To Review (was: In Progress) > enable the updated jmx management console to connect

[jira] Updated: (QPID-2178) Allow viewing of channel flow control status via JMX Management Console

2009-11-11 Thread Robbie Gemmell (JIRA)
[ https://issues.apache.org/jira/browse/QPID-2178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-2178: - Status: Ready To Review (was: In Progress) > Allow viewing of channel flow control status via JMX

[jira] Updated: (QPID-2189) only admin level users can complete connection to 2.5.0.0 or below (when configured to use / JMXMP)

2009-11-11 Thread Robbie Gemmell (JIRA)
[ https://issues.apache.org/jira/browse/QPID-2189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated QPID-2189: - Status: Ready To Review (was: In Progress) > only admin level users can complete connection to 2.