[jira] [Commented] (QPID-5001) Dispatch - A web page on the site for the Dispatch Router component
[ https://issues.apache.org/jira/browse/QPID-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13802513#comment-13802513 ] ASF subversion and git services commented on QPID-5001: --- Commit 1534893 from [~tedross] [ https://svn.apache.org/r1534893 ] QPID-5001 - Minor edits > Dispatch - A web page on the site for the Dispatch Router component > --- > > Key: QPID-5001 > URL: https://issues.apache.org/jira/browse/QPID-5001 > Project: Qpid > Issue Type: Bug > Components: Qpid Dispatch, Website >Reporter: Ted Ross >Assignee: Ted Ross > > This issue will track updates to the new Dispatch Router web page. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
RE: Documentation on flow control?
Hi Kerry, Does the broker queue constraints help your use case? http://qpid.apache.org/releases/qpid-0.24/cpp-broker/book/ch01s02.html#CheatSheetforconfiguringQueueOptions-ConfiguringQueueOptions -Steve > -Original Message- > From: Kerry Bonin [mailto:kerrybo...@gmail.com] > Sent: Tuesday, October 22, 2013 3:43 PM > To: qpid-dev > Subject: Documentation on flow control? > > Hello! I'm working on our next product scale up, and qpidd remains a critical > part of our infrastructure. One area where we are expecting challenges is > around flow control, which is exacerbated by our product currently being > Windows only (no federation or clustering.) For our 0.10 based release, flow > control was ugly. Only QMF seems to let us keep track of when the system is > in a state where producers are pushing faster than consumers are pulling, as > client exceptions were rather unreliable signalling mechanisms, and didn't > prevent us from crashing the broker, which we ended up having to deploy a > watchdog for. > > I was wondering where I could find documentation on what is currently > exposed for flow control, and any recommendations on best practices for > using it? Also, I was wondering if there are any client feedback mechanisms > other than QMF yet, or if I should start spending time integrating QMF based > feedback into our clients? > > Any pointers are greatly appreciated! > > Kerry Bonin > Lead Architect, UTC Fire & Security Integration Platform Team - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5001) Dispatch - A web page on the site for the Dispatch Router component
[ https://issues.apache.org/jira/browse/QPID-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13802309#comment-13802309 ] ASF subversion and git services commented on QPID-5001: --- Commit 1534810 from [~tedross] [ https://svn.apache.org/r1534810 ] QPID-5001 - Added content about Qpid Dispatch compliance with the AMQP Management specification. > Dispatch - A web page on the site for the Dispatch Router component > --- > > Key: QPID-5001 > URL: https://issues.apache.org/jira/browse/QPID-5001 > Project: Qpid > Issue Type: Bug > Components: Qpid Dispatch, Website >Reporter: Ted Ross >Assignee: Ted Ross > > This issue will track updates to the new Dispatch Router web page. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4984) Linear File Allocation for the Linux AIO Store
[ https://issues.apache.org/jira/browse/QPID-4984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13802254#comment-13802254 ] ASF subversion and git services commented on QPID-4984: --- Commit 1534781 from [~astitcher] in branch 'qpid/trunk' [ https://svn.apache.org/r1534781 ] QPID-4984: Make C++ tree build again > Linear File Allocation for the Linux AIO Store > -- > > Key: QPID-4984 > URL: https://issues.apache.org/jira/browse/QPID-4984 > Project: Qpid > Issue Type: Improvement > Components: C++ Broker >Reporter: Ted Ross >Assignee: Kim van der Riet > > This Jira is for a proposed change to the AIO "legacy" store in the Qpid C++ > Broker. > Rather than pre-allocating store files in a fixed-size ring buffer (per > queue), the linear store allocates files to queue journals on an as-needed > basis, freeing them to a free-pool when no longer needed (i.e. all stored > messages have been dequeued). > The development is ongoing in a branch called "linearstore". -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Documentation on flow control?
Hello! I'm working on our next product scale up, and qpidd remains a critical part of our infrastructure. One area where we are expecting challenges is around flow control, which is exacerbated by our product currently being Windows only (no federation or clustering.) For our 0.10 based release, flow control was ugly. Only QMF seems to let us keep track of when the system is in a state where producers are pushing faster than consumers are pulling, as client exceptions were rather unreliable signalling mechanisms, and didn't prevent us from crashing the broker, which we ended up having to deploy a watchdog for. I was wondering where I could find documentation on what is currently exposed for flow control, and any recommendations on best practices for using it? Also, I was wondering if there are any client feedback mechanisms other than QMF yet, or if I should start spending time integrating QMF based feedback into our clients? Any pointers are greatly appreciated! Kerry Bonin Lead Architect, UTC Fire & Security Integration Platform Team
[jira] [Commented] (QPID-4984) Linear File Allocation for the Linux AIO Store
[ https://issues.apache.org/jira/browse/QPID-4984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13802145#comment-13802145 ] ASF subversion and git services commented on QPID-4984: --- Commit 1534736 from [~kpvdr] in branch 'qpid/trunk' [ https://svn.apache.org/r1534736 ] QPID-4984: WIP: Copy of work over from branch to trunk. Non-tx works with some known bugs, tx not yet operational. > Linear File Allocation for the Linux AIO Store > -- > > Key: QPID-4984 > URL: https://issues.apache.org/jira/browse/QPID-4984 > Project: Qpid > Issue Type: Improvement > Components: C++ Broker >Reporter: Ted Ross >Assignee: Kim van der Riet > > This Jira is for a proposed change to the AIO "legacy" store in the Qpid C++ > Broker. > Rather than pre-allocating store files in a fixed-size ring buffer (per > queue), the linear store allocates files to queue journals on an as-needed > basis, freeing them to a free-pool when no longer needed (i.e. all stored > messages have been dequeued). > The development is ongoing in a branch called "linearstore". -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5216) Dispatch - Stabilization in anticipation of an early release
[ https://issues.apache.org/jira/browse/QPID-5216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13802110#comment-13802110 ] ASF subversion and git services commented on QPID-5216: --- Commit 1534726 from [~tedross] in branch 'qpid/trunk' [ https://svn.apache.org/r1534726 ] QPID-5216 - Removed "area" from the configuration as it is not currently implemented > Dispatch - Stabilization in anticipation of an early release > > > Key: QPID-5216 > URL: https://issues.apache.org/jira/browse/QPID-5216 > Project: Qpid > Issue Type: Bug > Components: Qpid Dispatch >Reporter: Ted Ross >Assignee: Ted Ross > > This issue is a placeholder for general stabilization of Dispatch. Effort is > underway to root out memory leaks, crashes, and any other instabilities. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-3914) SSL Client Authentication support for the Windows C++ client
[ https://issues.apache.org/jira/browse/QPID-3914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13802074#comment-13802074 ] ASF subversion and git services commented on QPID-3914: --- Commit 1534714 from cliffjan...@apache.org in branch 'qpid/trunk' [ https://svn.apache.org/r1534714 ] QPID-3914: Windows C++ SSL client certificate authentication support > SSL Client Authentication support for the Windows C++ client > > > Key: QPID-3914 > URL: https://issues.apache.org/jira/browse/QPID-3914 > Project: Qpid > Issue Type: New Feature > Components: C++ Client >Affects Versions: 0.14, 0.16 > Environment: Windows (all versions) >Reporter: JAkub Scholz >Assignee: Cliff Jansen > Attachments: ssl-client-authentication.patch, > ssl-client-authentication-updated.patch, ssl-client-auth-filecert.patch, > ssl-client-auth-filecert-updated.patch > > > The Windows C++ client has been missing support for the SSL Client > Authentication - authentication using SSL certificates on the client side. > The patch attached to this JIRA implements this feature. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5216) Dispatch - Stabilization in anticipation of an early release
[ https://issues.apache.org/jira/browse/QPID-5216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13802064#comment-13802064 ] ASF subversion and git services commented on QPID-5216: --- Commit 1534710 from [~tedross] in branch 'qpid/trunk' [ https://svn.apache.org/r1534710 ] QPID-5216 - Cleaned up the format of a router-id in the message annotations. > Dispatch - Stabilization in anticipation of an early release > > > Key: QPID-5216 > URL: https://issues.apache.org/jira/browse/QPID-5216 > Project: Qpid > Issue Type: Bug > Components: Qpid Dispatch >Reporter: Ted Ross >Assignee: Ted Ross > > This issue is a placeholder for general stabilization of Dispatch. Effort is > underway to root out memory leaks, crashes, and any other instabilities. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5203) Python client unexpected exception after ACL denial
[
https://issues.apache.org/jira/browse/QPID-5203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13801862#comment-13801862
]
ASF subversion and git services commented on QPID-5203:
---
Commit 1534643 from [~pmoravec] in branch 'qpid/trunk'
[ https://svn.apache.org/r1534643 ]
QPID-5203 Python client unexpected exception after ACL denial
> Python client unexpected exception after ACL denial
> ---
>
> Key: QPID-5203
> URL: https://issues.apache.org/jira/browse/QPID-5203
> Project: Qpid
> Issue Type: Bug
> Components: Python Client
>Affects Versions: 0.24
>Reporter: Pavel Moravec
>Assignee: Pavel Moravec
>Priority: Minor
> Attachments: bz974940.py
>
>
> Description of problem:
> After ACL denies a command from qpid Python client, an attempt to close
> either session or connection raises unexpected exception (relevant to ACL,
> though). While at that time, session is properly closed and connection is
> working fine.
> Version-Release number of selected component (if applicable):
> every
> How reproducible:
> 100%
> Steps to Reproduce:
> 1. Have ACL file:
> acl deny all consume all
> acl allow all all
> 2. Run attached script.
> Actual results:
>
> Create receiver failed with exception
> Traceback (most recent call last):
> File "ACL_denial_session-hang.py", line 13, in
> recv = session.receiver('testQ; {create:always}')
> File "", line 6, in receiver
> File "/usr/lib/python2.6/site-packages/qpid/messaging/endpoints.py", line
> 616, in receiver
> receiver._ewait(lambda: receiver.linked)
> File "/usr/lib/python2.6/site-packages/qpid/messaging/endpoints.py", line
> 973, in _ewait
> result = self.session._ewait(lambda: self.error or predicate(), timeout)
> File "/usr/lib/python2.6/site-packages/qpid/messaging/endpoints.py", line
> 567, in _ewait
> self.check_error()
> File "/usr/lib/python2.6/site-packages/qpid/messaging/endpoints.py", line
> 556, in check_error
> raise self.error
> UnauthorizedAccess: unauthorized-access: ACL denied Queue subscribe request
> from guest@QPID (qpid/broker/SessionAdapter.cpp:399)(403)
>
> Session close failed with exception
> Traceback (most recent call last):
> File "ACL_denial_session-hang.py", line 19, in
> session.close()
> File "", line 6, in close
> File "/usr/lib/python2.6/site-packages/qpid/messaging/endpoints.py", line
> 739, in close
> self.sync(timeout=timeout)
> File "", line 6, in sync
> File "/usr/lib/python2.6/site-packages/qpid/messaging/endpoints.py", line
> 731, in sync
> if not self._ewait(lambda: not self.outgoing and not self.acked,
> timeout=timeout):
> File "/usr/lib/python2.6/site-packages/qpid/messaging/endpoints.py", line
> 567, in _ewait
> self.check_error()
> File "/usr/lib/python2.6/site-packages/qpid/messaging/endpoints.py", line
> 556, in check_error
> raise self.error
> UnauthorizedAccess: unauthorized-access: ACL denied Queue subscribe request
> from guest@QPID (qpid/broker/SessionAdapter.cpp:399)(403)
>
> Connection close failed with exception
> Traceback (most recent call last):
> File "ACL_denial_session-hang.py", line 25, in
> connection.close()
> File "", line 6, in close
> File "/usr/lib/python2.6/site-packages/qpid/messaging/endpoints.py", line
> 316, in close
> ssn.close(timeout=timeout)
> File "", line 6, in close
> File "/usr/lib/python2.6/site-packages/qpid/messaging/endpoints.py", line
> 739, in close
> self.sync(timeout=timeout)
> File "", line 6, in sync
> File "/usr/lib/python2.6/site-packages/qpid/messaging/endpoints.py", line
> 731, in sync
> if not self._ewait(lambda: not self.outgoing and not self.acked,
> timeout=timeout):
> File "/usr/lib/python2.6/site-packages/qpid/messaging/endpoints.py", line
> 567, in _ewait
> self.check_error()
> File "/usr/lib/python2.6/site-packages/qpid/messaging/endpoints.py", line
> 556, in check_error
> raise self.error
> UnauthorizedAccess: unauthorized-access: ACL denied Queue subscribe request
> from guest@QPID (qpid/broker/SessionAdapter.cpp:399)(403)
> Expected results:
> Just the first exception is printed - when the "session.receiver" fails due
> to ACL.
> Additional info:
> Some hints for fixing it:
> - session object is properly closed. Just an attempt to close it again raises
> that exception. When trying to close a closed session without an ACL deny, no
> exception is raised
> - connection object is prope
[jira] [Created] (QPID-5251) [AMQP 1.0] allow create-on-demand through broker configuration
Gordon Sim created QPID-5251: Summary: [AMQP 1.0] allow create-on-demand through broker configuration Key: QPID-5251 URL: https://issues.apache.org/jira/browse/QPID-5251 Project: Qpid Issue Type: Bug Components: C++ Broker Affects Versions: 0.24 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: Future Though often it is better to have explicit configuration with errors raised when attempting to send to or receive from non-existent nodes, there are occasions when creating those nodes on demand would be preferable. The aim here is to add a mechanism to qpidd that will allow policies to be created that define which parts of the node 'namespace' get created on demand and what properties to apply to them. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-4984) Linear File Allocation for the Linux AIO Store
[ https://issues.apache.org/jira/browse/QPID-4984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13801791#comment-13801791 ] ASF subversion and git services commented on QPID-4984: --- Commit 1534627 from [~kpvdr] in branch 'qpid/branches/linearstore' [ https://svn.apache.org/r1534627 ] QPID-4984: WIP - Merge from trunk r.1534626. > Linear File Allocation for the Linux AIO Store > -- > > Key: QPID-4984 > URL: https://issues.apache.org/jira/browse/QPID-4984 > Project: Qpid > Issue Type: Improvement > Components: C++ Broker >Reporter: Ted Ross >Assignee: Kim van der Riet > > This Jira is for a proposed change to the AIO "legacy" store in the Qpid C++ > Broker. > Rather than pre-allocating store files in a fixed-size ring buffer (per > queue), the linear store allocates files to queue journals on an as-needed > basis, freeing them to a free-pool when no longer needed (i.e. all stored > messages have been dequeued). > The development is ongoing in a branch called "linearstore". -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-5250) Connection exceptions should specify the underlying connection failure
[
https://issues.apache.org/jira/browse/QPID-5250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darryl L. Pierce reassigned QPID-5250:
--
Assignee: Darryl L. Pierce
> Connection exceptions should specify the underlying connection failure
> --
>
> Key: QPID-5250
> URL: https://issues.apache.org/jira/browse/QPID-5250
> Project: Qpid
> Issue Type: New Feature
> Components: Ruby Client
>Affects Versions: 0.24
>Reporter: Greg Blomquist
>Assignee: Darryl L. Pierce
>
> I setup a test with the following scenario:
> installed rabbitmq-server
> installed qpidd
> started rabbitmq-server
> installed qpid_messaging gem
> installed amqp gem (rabbit)
> attempt to open connection to qpid
> In this scenario, the qpid client code outputs:
> {{2013-10-22 08:36:10 [System] error Caught exception in state: 3 with event:
> 1: Unsupported version: 0-9 supported version 0-10
> (/builddir/build/BUILD/qpid-0.24/cpp/src/qpid/client/TCPConnector.cpp:290)}}
> {{2013-10-22 08:36:10 [Client] warning Connection
> [10.13.129.81:33053-10.13.128.23:5672] closed}}
> After this output, it throws a generic {{MessagingError}}:
> {{#}}
> The problem is that by the time my ruby code catches the exception, the
> underlying reason for the connection failure has been lost. My ruby code
> never learns that the reason for the connection failure is because of a
> server amqp version mismatch.
> Take another scenario:
> stop rabbitmq-server (now, no amqp service is running)
> attempt to open connection to qpid
> In this scenario, the qpid client code outputs:
> {{2013-10-22 08:38:55 [Network] warning Connect failed: Connection refused}}
> {{2013-10-22 08:38:55 [Client] warning Connection closed}}
> After this output, it again throws a generic {{MessagingError}}:
> {{MessagingError: Failed to connect (reconnect disabled)}}
> It's impossible to tell from the exception thrown by the qpid client whether
> the underlying connection problem is because there is no service listening on
> the amqp port, or whether there is a service listening but it implements a
> different version of the amqp spec.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-5250) Connection exceptions should specify the underlying connection failure
Greg Blomquist created QPID-5250:
Summary: Connection exceptions should specify the underlying
connection failure
Key: QPID-5250
URL: https://issues.apache.org/jira/browse/QPID-5250
Project: Qpid
Issue Type: New Feature
Components: Ruby Client
Affects Versions: 0.24
Reporter: Greg Blomquist
I setup a test with the following scenario:
installed rabbitmq-server
installed qpidd
started rabbitmq-server
installed qpid_messaging gem
installed amqp gem (rabbit)
attempt to open connection to qpid
In this scenario, the qpid client code outputs:
{{2013-10-22 08:36:10 [System] error Caught exception in state: 3 with event:
1: Unsupported version: 0-9 supported version 0-10
(/builddir/build/BUILD/qpid-0.24/cpp/src/qpid/client/TCPConnector.cpp:290)}}
{{2013-10-22 08:36:10 [Client] warning Connection
[10.13.129.81:33053-10.13.128.23:5672] closed}}
After this output, it throws a generic {{MessagingError}}:
{{#}}
The problem is that by the time my ruby code catches the exception, the
underlying reason for the connection failure has been lost. My ruby code never
learns that the reason for the connection failure is because of a server amqp
version mismatch.
Take another scenario:
stop rabbitmq-server (now, no amqp service is running)
attempt to open connection to qpid
In this scenario, the qpid client code outputs:
{{2013-10-22 08:38:55 [Network] warning Connect failed: Connection refused}}
{{2013-10-22 08:38:55 [Client] warning Connection closed}}
After this output, it again throws a generic {{MessagingError}}:
{{MessagingError: Failed to connect (reconnect disabled)}}
It's impossible to tell from the exception thrown by the qpid client whether
the underlying connection problem is because there is no service listening on
the amqp port, or whether there is a service listening but it implements a
different version of the amqp spec.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5246) ACL treats DeleteQueue as a Reject Queue
[
https://issues.apache.org/jira/browse/QPID-5246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim resolved QPID-5246.
--
Resolution: Fixed
> ACL treats DeleteQueue as a Reject Queue
>
>
> Key: QPID-5246
> URL: https://issues.apache.org/jira/browse/QPID-5246
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
>Affects Versions: 0.24
>Reporter: Adrian Flowers
>Assignee: Gordon Sim
> Labels: ACL
>
> ACL does not yet support the deleteQueue policy ("self-destruct").
> There is no option available to allow the creation of self-destruct queues as
> ACL only recognizes the following Queue policy types: ring, ring_strict,
> flow_to_disk, reject.
> Additionally, if the ACL rules specify to deny the creation of a "reject"
> queue, then a deleteQueue is also denied.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-5246) ACL treats DeleteQueue as a Reject Queue
[
https://issues.apache.org/jira/browse/QPID-5246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim updated QPID-5246:
-
Fix Version/s: 0.25
> ACL treats DeleteQueue as a Reject Queue
>
>
> Key: QPID-5246
> URL: https://issues.apache.org/jira/browse/QPID-5246
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
>Affects Versions: 0.24
>Reporter: Adrian Flowers
>Assignee: Gordon Sim
> Labels: ACL
> Fix For: 0.25
>
>
> ACL does not yet support the deleteQueue policy ("self-destruct").
> There is no option available to allow the creation of self-destruct queues as
> ACL only recognizes the following Queue policy types: ring, ring_strict,
> flow_to_disk, reject.
> Additionally, if the ACL rules specify to deny the creation of a "reject"
> queue, then a deleteQueue is also denied.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5246) ACL treats DeleteQueue as a Reject Queue
[
https://issues.apache.org/jira/browse/QPID-5246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13801758#comment-13801758
]
ASF subversion and git services commented on QPID-5246:
---
Commit 1534613 from [~gsim] in branch 'qpid/trunk'
[ https://svn.apache.org/r1534613 ]
QPID-5246: update ACL code to recognise self-destruct policy
> ACL treats DeleteQueue as a Reject Queue
>
>
> Key: QPID-5246
> URL: https://issues.apache.org/jira/browse/QPID-5246
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
>Affects Versions: 0.24
>Reporter: Adrian Flowers
>Assignee: Gordon Sim
> Labels: ACL
>
> ACL does not yet support the deleteQueue policy ("self-destruct").
> There is no option available to allow the creation of self-destruct queues as
> ACL only recognizes the following Queue policy types: ring, ring_strict,
> flow_to_disk, reject.
> Additionally, if the ACL rules specify to deny the creation of a "reject"
> queue, then a deleteQueue is also denied.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPID-5246) ACL treats DeleteQueue as a Reject Queue
[
https://issues.apache.org/jira/browse/QPID-5246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim reassigned QPID-5246:
Assignee: Gordon Sim
> ACL treats DeleteQueue as a Reject Queue
>
>
> Key: QPID-5246
> URL: https://issues.apache.org/jira/browse/QPID-5246
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
>Affects Versions: 0.24
>Reporter: Adrian Flowers
>Assignee: Gordon Sim
> Labels: ACL
>
> ACL does not yet support the deleteQueue policy ("self-destruct").
> There is no option available to allow the creation of self-destruct queues as
> ACL only recognizes the following Queue policy types: ring, ring_strict,
> flow_to_disk, reject.
> Additionally, if the ACL rules specify to deny the creation of a "reject"
> queue, then a deleteQueue is also denied.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-5248) [AMQP 1.0] non-autodeleted,non-shared subscription queues should be deleted when receiver is explicitly closed
[ https://issues.apache.org/jira/browse/QPID-5248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-5248. -- Resolution: Fixed > [AMQP 1.0] non-autodeleted,non-shared subscription queues should be deleted > when receiver is explicitly closed > -- > > Key: QPID-5248 > URL: https://issues.apache.org/jira/browse/QPID-5248 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Affects Versions: 0.24 >Reporter: Gordon Sim >Assignee: Gordon Sim > Fix For: 0.25 > > -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5248) [AMQP 1.0] non-autodeleted,non-shared subscription queues should be deleted when receiver is explicitly closed
[ https://issues.apache.org/jira/browse/QPID-5248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13801698#comment-13801698 ] ASF subversion and git services commented on QPID-5248: --- Commit 1534594 from [~gsim] in branch 'qpid/trunk' [ https://svn.apache.org/r1534594 ] QPID-5248: cleanup subscription queue if needed on explicit detach > [AMQP 1.0] non-autodeleted,non-shared subscription queues should be deleted > when receiver is explicitly closed > -- > > Key: QPID-5248 > URL: https://issues.apache.org/jira/browse/QPID-5248 > Project: Qpid > Issue Type: Bug > Components: C++ Broker >Affects Versions: 0.24 >Reporter: Gordon Sim >Assignee: Gordon Sim > Fix For: 0.25 > > -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5232) [AMQP 1.0] receiver links from exchanges should be unreliable by default
[ https://issues.apache.org/jira/browse/QPID-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13801697#comment-13801697 ] ASF subversion and git services commented on QPID-5232: --- Commit 1534593 from [~gsim] in branch 'qpid/trunk' [ https://svn.apache.org/r1534593 ] QPID-5232: fix handling of autodelete for subscription queues of default reliability > [AMQP 1.0] receiver links from exchanges should be unreliable by default > > > Key: QPID-5232 > URL: https://issues.apache.org/jira/browse/QPID-5232 > Project: Qpid > Issue Type: Bug > Components: C++ Broker, C++ Client >Affects Versions: 0.24 >Reporter: Gordon Sim >Assignee: Gordon Sim > Fix For: 0.25 > > > and also use autodelete queues by default. -- This message was sent by Atlassian JIRA (v6.1#6144) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: i got error in below .. how to open lock file
On 10/21/2013 06:57 AM, Naresh Maram wrote: 2013-10-21 11:25:53 [Unspecified] notice Cannot stop broker: Cannot open lock file /home/naresh/.qpidd/qpidd.5672.pid: No such file or directory That usually means that qpidd was not started in daemon mode on port 5672. - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-5225) qpid address MalformedAddress for parentheses
[
https://issues.apache.org/jira/browse/QPID-5225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13801650#comment-13801650
]
Kai Qiang Wu commented on QPID-5225:
Hi Gordon, After some consideration, I don't want to use such Quoting method,
since it can bring other issue for the Openstack code, since it pass str
directly,
create(binary='nova-compute',
host=name,
manager=self.manager)
that create fun will be used to create qpid consumer, which use such name as
part of node topic
node_topic = '%s.%s' % (self.topic, self.host)
Other parts code would call get(host) method, which host is just the str,
If added '' for host str, it means you need manual intelligent check for such
str with '', you need hack that
for example: 'testhe''(bill)', it is not easy to directly get testhe''(bill),
since it also includes ''.
So considering the harmful and dreadful thing, I will not use that way, and
only pass to qpid address with pattern. (follow hostname pattern, the compute
hostname is a standard. I think qpid should use that directly, Not with special
( involved)
Thanks
> qpid address MalformedAddress for parentheses
> -
>
> Key: QPID-5225
> URL: https://issues.apache.org/jira/browse/QPID-5225
> Project: Qpid
> Issue Type: Bug
> Environment: Ubuntu 12.04
> qpid 0.14
> qpid-tools 0.12
>Reporter: Kai Qiang Wu
>
> I used Qpid Messaging API (Python), and when created(receiver) use following
> address:
> nova/compute.test,123(bill)@192.168.51.57-443 ; {"node": {"x-declare":
> {"auto-delete": true, "durable": true}, "type": "topic"}, "create": "always",
> "link": {"x-declare": {"auto-delete": false, "exclusive": false, "durable":
> false}, "durable": true, "name": "compute.test,123(bill)@192.168.51.57-443"}}
> But the qpid would complain for address parse for the error like this:
> File "/usr/lib/python2.7/dist-packages/qpid/messaging/endpoints.py", line
> 607, in receiver
>raise e
> MalformedAddress: unrecognized characters line:1,21: for that address,
> I did check, qpid doc said address BNF:
> http://qpid.apache.org/components/programming/book/section-addresses.html#section-address-string-bnf
> it not have token for "(" match, but I am confused when use qpid-config,
> I can create topic like following,
> qpid-config add exchange topic "nova/compute.test,123(bill)@192.168.51.57"
> -a admin/qpid@localhost
> So it seems not right not follow same rule, or I missed something.
> Thanks
--
This message was sent by Atlassian JIRA
(v6.1#6144)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
