[
https://issues.apache.org/jira/browse/PROTON-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16868398#comment-16868398
]
Robbie Gemmell edited comment on PROTON-2069 at 6/20/19 9:45 AM:
-----------------------------------------------------------------
In general, please use the mailing lists for questions:
[https://qpid.apache.org/discussion.html#mailing-lists.] There are more folks
there who could possibly answer, and a lot less noise from issue traffic to
drown out questions.
The documentation you link to from the broker docs is actually not for Proton's
python binding as you described/understood, but is rather for the old
'qpid-python' client for AMQP 0-10.
The old 'addr format' strings used in those examples is not used by Proton (or
the AMQP 1.0 Qpid JMS client) since it is largely reliant on AMQP 0-x protocol
functionality specific to its hard-defined 'broker model' and related commands.
AMQP 1.0 is more of a peer to peer protocol and does not enforce a broker model
in the same fashion (allowing things like Dispatch router and other things to
be done in addition to client-broker setups) nor does it define much in way of
related methods/commands for creating queues etc. There is a layered management
spec in progress, and the cpp broker has its own existing scheme of management
through use of messages.
You will either need to use management tools (or formulate management messages
yourself to similar effect, e.g see for[1] some different examples of that,
albeit in C++) to create your queues, or alternatively the broker can be
configured to auto-create things based on address policies (e.g
--queue-patterns queue.* to create queues for addresses starting queue), though
I've not used it for something like the above before. Again, the users list can
probably offer more assistance here than I can.
[1]
[http://qpid.2158936.n2.nabble.com/Client-to-broker-connection-status-using-C-API-td7680160.html]
was (Author: gemmellr):
In general, please use the mailing lists for questions:
[https://qpid.apache.org/discussion.html#mailing-lists.] There are more folks
there who could possibly answer, and a lot less noise from issue traffic to
drown out questions.
The documentation you link to from the broker docs is actually not for Proton's
python binding as you described/understood, but is rather for the old
'qpid-python' client for AMQP 0-10.
The old 'addr format' strings used in those examples is not used by Proton (or
the AMQP 1.0 Qpid JMS client) since it is largely reliant on AMQP 0-x protocol
functionality specific to its hard-defined 'broker model' and related commands.
AMQP 1.0 is more of a peer to peer protocol and does not enforce a broker model
in the same fashion (allowing things like Dispatch router and other thigns to
be done in addition to client-broker setups) nor does it define much in way of
related methods/commands for creating queues etc. There is a layered management
spec in progress, and the cpp broker has its own existing scheme of management
through use of messages.
You will either need to use management tools (or formulate management messages
yourself to similar effect, e.g see for[1] some different examples of that,
albeit in C++) to create your queues, or alternatively the broker can be
configured to auto-create things based on address policies (e.g
--queue-patterns queue.* to create queues for addresses starting queue), though
I've not used it for something like the above before. Again, the users list can
probably ofer more assistant here than I can.
[1]
[http://qpid.2158936.n2.nabble.com/Client-to-broker-connection-status-using-C-API-td7680160.html]
> Can't create queue from python
> ------------------------------
>
> Key: PROTON-2069
> URL: https://issues.apache.org/jira/browse/PROTON-2069
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding
> Affects Versions: proton-c-0.28.0
> Environment: Python 3.7, python-qpid-proton==0.28.0
> qpidd -v 1.39
> Reporter: Matthias Brandt
> Priority: Major
>
> According to the [proton c++
> documentation|https://qpid.apache.org/releases/qpid-cpp-1.39.0/messaging-api/book/Message-Groups-Guide.html#idm140612067785264]
> one should be able to create a queue (in this case a group queue) like this:
> sender = connection.session().sender("msg-group-q;" +
> " \{create:always, delete:receiver," +
> " node: {x-declare: {arguments:" +
> " {'qpid.group_header_key':'THE-GROUP',"
> +
> " 'qpid.shared_msg_group':1}}}}")
>
> Expected behaviour:
> * A queue with the name msg-group-q is created on broker side
> * A sender with the address msg-group-q is created on client side
> Actual behaviour:
> * No queue is created
> * A sender with the name of the complete string and no address is created.
> Is more information needed?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
