[jira] [Closed] (QPID-6483) Messages in the acquired state with no consumers

[Keith Wall (JIRA)]

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

Keith Wall closed QPID-6483.

Resolution: Cannot Reproduce

> Messages in the acquired state with no consumers
> 
>
> Key: QPID-6483
> URL: https://issues.apache.org/jira/browse/QPID-6483
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: 0.32
>Reporter: Mark Soderquist
> Attachments: qpid.acquired.png, qpid.queue.attributes.png, 
> qpid.restart.png
>
>
> This may be a misunderstanding on my part so correct me if I'm wrong. We have 
> a situation where there are 165 messages in the acquired state but there are 
> no consumers registered. I was expecting that if there are no consumers, then 
> there cannot be any acquired locks. These messages appear to be "stuck" 
> because no other consumers can acquire them for consumption. See attached 
> screen shot.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPID-6653) Earlier Qpid Java client: receiver issue with multi-transfer pre-settled messages

[Keith Wall (JIRA)]

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

Keith Wall updated QPID-6653:
-
Fix Version/s: qpid-java-7.0.0

> Earlier Qpid Java client: receiver issue with multi-transfer pre-settled 
> messages
> -
>
> Key: QPID-6653
> URL: https://issues.apache.org/jira/browse/QPID-6653
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: 0.32
>Reporter: Xin Chen
> Fix For: qpid-java-7.0.0
>
> Attachments: ReceivingLinkEndpoint.java
>
>
> This issue is regarding the Qpid Java client released as part of the Qpid JMS 
> 0.32. https://qpid.apache.org/releases/qpid-0.32/index.html
> When the remote peer sends settled message with multiple transfer frames, it 
> could use the same delivery tag (e.g. an empty binary) for all messages. The 
> ReceivingLinkEndpoint class keeps track of both unsettled deliveries and 
> partially received deliveries in two maps, _unsettledIds and _unsettledMap. 
> When user acknowledges a message by calling Receiver.acknowledge(Message), 
> the state of the delivery is removed from both maps. This is causing a 
> problem if the user acknowledges a previously received message and a new 
> message is being partially received (because they share the same delivery 
> tag). The observed symptom is receiver stuck and NullPointerException from 
> connection's frame pump when decoding frame buffers.
> I attempted a fix by using a new variable to remember the last received 
> partial delivery, if any, and only putting unsettled deliveries into the two 
> maps. It worked in this particular scenario. The existing tests are passing 
> with this change but I am not completely sure if it has any side effects.
> I will attach a modified ReceivingLinkEndpoint.Java file so you can take a 
> look.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Closed] (QPID-6986) Management: Users should not be able to view an object to which they have no access

[Keith Wall (JIRA)]

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

Keith Wall closed QPID-6986.

Resolution: Duplicate

> Management: Users should not be able to view an object to which they have no 
> access
> ---
>
> Key: QPID-6986
> URL: https://issues.apache.org/jira/browse/QPID-6986
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Reporter: Keith Wall
> Fix For: qpid-java-6.2
>
>
> In a managed service scenario, a single Broker may hosts applications 
> belonging to different groups.   For management purposes, an operator needs 
> to be able to enter the management console and check on queues, messages, 
> exchanges etc of his application.
> However, the Broker should have the ability to restrict an operator from 
> viewing the objects of a virtual host to which he has no access permission.  
> Currently the Broker enforces CRUD permissions on all objects in the 
> hierarchy, but this does not impose restrictions on *view*.
> The view restriction needs to apply to the Web Management Console and the 
> REST-API.
> An interesting case is Connections.  Connections are children on a Port but 
> become associated with a Virtualhost.  A management user with access 
> permission a virtual host needs to be able to see the connections associated 
> with that virtual host, even if he doesn't have permission to view the Broker 
> or Port directly.
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPID-7385) Add ability to switch to Dojo's uncompressed sources to aid UI debugging

[Keith Wall (JIRA)]

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

Keith Wall updated QPID-7385:
-
Fix Version/s: qpid-java-6.1

> Add ability to switch to Dojo's uncompressed sources to aid UI debugging
> 
>
> Key: QPID-7385
> URL: https://issues.apache.org/jira/browse/QPID-7385
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Reporter: Keith Wall
>Priority: Minor
> Fix For: qpid-java-6.1
>
>
> When debugging the UI it is convenient to have the ability to switch the 
> server to serving the uncompressed Dojo javascript sources rather than the 
> default compressed ones.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Resolved] (QPID-7385) Add ability to switch to Dojo's uncompressed sources to aid UI debugging

[Keith Wall (JIRA)]

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

Keith Wall resolved QPID-7385.
--
Resolution: Fixed

> Add ability to switch to Dojo's uncompressed sources to aid UI debugging
> 
>
> Key: QPID-7385
> URL: https://issues.apache.org/jira/browse/QPID-7385
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Reporter: Keith Wall
>Priority: Minor
> Fix For: qpid-java-6.1
>
>
> When debugging the UI it is convenient to have the ability to switch the 
> server to serving the uncompressed Dojo javascript sources rather than the 
> default compressed ones.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPID-7588) [Python Client 0-8..0-91] The received message ocasionally might not be dispatched into the application queue in timely manner

[Keith Wall (JIRA)]

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

Keith Wall updated QPID-7588:
-
Status: Reviewable  (was: In Progress)

> [Python Client 0-8..0-91] The received message ocasionally might not be 
> dispatched into the application queue in timely manner
> --
>
> Key: QPID-7588
> URL: https://issues.apache.org/jira/browse/QPID-7588
> Project: Qpid
>  Issue Type: Bug
>  Components: Python Test Suite
>Affects Versions: qpid-python-1.35.0
>Reporter: Alex Rudyy
>Assignee: Keith Wall
> Fix For: qpid-cpp-1.35.1
>
> Attachments: 
> qpid_tests.broker_0_9.echo.EchoTests.test_largest_single_frame_message.broker.log,
>  qpid_tests.broker_0_9.echo.EchoTests.test_largest_single_frame_message.log
>
>
> The python test 
> {{qpid_tests.broker_0_9.echo.EchoTests.test_largest_single_frame_message}} 
> for 0.9 AMQP protocol fails occasionally with the following stack trace:
> {noformat}
> qpid_tests.broker_0_9.echo.EchoTests.test_largest_single_frame_message (from 
> (TEST-python_pre1.0.xml))
> Failing for the past 1 build (Since Failed#1256 )
> Took 14 sec.
> Stacktrace
> Error during test:  Traceback (most recent call last):
> File 
> "/home/jenkins/jenkins-slave/workspace/Qpid-Python-Java-Test/site-packages/bin/qpid-python-test",
>  line 340, in run
>   phase()
> File 
> "/home/jenkins/jenkins-slave/workspace/Qpid-Python-Java-Test/site-packages/lib/python2.7/site-packages/qpid_tests/broker_0_9/echo.py",
>  line 45, in test_largest_single_frame_message
>   self.echo_message(body)
> File 
> "/home/jenkins/jenkins-slave/workspace/Qpid-Python-Java-Test/site-packages/lib/python2.7/site-packages/qpid_tests/broker_0_9/echo.py",
>  line 61, in echo_message
>   msg = consumer.get(timeout=1)
> File 
> "/home/jenkins/jenkins-slave/workspace/Qpid-Python-Java-Test/site-packages/lib/python2.7/site-packages/qpid/queue.py",
>  line 51, in get
>   result = BaseQueue.get(self, block, timeout)
> File "/usr/lib/python2.7/Queue.py", line 176, in get
>   raise Empty
>   Empty
> {noformat}
> The client and broker logs have records of the  message being received by the 
> client in timely manner (It took 3millisecond to deliver the message). 
> However, the received message was not put into the client queue and test 
> failed.
> It is unclear at the moment whether it is an issue with threads or a bug in 
> client code. More investigation is required.
> The issue might cause sporadic timeouts in applications using 0.8...0.91 
> python API. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-7588) [Python Client 0-8..0-91] The received message ocasionally might not be dispatched into the application queue in timely manner

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-7588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15773263#comment-15773263
 ] 

ASF subversion and git services commented on QPID-7588:
---

Commit 7e0e81b175114a0c965ffa55bb7c152b93a970a8 in qpid-python's branch 
refs/heads/master from [~k-wall]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-python.git;h=7e0e81b ]

QPID-7588: [Python Test Suite] [0-8..0-91]  Allow message receive timeouts to 
be configured from the command line (-D) to accomodate slower CI environments


> [Python Client 0-8..0-91] The received message ocasionally might not be 
> dispatched into the application queue in timely manner
> --
>
> Key: QPID-7588
> URL: https://issues.apache.org/jira/browse/QPID-7588
> Project: Qpid
>  Issue Type: Bug
>  Components: Python Test Suite
>Affects Versions: qpid-python-1.35.0
>Reporter: Alex Rudyy
> Fix For: qpid-cpp-1.35.1
>
> Attachments: 
> qpid_tests.broker_0_9.echo.EchoTests.test_largest_single_frame_message.broker.log,
>  qpid_tests.broker_0_9.echo.EchoTests.test_largest_single_frame_message.log
>
>
> The python test 
> {{qpid_tests.broker_0_9.echo.EchoTests.test_largest_single_frame_message}} 
> for 0.9 AMQP protocol fails occasionally with the following stack trace:
> {noformat}
> qpid_tests.broker_0_9.echo.EchoTests.test_largest_single_frame_message (from 
> (TEST-python_pre1.0.xml))
> Failing for the past 1 build (Since Failed#1256 )
> Took 14 sec.
> Stacktrace
> Error during test:  Traceback (most recent call last):
> File 
> "/home/jenkins/jenkins-slave/workspace/Qpid-Python-Java-Test/site-packages/bin/qpid-python-test",
>  line 340, in run
>   phase()
> File 
> "/home/jenkins/jenkins-slave/workspace/Qpid-Python-Java-Test/site-packages/lib/python2.7/site-packages/qpid_tests/broker_0_9/echo.py",
>  line 45, in test_largest_single_frame_message
>   self.echo_message(body)
> File 
> "/home/jenkins/jenkins-slave/workspace/Qpid-Python-Java-Test/site-packages/lib/python2.7/site-packages/qpid_tests/broker_0_9/echo.py",
>  line 61, in echo_message
>   msg = consumer.get(timeout=1)
> File 
> "/home/jenkins/jenkins-slave/workspace/Qpid-Python-Java-Test/site-packages/lib/python2.7/site-packages/qpid/queue.py",
>  line 51, in get
>   result = BaseQueue.get(self, block, timeout)
> File "/usr/lib/python2.7/Queue.py", line 176, in get
>   raise Empty
>   Empty
> {noformat}
> The client and broker logs have records of the  message being received by the 
> client in timely manner (It took 3millisecond to deliver the message). 
> However, the received message was not put into the client queue and test 
> failed.
> It is unclear at the moment whether it is an issue with threads or a bug in 
> client code. More investigation is required.
> The issue might cause sporadic timeouts in applications using 0.8...0.91 
> python API. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Assigned] (QPID-7588) [Python Client 0-8..0-91] The received message ocasionally might not be dispatched into the application queue in timely manner

[Keith Wall (JIRA)]

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

Keith Wall reassigned QPID-7588:


Assignee: Keith Wall

> [Python Client 0-8..0-91] The received message ocasionally might not be 
> dispatched into the application queue in timely manner
> --
>
> Key: QPID-7588
> URL: https://issues.apache.org/jira/browse/QPID-7588
> Project: Qpid
>  Issue Type: Bug
>  Components: Python Test Suite
>Affects Versions: qpid-python-1.35.0
>Reporter: Alex Rudyy
>Assignee: Keith Wall
> Fix For: qpid-cpp-1.35.1
>
> Attachments: 
> qpid_tests.broker_0_9.echo.EchoTests.test_largest_single_frame_message.broker.log,
>  qpid_tests.broker_0_9.echo.EchoTests.test_largest_single_frame_message.log
>
>
> The python test 
> {{qpid_tests.broker_0_9.echo.EchoTests.test_largest_single_frame_message}} 
> for 0.9 AMQP protocol fails occasionally with the following stack trace:
> {noformat}
> qpid_tests.broker_0_9.echo.EchoTests.test_largest_single_frame_message (from 
> (TEST-python_pre1.0.xml))
> Failing for the past 1 build (Since Failed#1256 )
> Took 14 sec.
> Stacktrace
> Error during test:  Traceback (most recent call last):
> File 
> "/home/jenkins/jenkins-slave/workspace/Qpid-Python-Java-Test/site-packages/bin/qpid-python-test",
>  line 340, in run
>   phase()
> File 
> "/home/jenkins/jenkins-slave/workspace/Qpid-Python-Java-Test/site-packages/lib/python2.7/site-packages/qpid_tests/broker_0_9/echo.py",
>  line 45, in test_largest_single_frame_message
>   self.echo_message(body)
> File 
> "/home/jenkins/jenkins-slave/workspace/Qpid-Python-Java-Test/site-packages/lib/python2.7/site-packages/qpid_tests/broker_0_9/echo.py",
>  line 61, in echo_message
>   msg = consumer.get(timeout=1)
> File 
> "/home/jenkins/jenkins-slave/workspace/Qpid-Python-Java-Test/site-packages/lib/python2.7/site-packages/qpid/queue.py",
>  line 51, in get
>   result = BaseQueue.get(self, block, timeout)
> File "/usr/lib/python2.7/Queue.py", line 176, in get
>   raise Empty
>   Empty
> {noformat}
> The client and broker logs have records of the  message being received by the 
> client in timely manner (It took 3millisecond to deliver the message). 
> However, the received message was not put into the client queue and test 
> failed.
> It is unclear at the moment whether it is an issue with threads or a bug in 
> client code. More investigation is required.
> The issue might cause sporadic timeouts in applications using 0.8...0.91 
> python API. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Closed] (QPID-6122) Python test TimeoutTests occasionally hangs with selector thread failing

[Keith Wall (JIRA)]

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

Keith Wall closed QPID-6122.

Resolution: Resolved

Possible that this is resolved by work of QPID-7317. With this hope, the 
exclusion is removed.  This will be reopened if the problem recurs.

> Python test TimeoutTests occasionally hangs with selector thread failing 
> -
>
> Key: QPID-6122
> URL: https://issues.apache.org/jira/browse/QPID-6122
> Project: Qpid
>  Issue Type: Bug
>  Components: Python Client
>Affects Versions: 0.30, 0.31
> Environment: Python 2.6.9 (unknown, Sep 13 2014, 00:25:11) 
> [GCC 4.8.2 20140120 (Red Hat 4.8.2-16)] on linux2
>Reporter: Keith Wall
>Assignee: Keith Wall
>
> Running the python test suite on a new CI box reveals a sporadic hang from 
> TimeoutTests and the following stack trace written to stderr:
> {noformat}
> Exception in thread Thread-62:
>  Traceback (most recent call last):
>File "/usr/lib64/python2.6/threading.py", line 532, in __bootstrap_inner
>  self.run()
>File "/usr/lib64/python2.6/threading.py", line 484, in run
>  self.__target(*self.__args, **self.__kwargs)
>File 
> "/var/lib/jenkins/workspace/qpid-python-trunk/qpid/python/qpid/selector.py", 
> line 128, in run
> {noformat}
> It appears that the exception handing in the selector thread is at fault, at 
> least on this platform/python version (details included).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-7317) Deadlock on publish

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-7317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15773258#comment-15773258
 ] 

ASF subversion and git services commented on QPID-7317:
---

Commit 1775853 from [~k-wall] in branch 'java/trunk'
[ https://svn.apache.org/r1775853 ]

QPID-6122: [Python Test Suite] Remove test exclusion 
qpid.tests.messaging.endpoints.TimeoutTests from Java Broker 0-10 Python 
excludes file

>From this description of QPID-7317, it seems possible this is fixed.

> Deadlock on publish
> ---
>
> Key: QPID-7317
> URL: https://issues.apache.org/jira/browse/QPID-7317
> Project: Qpid
>  Issue Type: Bug
>  Components: Python Client
>Affects Versions: 0.32
> Environment: python-qpid-0.32-13.fc23.noarch
>Reporter: Brian Bouterse
>Assignee: Alan Conway
> Fix For: qpid-python-1.36.0
>
> Attachments: bad_child.py, bad_child.py, bt.txt, lsof.txt, 
> spout-hang-trace.txt, spout-hang.py, taabt.txt
>
>
> When publishing a task with qpid.messaging it deadlocks and our application 
> cannot continue. This has not been a problem for several releases, but within 
> a few days recently, another Satellite developer and I both experienced the 
> issue on separate machines, different distros. He is using a MRG built 
> pacakge (not sure of version). I am using python-qpid-0.32-13.fc23.
> Both deadlocked machines had core dumps taken on the deadlocked processes and 
> only show only 1 Qpid thread when I expect there to be 2. There are other 
> mongo threads, but those are idle as expected and not related. The traces 
> show our application calling into qpid.messaging to publish a message to the 
> message bus.
> This problem happens intermittently, and in cases where message publish is 
> successful I've verified by core dump that there are the expected 2 threads 
> for Qpid.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-6122) Python test TimeoutTests occasionally hangs with selector thread failing

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-6122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15773257#comment-15773257
 ] 

ASF subversion and git services commented on QPID-6122:
---

Commit 1775853 from [~k-wall] in branch 'java/trunk'
[ https://svn.apache.org/r1775853 ]

QPID-6122: [Python Test Suite] Remove test exclusion 
qpid.tests.messaging.endpoints.TimeoutTests from Java Broker 0-10 Python 
excludes file

>From this description of QPID-7317, it seems possible this is fixed.

> Python test TimeoutTests occasionally hangs with selector thread failing 
> -
>
> Key: QPID-6122
> URL: https://issues.apache.org/jira/browse/QPID-6122
> Project: Qpid
>  Issue Type: Bug
>  Components: Python Client
>Affects Versions: 0.30, 0.31
> Environment: Python 2.6.9 (unknown, Sep 13 2014, 00:25:11) 
> [GCC 4.8.2 20140120 (Red Hat 4.8.2-16)] on linux2
>Reporter: Keith Wall
>Assignee: Keith Wall
>
> Running the python test suite on a new CI box reveals a sporadic hang from 
> TimeoutTests and the following stack trace written to stderr:
> {noformat}
> Exception in thread Thread-62:
>  Traceback (most recent call last):
>File "/usr/lib64/python2.6/threading.py", line 532, in __bootstrap_inner
>  self.run()
>File "/usr/lib64/python2.6/threading.py", line 484, in run
>  self.__target(*self.__args, **self.__kwargs)
>File 
> "/var/lib/jenkins/workspace/qpid-python-trunk/qpid/python/qpid/selector.py", 
> line 128, in run
> {noformat}
> It appears that the exception handing in the selector thread is at fault, at 
> least on this platform/python version (details included).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPID-7429) [Python Client 0-8..0-91] Legacy Python client leaks threads when connection is closed from broker side

[Keith Wall (JIRA)]

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

Keith Wall updated QPID-7429:
-
Status: Reviewable  (was: In Progress)

> [Python Client 0-8..0-91] Legacy Python client leaks threads when connection 
> is closed from broker side
> ---
>
> Key: QPID-7429
> URL: https://issues.apache.org/jira/browse/QPID-7429
> Project: Qpid
>  Issue Type: Bug
>  Components: Python Client
>Affects Versions: 0.32, qpid-python-1.35.0
>Reporter: Alex Rudyy
>Assignee: Keith Wall
>
> Python client does not stop properly its threads when connection is closed 
> from broker side. As result, client application can leak threads and 
> eventually ran out of threads.
> It seems that writer thread from Peer is blocked on outgoing queue and never 
> exits



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPID-7429) [Python Client 0-8..0-91] Legacy Python client leaks threads when connection is closed from broker side

[Keith Wall (JIRA)]

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

Keith Wall updated QPID-7429:
-
Assignee: (was: Keith Wall)

> [Python Client 0-8..0-91] Legacy Python client leaks threads when connection 
> is closed from broker side
> ---
>
> Key: QPID-7429
> URL: https://issues.apache.org/jira/browse/QPID-7429
> Project: Qpid
>  Issue Type: Bug
>  Components: Python Client
>Affects Versions: 0.32, qpid-python-1.35.0
>Reporter: Alex Rudyy
>
> Python client does not stop properly its threads when connection is closed 
> from broker side. As result, client application can leak threads and 
> eventually ran out of threads.
> It seems that writer thread from Peer is blocked on outgoing queue and never 
> exits



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Assigned] (QPID-7429) [Python Client 0-8..0-91] Legacy Python client leaks threads when connection is closed from broker side

[Keith Wall (JIRA)]

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

Keith Wall reassigned QPID-7429:


Assignee: Keith Wall

> [Python Client 0-8..0-91] Legacy Python client leaks threads when connection 
> is closed from broker side
> ---
>
> Key: QPID-7429
> URL: https://issues.apache.org/jira/browse/QPID-7429
> Project: Qpid
>  Issue Type: Bug
>  Components: Python Client
>Affects Versions: 0.32, qpid-python-1.35.0
>Reporter: Alex Rudyy
>Assignee: Keith Wall
>
> Python client does not stop properly its threads when connection is closed 
> from broker side. As result, client application can leak threads and 
> eventually ran out of threads.
> It seems that writer thread from Peer is blocked on outgoing queue and never 
> exits



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Closed] (QPID-7254) [Python Client] Perform SSL hostname verification

[Keith Wall (JIRA)]

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

Keith Wall closed QPID-7254.

Resolution: Duplicate

> [Python Client] Perform SSL hostname verification
> -
>
> Key: QPID-7254
> URL: https://issues.apache.org/jira/browse/QPID-7254
> Project: Qpid
>  Issue Type: Improvement
>  Components: Python Client
>Reporter: Lorenz Quack
>Assignee: Lorenz Quack
>
> Currently the Python client does not perform hostname verification.
> We should add this ability. Ideally it should respect hostnames from both CN 
> and SANs and support wildcards.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-7254) [Python Client] Perform SSL hostname verification

[Keith Wall (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-7254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15773224#comment-15773224
 ] 

Keith Wall commented on QPID-7254:
--

Appears to duplicate QPID-7258.

> [Python Client] Perform SSL hostname verification
> -
>
> Key: QPID-7254
> URL: https://issues.apache.org/jira/browse/QPID-7254
> Project: Qpid
>  Issue Type: Improvement
>  Components: Python Client
>Reporter: Lorenz Quack
>Assignee: Lorenz Quack
>
> Currently the Python client does not perform hostname verification.
> We should add this ability. Ideally it should respect hostnames from both CN 
> and SANs and support wildcards.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-7588) [Python Client 0-8..0-91] The received message ocasionally might not be dispatched into the application queue in timely manner

[Keith Wall (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-7588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15773210#comment-15773210
 ] 

Keith Wall commented on QPID-7588:
--

This is probably just an environmental issue.  The Apache CI hosts can be very 
slow.  We'll factor out the timeout so the noise can be reduced.


> [Python Client 0-8..0-91] The received message ocasionally might not be 
> dispatched into the application queue in timely manner
> --
>
> Key: QPID-7588
> URL: https://issues.apache.org/jira/browse/QPID-7588
> Project: Qpid
>  Issue Type: Bug
>  Components: Python Test Suite
>Affects Versions: qpid-python-1.35.0
>Reporter: Alex Rudyy
> Fix For: qpid-cpp-1.35.1
>
> Attachments: 
> qpid_tests.broker_0_9.echo.EchoTests.test_largest_single_frame_message.broker.log,
>  qpid_tests.broker_0_9.echo.EchoTests.test_largest_single_frame_message.log
>
>
> The python test 
> {{qpid_tests.broker_0_9.echo.EchoTests.test_largest_single_frame_message}} 
> for 0.9 AMQP protocol fails occasionally with the following stack trace:
> {noformat}
> qpid_tests.broker_0_9.echo.EchoTests.test_largest_single_frame_message (from 
> (TEST-python_pre1.0.xml))
> Failing for the past 1 build (Since Failed#1256 )
> Took 14 sec.
> Stacktrace
> Error during test:  Traceback (most recent call last):
> File 
> "/home/jenkins/jenkins-slave/workspace/Qpid-Python-Java-Test/site-packages/bin/qpid-python-test",
>  line 340, in run
>   phase()
> File 
> "/home/jenkins/jenkins-slave/workspace/Qpid-Python-Java-Test/site-packages/lib/python2.7/site-packages/qpid_tests/broker_0_9/echo.py",
>  line 45, in test_largest_single_frame_message
>   self.echo_message(body)
> File 
> "/home/jenkins/jenkins-slave/workspace/Qpid-Python-Java-Test/site-packages/lib/python2.7/site-packages/qpid_tests/broker_0_9/echo.py",
>  line 61, in echo_message
>   msg = consumer.get(timeout=1)
> File 
> "/home/jenkins/jenkins-slave/workspace/Qpid-Python-Java-Test/site-packages/lib/python2.7/site-packages/qpid/queue.py",
>  line 51, in get
>   result = BaseQueue.get(self, block, timeout)
> File "/usr/lib/python2.7/Queue.py", line 176, in get
>   raise Empty
>   Empty
> {noformat}
> The client and broker logs have records of the  message being received by the 
> client in timely manner (It took 3millisecond to deliver the message). 
> However, the received message was not put into the client queue and test 
> failed.
> It is unclear at the moment whether it is an issue with threads or a bug in 
> client code. More investigation is required.
> The issue might cause sporadic timeouts in applications using 0.8...0.91 
> python API. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPID-7588) [Python Client 0-8..0-91] The received message ocasionally might not be dispatched into the application queue in timely manner

[Keith Wall (JIRA)]

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

Keith Wall updated QPID-7588:
-
Component/s: (was: Python Client)
 Python Test Suite

> [Python Client 0-8..0-91] The received message ocasionally might not be 
> dispatched into the application queue in timely manner
> --
>
> Key: QPID-7588
> URL: https://issues.apache.org/jira/browse/QPID-7588
> Project: Qpid
>  Issue Type: Bug
>  Components: Python Test Suite
>Affects Versions: qpid-python-1.35.0
>Reporter: Alex Rudyy
> Fix For: qpid-cpp-1.35.1
>
> Attachments: 
> qpid_tests.broker_0_9.echo.EchoTests.test_largest_single_frame_message.broker.log,
>  qpid_tests.broker_0_9.echo.EchoTests.test_largest_single_frame_message.log
>
>
> The python test 
> {{qpid_tests.broker_0_9.echo.EchoTests.test_largest_single_frame_message}} 
> for 0.9 AMQP protocol fails occasionally with the following stack trace:
> {noformat}
> qpid_tests.broker_0_9.echo.EchoTests.test_largest_single_frame_message (from 
> (TEST-python_pre1.0.xml))
> Failing for the past 1 build (Since Failed#1256 )
> Took 14 sec.
> Stacktrace
> Error during test:  Traceback (most recent call last):
> File 
> "/home/jenkins/jenkins-slave/workspace/Qpid-Python-Java-Test/site-packages/bin/qpid-python-test",
>  line 340, in run
>   phase()
> File 
> "/home/jenkins/jenkins-slave/workspace/Qpid-Python-Java-Test/site-packages/lib/python2.7/site-packages/qpid_tests/broker_0_9/echo.py",
>  line 45, in test_largest_single_frame_message
>   self.echo_message(body)
> File 
> "/home/jenkins/jenkins-slave/workspace/Qpid-Python-Java-Test/site-packages/lib/python2.7/site-packages/qpid_tests/broker_0_9/echo.py",
>  line 61, in echo_message
>   msg = consumer.get(timeout=1)
> File 
> "/home/jenkins/jenkins-slave/workspace/Qpid-Python-Java-Test/site-packages/lib/python2.7/site-packages/qpid/queue.py",
>  line 51, in get
>   result = BaseQueue.get(self, block, timeout)
> File "/usr/lib/python2.7/Queue.py", line 176, in get
>   raise Empty
>   Empty
> {noformat}
> The client and broker logs have records of the  message being received by the 
> client in timely manner (It took 3millisecond to deliver the message). 
> However, the received message was not put into the client queue and test 
> failed.
> It is unclear at the moment whether it is an issue with threads or a bug in 
> client code. More investigation is required.
> The issue might cause sporadic timeouts in applications using 0.8...0.91 
> python API. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPID-7588) [Python Client 0-8..0-91] The received message ocasionally might not be dispatched into the application queue in timely manner

[Keith Wall (JIRA)]

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

Keith Wall updated QPID-7588:
-
Fix Version/s: qpid-cpp-1.35.1

> [Python Client 0-8..0-91] The received message ocasionally might not be 
> dispatched into the application queue in timely manner
> --
>
> Key: QPID-7588
> URL: https://issues.apache.org/jira/browse/QPID-7588
> Project: Qpid
>  Issue Type: Bug
>  Components: Python Test Suite
>Affects Versions: qpid-python-1.35.0
>Reporter: Alex Rudyy
> Fix For: qpid-cpp-1.35.1
>
> Attachments: 
> qpid_tests.broker_0_9.echo.EchoTests.test_largest_single_frame_message.broker.log,
>  qpid_tests.broker_0_9.echo.EchoTests.test_largest_single_frame_message.log
>
>
> The python test 
> {{qpid_tests.broker_0_9.echo.EchoTests.test_largest_single_frame_message}} 
> for 0.9 AMQP protocol fails occasionally with the following stack trace:
> {noformat}
> qpid_tests.broker_0_9.echo.EchoTests.test_largest_single_frame_message (from 
> (TEST-python_pre1.0.xml))
> Failing for the past 1 build (Since Failed#1256 )
> Took 14 sec.
> Stacktrace
> Error during test:  Traceback (most recent call last):
> File 
> "/home/jenkins/jenkins-slave/workspace/Qpid-Python-Java-Test/site-packages/bin/qpid-python-test",
>  line 340, in run
>   phase()
> File 
> "/home/jenkins/jenkins-slave/workspace/Qpid-Python-Java-Test/site-packages/lib/python2.7/site-packages/qpid_tests/broker_0_9/echo.py",
>  line 45, in test_largest_single_frame_message
>   self.echo_message(body)
> File 
> "/home/jenkins/jenkins-slave/workspace/Qpid-Python-Java-Test/site-packages/lib/python2.7/site-packages/qpid_tests/broker_0_9/echo.py",
>  line 61, in echo_message
>   msg = consumer.get(timeout=1)
> File 
> "/home/jenkins/jenkins-slave/workspace/Qpid-Python-Java-Test/site-packages/lib/python2.7/site-packages/qpid/queue.py",
>  line 51, in get
>   result = BaseQueue.get(self, block, timeout)
> File "/usr/lib/python2.7/Queue.py", line 176, in get
>   raise Empty
>   Empty
> {noformat}
> The client and broker logs have records of the  message being received by the 
> client in timely manner (It took 3millisecond to deliver the message). 
> However, the received message was not put into the client queue and test 
> failed.
> It is unclear at the moment whether it is an issue with threads or a bug in 
> client code. More investigation is required.
> The issue might cause sporadic timeouts in applications using 0.8...0.91 
> python API. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (PROTON-1375) Compile without warnings under clang 4.0

[Andrew Stitcher (JIRA)]

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

Andrew Stitcher updated PROTON-1375:

Description: 
The following warnings prevent me from compiling proton-c with clang 4.0 snaphot

# (/) /qpid-proton-fuzz/proton-c/src/tests/object.c:60:16: error: passing an 
object that undergoes default argument promotion to 'va_start' has undefined 
behavior
# (x) /test/qpid-proton/proton-c/bindings/cpp/include/proton/message.hpp:51:11: 
error: instantiation of function
  'proton::internal::cached_map::cached_map' required here, but no definition is

see complete error messages in comments below

  was:
The following warnings prevent me from compiling proton-c with clang 4.0 snaphot

# (/) /qpid-proton-fuzz/proton-c/src/tests/object.c:60:16: error: passing an 
object that undergoes default argument promotion to 'va_start' has undefined 
behavior
# (off) 
/test/qpid-proton/proton-c/bindings/cpp/include/proton/message.hpp:51:11: 
error: instantiation of function
  'proton::internal::cached_map::cached_map' required here, but no definition is

see complete error messages in comments below


> Compile without warnings under clang 4.0
> 
>
> Key: PROTON-1375
> URL: https://issues.apache.org/jira/browse/PROTON-1375
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: proton-c
>Affects Versions: 0.16.0
> Environment: Debian Jessie. Install latest clang 4.0 snapshot from 
> http://apt.llvm.org/.
>Reporter: Jiri Danek
>Assignee: Andrew Stitcher
>Priority: Minor
> Fix For: 0.17.0
>
>
> The following warnings prevent me from compiling proton-c with clang 4.0 
> snaphot
> # (/) /qpid-proton-fuzz/proton-c/src/tests/object.c:60:16: error: passing an 
> object that undergoes default argument promotion to 'va_start' has undefined 
> behavior
> # (x) 
> /test/qpid-proton/proton-c/bindings/cpp/include/proton/message.hpp:51:11: 
> error: instantiation of function
>   'proton::internal::cached_map proton::scalar>::cached_map' required here, but no definition is
> see complete error messages in comments below



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (PROTON-1379) Compile without warnings under g++ 7.0

[Andrew Stitcher (JIRA)]

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

Andrew Stitcher updated PROTON-1379:

Description: 
The following error prevents from compiling the cpp binding with g++ 7.0 snaphot

# (on) /qpid-proton/proton-c/bindings/cpp/include/proton/container.hpp:219:48: 
error: 'std::function' has not been declared

see complete error messages in comments below

  was:
The following error prevents from compiling the cpp binding with g++ 7.0 snaphot

# (off) /qpid-proton/proton-c/bindings/cpp/include/proton/container.hpp:219:48: 
error: 'std::function' has not been declared

see complete error messages in comments below


> Compile without warnings under g++ 7.0
> --
>
> Key: PROTON-1379
> URL: https://issues.apache.org/jira/browse/PROTON-1379
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: 0.17.0
> Environment: Debian testing. GCC nightly build from 
> https://hub.docker.com/r/jdanekrh/nightly-gccgo-trunk-docker-image/
>Reporter: Jiri Danek
>Assignee: Andrew Stitcher
>Priority: Minor
>  Labels: patch
> Fix For: 0.17.0
>
>
> The following error prevents from compiling the cpp binding with g++ 7.0 
> snaphot
> # (on) 
> /qpid-proton/proton-c/bindings/cpp/include/proton/container.hpp:219:48: 
> error: 'std::function' has not been declared
> see complete error messages in comments below



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (PROTON-1379) Compile without warnings under g++ 7.0

[Andrew Stitcher (JIRA)]

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

Andrew Stitcher updated PROTON-1379:

Description: 
The following error prevents from compiling the cpp binding with g++ 7.0 snaphot

# (/) /qpid-proton/proton-c/bindings/cpp/include/proton/container.hpp:219:48: 
error: 'std::function' has not been declared

see complete error messages in comments below

  was:
The following error prevents from compiling the cpp binding with g++ 7.0 snaphot

# (on) /qpid-proton/proton-c/bindings/cpp/include/proton/container.hpp:219:48: 
error: 'std::function' has not been declared

see complete error messages in comments below


> Compile without warnings under g++ 7.0
> --
>
> Key: PROTON-1379
> URL: https://issues.apache.org/jira/browse/PROTON-1379
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: 0.17.0
> Environment: Debian testing. GCC nightly build from 
> https://hub.docker.com/r/jdanekrh/nightly-gccgo-trunk-docker-image/
>Reporter: Jiri Danek
>Assignee: Andrew Stitcher
>Priority: Minor
>  Labels: patch
> Fix For: 0.17.0
>
>
> The following error prevents from compiling the cpp binding with g++ 7.0 
> snaphot
> # (/) /qpid-proton/proton-c/bindings/cpp/include/proton/container.hpp:219:48: 
> error: 'std::function' has not been declared
> see complete error messages in comments below



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Resolved] (PROTON-1379) Compile without warnings under g++ 7.0

[Andrew Stitcher (JIRA)]

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

Andrew Stitcher resolved PROTON-1379.
-
Resolution: Fixed

> Compile without warnings under g++ 7.0
> --
>
> Key: PROTON-1379
> URL: https://issues.apache.org/jira/browse/PROTON-1379
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: 0.17.0
> Environment: Debian testing. GCC nightly build from 
> https://hub.docker.com/r/jdanekrh/nightly-gccgo-trunk-docker-image/
>Reporter: Jiri Danek
>Assignee: Andrew Stitcher
>Priority: Minor
>  Labels: patch
> Fix For: 0.17.0
>
>
> The following error prevents from compiling the cpp binding with g++ 7.0 
> snaphot
> # (off) 
> /qpid-proton/proton-c/bindings/cpp/include/proton/container.hpp:219:48: 
> error: 'std::function' has not been declared
> see complete error messages in comments below



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[GitHub] qpid-proton pull request #92: PROTON-1379: [C++ binding] Add #if'd #include ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/qpid-proton/pull/92


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1379) Compile without warnings under g++ 7.0

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15773150#comment-15773150
 ] 

ASF GitHub Bot commented on PROTON-1379:


Github user asfgit closed the pull request at:

https://github.com/apache/qpid-proton/pull/92


> Compile without warnings under g++ 7.0
> --
>
> Key: PROTON-1379
> URL: https://issues.apache.org/jira/browse/PROTON-1379
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: 0.17.0
> Environment: Debian testing. GCC nightly build from 
> https://hub.docker.com/r/jdanekrh/nightly-gccgo-trunk-docker-image/
>Reporter: Jiri Danek
>Assignee: Andrew Stitcher
>Priority: Minor
>  Labels: patch
> Fix For: 0.17.0
>
>
> The following error prevents from compiling the cpp binding with g++ 7.0 
> snaphot
> # (off) 
> /qpid-proton/proton-c/bindings/cpp/include/proton/container.hpp:219:48: 
> error: 'std::function' has not been declared
> see complete error messages in comments below



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1379) Compile without warnings under g++ 7.0

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15773149#comment-15773149
 ] 

ASF subversion and git services commented on PROTON-1379:
-

Commit cd6ecc5fd9cc29cd2fa594c59166dd9d432fd4b9 in qpid-proton's branch 
refs/heads/master from [~jdanek]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=cd6ecc5 ]

PROTON-1379: [C++ binding] Add #if'd #include 
[closes #92]


> Compile without warnings under g++ 7.0
> --
>
> Key: PROTON-1379
> URL: https://issues.apache.org/jira/browse/PROTON-1379
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: 0.17.0
> Environment: Debian testing. GCC nightly build from 
> https://hub.docker.com/r/jdanekrh/nightly-gccgo-trunk-docker-image/
>Reporter: Jiri Danek
>Assignee: Andrew Stitcher
>Priority: Minor
>  Labels: patch
> Fix For: 0.17.0
>
>
> The following error prevents from compiling the cpp binding with g++ 7.0 
> snaphot
> # (off) 
> /qpid-proton/proton-c/bindings/cpp/include/proton/container.hpp:219:48: 
> error: 'std::function' has not been declared
> see complete error messages in comments below



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (DISPATCH-599) Link routing : messages is not transferred if sender detach link immediately

[Paolo Patierno (JIRA)]

Paolo Patierno created DISPATCH-599:
---

 Summary: Link routing : messages is not transferred if sender 
detach link immediately
 Key: DISPATCH-599
 URL: https://issues.apache.org/jira/browse/DISPATCH-599
 Project: Qpid Dispatch
  Issue Type: Bug
Affects Versions: 0.8.0
Reporter: Paolo Patierno


Hi,

using link routing, if the sender sends a message and detach the link 
immediately after that, the message isn't transferred to the receiver (just 
dropped by the router ?). Following what I see from log :

[0x7fd30803e4c0]:0 <- @transfer(20) [handle=3, delivery-id=1, 
delivery-tag=b"1", message-format=0] (66) 
"\x00Sp\xc0\x06\x05B@@@C\x00Sr\xc1\x15\x04\xa3\x05x-qosT\x00\xa3\x08x-retainB\x00Ss\xc0\x0e\x03T\xff@\xa1\x08my_topic\x00Su\xa0\x05Hello"
[0x7fd30803e4c0]:0 <- @detach(22) [handle=3, closed=true]
[0x7fd30803e4c0]:0 <- @close(24) []
[0x7fd30803e4c0]:  <- EOS
[0x7fd30803e4c0]:0 -> @close(24) []
[0x7fd308021780]:1 -> @detach(22) [handle=0, closed=true]
[0x7fd30803e4c0]:  -> EOS

It doesn't happen with message routing.

Thanks,
Paolo.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1379) Compile without warnings under g++ 7.0

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15773091#comment-15773091
 ] 

ASF GitHub Bot commented on PROTON-1379:


Github user astitcher commented on the issue:

https://github.com/apache/qpid-proton/pull/92
  
Yep this looks like a mistake - I 'll pull it in.


> Compile without warnings under g++ 7.0
> --
>
> Key: PROTON-1379
> URL: https://issues.apache.org/jira/browse/PROTON-1379
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: 0.17.0
> Environment: Debian testing. GCC nightly build from 
> https://hub.docker.com/r/jdanekrh/nightly-gccgo-trunk-docker-image/
>Reporter: Jiri Danek
>Assignee: Andrew Stitcher
>Priority: Minor
>  Labels: patch
> Fix For: 0.17.0
>
>
> The following error prevents from compiling the cpp binding with g++ 7.0 
> snaphot
> # (off) 
> /qpid-proton/proton-c/bindings/cpp/include/proton/container.hpp:219:48: 
> error: 'std::function' has not been declared
> see complete error messages in comments below



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[GitHub] qpid-proton issue #92: PROTON-1379: [C++ binding] Add #if'd #include

[astitcher]

Github user astitcher commented on the issue:

https://github.com/apache/qpid-proton/pull/92
  
Yep this looks like a mistake - I 'll pull it in.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-6028) [Java Broker] Configured model objects should have only one parent

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15773006#comment-15773006
 ] 

ASF subversion and git services commented on QPID-6028:
---

Commit 1775841 from [~k-wall] in branch 'java/trunk'
[ https://svn.apache.org/r1775841 ]

QPID-6028 : [Java Broker] Fix failing BDBUpgradeTest

> [Java Broker] Configured model objects should have only one parent
> --
>
> Key: QPID-6028
> URL: https://issues.apache.org/jira/browse/QPID-6028
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Reporter: Rob Godfrey
>Assignee: Keith Wall
> Fix For: qpid-java-7.0.0
>
>
> Currently it is possible for a configured object to be defined as having 
> multiple parents (of different classes)
> Thus a binding has a "queue" parent and an "exchange" parent, a consumer has 
> a "session" parent and a "queue" parent, a virtualhostalias has a "port" 
> parent and a virtialhost parent.
> This design should be changed.
> h5. Bindings
> Bindings should have a single exchange parent with the queue being an 
> attribute (note that this probably also requires adding binding-key as an 
> attribute and setting the name to queue/binding-key or some such.  
> Exchange-wide validation on the binding-key will be required)
> h5. Consumers
> Since in AMQP 1.0 a link endpoint may outlive the session that created it, it 
> makes sense for the parent of the Consumer to be the Queue.  The Session will 
> be a (derived) attribute of the Consumer.
> h5. VirtualhostAliases
> The primary parent of the virtualhostalias should be the (amqp) port.  The 
> virtualHost should be an attribute.  On creating a VirtualHost we should 
> offer to create an alias for the virtual host on all existing ports with the 
> host name as the alias.  On creating a port we should offer to create aliases 
> for each of the existing virtualhosts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (PROTON-1379) Compile without warnings under g++ 7.0

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/PROTON-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15772995#comment-15772995
 ] 

ASF GitHub Bot commented on PROTON-1379:


GitHub user jdanekrh opened a pull request:

https://github.com/apache/qpid-proton/pull/92

PROTON-1379: [C++ binding] Add #if'd #include 



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/rh-messaging-qe/qpid-proton jd_function

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/qpid-proton/pull/92.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #92


commit 3a94799237f2647844dfffb6b1affc2b70f6f485
Author: Jiri Danek 
Date:   2016-12-23T14:18:28Z

PROTON-1379: [C++ binding] Add #if'd #include 




> Compile without warnings under g++ 7.0
> --
>
> Key: PROTON-1379
> URL: https://issues.apache.org/jira/browse/PROTON-1379
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: 0.17.0
> Environment: Debian testing. GCC nightly build from 
> https://hub.docker.com/r/jdanekrh/nightly-gccgo-trunk-docker-image/
>Reporter: Jiri Danek
>Assignee: Andrew Stitcher
>Priority: Minor
>  Labels: patch
> Fix For: 0.17.0
>
>
> The following error prevents from compiling the cpp binding with g++ 7.0 
> snaphot
> # (off) 
> /qpid-proton/proton-c/bindings/cpp/include/proton/container.hpp:219:48: 
> error: 'std::function' has not been declared
> see complete error messages in comments below



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[GitHub] qpid-proton pull request #92: PROTON-1379: [C++ binding] Add #if'd #include ...

[jdanekrh]

GitHub user jdanekrh opened a pull request:

https://github.com/apache/qpid-proton/pull/92

PROTON-1379: [C++ binding] Add #if'd #include 



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/rh-messaging-qe/qpid-proton jd_function

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/qpid-proton/pull/92.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #92


commit 3a94799237f2647844dfffb6b1affc2b70f6f485
Author: Jiri Danek 
Date:   2016-12-23T14:18:28Z

PROTON-1379: [C++ binding] Add #if'd #include 




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (PROTON-1379) Compile without warnings under g++ 7.0

[Jiri Danek (JIRA)]

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

Jiri Danek updated PROTON-1379:
---
  Flags: Patch
 Labels: patch  (was: )
Description: 
The following error prevents from compiling the cpp binding with g++ 7.0 snaphot

# (off) /qpid-proton/proton-c/bindings/cpp/include/proton/container.hpp:219:48: 
error: 'std::function' has not been declared

see complete error messages in comments below

  was:
The following warnings prevent me from compiling proton-c with clang 4.0 snaphot

# (/) /qpid-proton-fuzz/proton-c/src/tests/object.c:60:16: error: passing an 
object that undergoes default argument promotion to 'va_start' has undefined 
behavior
# (off) 
/test/qpid-proton/proton-c/bindings/cpp/include/proton/message.hpp:51:11: 
error: instantiation of function
  'proton::internal::cached_map::cached_map' required here, but no definition is

see complete error messages in comments below


In output of {VERBOSE=1 make}:

{noformat}
cd /qpid-proton/build/proton-c/bindings/cpp && /usr/local/bin/c++   
-DPN_CPP_HAS_LONG_LONG=1 -DPN_CPP_HAS_STD_PTR=1 -Dqpid_proton_cpp_EXPORTS 
-I/qpid-proton/build/proton-c/src -I/qpid-proton/build/proton-c/include 
-I/qpid-proton/proton-c/src -I/qpid-proton/proton-c/include 
-I/qpid-proton/proton-c/bindings/cpp/include 
-I/qpid-proton/proton-c/bindings/cpp/src/include  -std=c++11 
-fvisibility=hidden -g -fPIC   -Werror -Wall -pedantic-errors -Wno-format 
-Wno-variadic-macros -o CMakeFiles/qpid-proton-cpp.dir/src/connection.cpp.o -c 
/qpid-proton/proton-c/bindings/cpp/src/connection.cpp
In file included from 
/qpid-proton/proton-c/bindings/cpp/src/connection.cpp:25:0:
/qpid-proton/proton-c/bindings/cpp/include/proton/container.hpp:219:48: error: 
'std::function' has not been declared
 PN_CPP_EXTERN void schedule(duration, std::function);
^~~~
/qpid-proton/proton-c/bindings/cpp/include/proton/container.hpp:219:56: error: 
expected ',' or '...' before '<' token
 PN_CPP_EXTERN void schedule(duration, std::function);
^
proton-c/bindings/cpp/CMakeFiles/qpid-proton-cpp.dir/build.make:134: recipe for 
target 
'proton-c/bindings/cpp/CMakeFiles/qpid-proton-cpp.dir/src/connection.cpp.o' 
failed
{noformat}

I do not understand why it did not appear with previous GCC or clang versions 
(I tried them also with {{CXXFLAGS="-std=c++11"}}), but the error looks real 
(and not just regression in GCC itself).

> Compile without warnings under g++ 7.0
> --
>
> Key: PROTON-1379
> URL: https://issues.apache.org/jira/browse/PROTON-1379
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: 0.17.0
> Environment: Debian testing. GCC nightly build from 
> https://hub.docker.com/r/jdanekrh/nightly-gccgo-trunk-docker-image/
>Reporter: Jiri Danek
>Assignee: Andrew Stitcher
>Priority: Minor
>  Labels: patch
> Fix For: 0.17.0
>
>
> The following error prevents from compiling the cpp binding with g++ 7.0 
> snaphot
> # (off) 
> /qpid-proton/proton-c/bindings/cpp/include/proton/container.hpp:219:48: 
> error: 'std::function' has not been declared
> see complete error messages in comments below



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (PROTON-1379) Compile without warnings under g++ 7.0

[Jiri Danek (JIRA)]

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

Jiri Danek updated PROTON-1379:
---
Environment: Debian testing. GCC nightly build from 
https://hub.docker.com/r/jdanekrh/nightly-gccgo-trunk-docker-image/  (was: 
Debian Jessie. Install latest clang 4.0 snapshot from http://apt.llvm.org/.)

> Compile without warnings under g++ 7.0
> --
>
> Key: PROTON-1379
> URL: https://issues.apache.org/jira/browse/PROTON-1379
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: 0.17.0
> Environment: Debian testing. GCC nightly build from 
> https://hub.docker.com/r/jdanekrh/nightly-gccgo-trunk-docker-image/
>Reporter: Jiri Danek
>Assignee: Andrew Stitcher
>Priority: Minor
> Fix For: 0.17.0
>
>
> The following warnings prevent me from compiling proton-c with clang 4.0 
> snaphot
> # (/) /qpid-proton-fuzz/proton-c/src/tests/object.c:60:16: error: passing an 
> object that undergoes default argument promotion to 'va_start' has undefined 
> behavior
> # (off) 
> /test/qpid-proton/proton-c/bindings/cpp/include/proton/message.hpp:51:11: 
> error: instantiation of function
>   'proton::internal::cached_map proton::scalar>::cached_map' required here, but no definition is
> see complete error messages in comments below



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (PROTON-1379) Compile without warnings under g++ 7.0

[Jiri Danek (JIRA)]

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

Jiri Danek updated PROTON-1379:
---
Component/s: (was: proton-c)
 cpp-binding

> Compile without warnings under g++ 7.0
> --
>
> Key: PROTON-1379
> URL: https://issues.apache.org/jira/browse/PROTON-1379
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: 0.17.0
> Environment: Debian Jessie. Install latest clang 4.0 snapshot from 
> http://apt.llvm.org/.
>Reporter: Jiri Danek
>Assignee: Andrew Stitcher
>Priority: Minor
> Fix For: 0.17.0
>
>
> The following warnings prevent me from compiling proton-c with clang 4.0 
> snaphot
> # (/) /qpid-proton-fuzz/proton-c/src/tests/object.c:60:16: error: passing an 
> object that undergoes default argument promotion to 'va_start' has undefined 
> behavior
> # (off) 
> /test/qpid-proton/proton-c/bindings/cpp/include/proton/message.hpp:51:11: 
> error: instantiation of function
>   'proton::internal::cached_map proton::scalar>::cached_map' required here, but no definition is
> see complete error messages in comments below



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (PROTON-1379) Compile without warnings under g++ 7.0

[Jiri Danek (JIRA)]

Jiri Danek created PROTON-1379:
--

 Summary: Compile without warnings under g++ 7.0
 Key: PROTON-1379
 URL: https://issues.apache.org/jira/browse/PROTON-1379
 Project: Qpid Proton
  Issue Type: Bug
  Components: proton-c
Affects Versions: 0.16.0
 Environment: Debian Jessie. Install latest clang 4.0 snapshot from 
http://apt.llvm.org/.
Reporter: Jiri Danek
Assignee: Andrew Stitcher
Priority: Minor
 Fix For: 0.17.0


The following warnings prevent me from compiling proton-c with clang 4.0 snaphot

# (/) /qpid-proton-fuzz/proton-c/src/tests/object.c:60:16: error: passing an 
object that undergoes default argument promotion to 'va_start' has undefined 
behavior
# (off) 
/test/qpid-proton/proton-c/bindings/cpp/include/proton/message.hpp:51:11: 
error: instantiation of function
  'proton::internal::cached_map::cached_map' required here, but no definition is

see complete error messages in comments below



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (PROTON-1379) Compile without warnings under g++ 7.0

[Jiri Danek (JIRA)]

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

Jiri Danek updated PROTON-1379:
---
Affects Version/s: (was: 0.16.0)
   0.17.0

> Compile without warnings under g++ 7.0
> --
>
> Key: PROTON-1379
> URL: https://issues.apache.org/jira/browse/PROTON-1379
> Project: Qpid Proton
>  Issue Type: Bug
>  Components: cpp-binding
>Affects Versions: 0.17.0
> Environment: Debian Jessie. Install latest clang 4.0 snapshot from 
> http://apt.llvm.org/.
>Reporter: Jiri Danek
>Assignee: Andrew Stitcher
>Priority: Minor
> Fix For: 0.17.0
>
>
> The following warnings prevent me from compiling proton-c with clang 4.0 
> snaphot
> # (/) /qpid-proton-fuzz/proton-c/src/tests/object.c:60:16: error: passing an 
> object that undergoes default argument promotion to 'va_start' has undefined 
> behavior
> # (off) 
> /test/qpid-proton/proton-c/bindings/cpp/include/proton/message.hpp:51:11: 
> error: instantiation of function
>   'proton::internal::cached_map proton::scalar>::cached_map' required here, but no definition is
> see complete error messages in comments below



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Updated] (QPID-3987) Tests broker_0_9.queue.QueueTests.test_unbind_fanout and broker_0_9.queue.QueueTests.test_unbind_headers fail with 404, 'No such binding'

[Keith Wall (JIRA)]

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

Keith Wall updated QPID-3987:
-
Status: Reviewable  (was: In Progress)

> Tests broker_0_9.queue.QueueTests.test_unbind_fanout and 
> broker_0_9.queue.QueueTests.test_unbind_headers fail with 404, 'No such 
> binding'
> -
>
> Key: QPID-3987
> URL: https://issues.apache.org/jira/browse/QPID-3987
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker, Python Test Suite
>Affects Versions: 0.17
>Reporter: Keith Wall
>Assignee: Keith Wall
>Priority: Minor
> Fix For: qpid-java-7.0.0
>
>
> Running the broker_0_9 test suite from tests/src/py/qpid_tests/broker_0_9 
> show the following tests fail:
> {code}
> broker_0_9.queue.QueueTests.test_unbind_fanout
> broker_0_9.queue.QueueTests.test_unbind_headers
> {code}
> The test is producing the following stack trace:
> {code}
> Error during test:  Traceback (most recent call last):
> File "./qpid-python-test", line 340, in run
>   phase()
> File 
> "/home/kwall/src/qpid/qpid/tests/src/py/qpid_tests/broker_0_9/queue.py", line 
> 34, in test_unbind_fanout
>   self.unbind_test(exchange="amq.fanout")
> File 
> "/home/kwall/src/qpid/qpid/tests/src/py/qpid_tests/broker_0_9/queue.py", line 
> 60, in unbind_test
>   channel.queue_unbind(exchange=exchange, queue="queue-1", 
> routing_key=routing_key, arguments=args)
> File "/home/kwall/src/qpid/qpid/python/qpid/peer.py", line 350, in 
> 
>   method = lambda *args, **kwargs: self.invoke(type, args, kwargs)
> File "/home/kwall/src/qpid/qpid/python/qpid/peer.py", line 268, in invoke
>   return self.invoker(frame, content)
> File "/home/kwall/src/qpid/qpid/python/qpid/peer.py", line 343, in 
> invoke_method
>   raise Closed(self.reason)
>   Closed: Method(name=close, id=40) (404, 'No such binding', 50, 50) content 
> = None
> Totals: 1 tests, 0 passed, 0 skipped, 0 ignored, 1 failed
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Assigned] (QPID-3987) Tests broker_0_9.queue.QueueTests.test_unbind_fanout and broker_0_9.queue.QueueTests.test_unbind_headers fail with 404, 'No such binding'

[Keith Wall (JIRA)]

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

Keith Wall reassigned QPID-3987:


Assignee: Keith Wall

> Tests broker_0_9.queue.QueueTests.test_unbind_fanout and 
> broker_0_9.queue.QueueTests.test_unbind_headers fail with 404, 'No such 
> binding'
> -
>
> Key: QPID-3987
> URL: https://issues.apache.org/jira/browse/QPID-3987
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker, Python Test Suite
>Affects Versions: 0.17
>Reporter: Keith Wall
>Assignee: Keith Wall
>Priority: Minor
> Fix For: qpid-java-7.0.0
>
>
> Running the broker_0_9 test suite from tests/src/py/qpid_tests/broker_0_9 
> show the following tests fail:
> {code}
> broker_0_9.queue.QueueTests.test_unbind_fanout
> broker_0_9.queue.QueueTests.test_unbind_headers
> {code}
> The test is producing the following stack trace:
> {code}
> Error during test:  Traceback (most recent call last):
> File "./qpid-python-test", line 340, in run
>   phase()
> File 
> "/home/kwall/src/qpid/qpid/tests/src/py/qpid_tests/broker_0_9/queue.py", line 
> 34, in test_unbind_fanout
>   self.unbind_test(exchange="amq.fanout")
> File 
> "/home/kwall/src/qpid/qpid/tests/src/py/qpid_tests/broker_0_9/queue.py", line 
> 60, in unbind_test
>   channel.queue_unbind(exchange=exchange, queue="queue-1", 
> routing_key=routing_key, arguments=args)
> File "/home/kwall/src/qpid/qpid/python/qpid/peer.py", line 350, in 
> 
>   method = lambda *args, **kwargs: self.invoke(type, args, kwargs)
> File "/home/kwall/src/qpid/qpid/python/qpid/peer.py", line 268, in invoke
>   return self.invoker(frame, content)
> File "/home/kwall/src/qpid/qpid/python/qpid/peer.py", line 343, in 
> invoke_method
>   raise Closed(self.reason)
>   Closed: Method(name=close, id=40) (404, 'No such binding', 50, 50) content 
> = None
> Totals: 1 tests, 0 passed, 0 skipped, 0 ignored, 1 failed
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Closed] (QPID-7596) client-server example from proton python doesn't work

[Gordon Sim (JIRA)]

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

Gordon Sim closed QPID-7596.

Resolution: Duplicate

> client-server example from proton python doesn't work
> -
>
> Key: QPID-7596
> URL: https://issues.apache.org/jira/browse/QPID-7596
> Project: Qpid
>  Issue Type: Bug
>  Components: Java Broker
>Affects Versions: qpid-java-6.1
>Reporter: Gordon Sim
>
> I.e. using 
> https://qpid.apache.org/releases/qpid-proton-0.16.0/proton/python/examples/server.py.html
>  and 
> https://qpid.apache.org/releases/qpid-proton-0.16.0/proton/python/examples/client.py.html
> (Broker needs a queue called examples, may need to modify the url used by the 
> server, to avoid getting an error on connect due to the hostname in the open 
> frame.)
> {noformat}
> $ PN_TRACE_FRM=1 ./server.py 
> Listening on localhost:amqp
> [0x55ae05a3f1b0]:  -> SASL
> [0x55ae05a3f1b0]:  <- SASL
> [0x55ae05a3f1b0]:0 <- @sasl-mechanisms(64) 
> [sasl-server-mechanisms=@PN_SYMBOL[:ANONYMOUS]]
> [0x55ae05a3f1b0]:0 -> @sasl-init(65) [mechanism=:ANONYMOUS, 
> initial-response=b"anonymous@localhost.localdomain"]
> [0x55ae05a3f1b0]:0 <- @sasl-outcome(68) [code=0]
> [0x55ae05a3f1b0]:  -> AMQP
> [0x55ae05a3f1b0]:0 -> @open(16) 
> [container-id="396bbe81-3d21-4f89-9121-0923d04fa850", hostname="localhost", 
> channel-max=32767]
> [0x55ae05a3f1b0]:0 -> @begin(17) [next-outgoing-id=0, 
> incoming-window=2147483647, outgoing-window=2147483647]
> [0x55ae05a3f1b0]:0 -> @attach(18) 
> [name="396bbe81-3d21-4f89-9121-0923d04fa850-examples", handle=0, role=true, 
> snd-settle-mode=2, rcv-settle-mode=0, source=@source(40) [address="examples", 
> durable=0, timeout=0, dynamic=false], target=@target(41) [durable=0, 
> timeout=0, dynamic=false], initial-delivery-count=0]
> [0x55ae05a3f1b0]:0 -> @attach(18) 
> [name="396bbe81-3d21-4f89-9121-0923d04fa850-726bcf6d-dc7d-45a5-aff5-bd92f735fa8f",
>  handle=1, role=false, snd-settle-mode=2, rcv-settle-mode=0, 
> source=@source(40) [durable=0, timeout=0, dynamic=false], target=@target(41) 
> [durable=0, timeout=0, dynamic=false], initial-delivery-count=0]
> [0x55ae05a3f1b0]:0 -> @flow(19) [incoming-window=2147483647, 
> next-outgoing-id=0, outgoing-window=2147483647, handle=0, delivery-count=0, 
> link-credit=10, drain=false]
> [0x55ae05a3f1b0]:  <- AMQP
> [0x55ae05a3f1b0]:0 <- @open(16) 
> [container-id="82345187-1927-467f-87ae-a40e218e3899", max-frame-size=32768, 
> channel-max=255, idle-time-out=0, properties={:product="qpid", 
> :version="6.1.1", :"qpid.build"="Unversioned directory", 
> :"qpid.instance_name"="Broker"}]
> [0x55ae05a3f1b0]:0 <- @begin(17) [remote-channel=0, next-outgoing-id=0, 
> incoming-window=2048, outgoing-window=2048]
> [0x55ae05a3f1b0]:0 <- @attach(18) 
> [name="396bbe81-3d21-4f89-9121-0923d04fa850-examples", handle=0, role=false, 
> snd-settle-mode=2, rcv-settle-mode=0, source=@source(40) [address="examples", 
> durable=0, timeout=0, dynamic=false], target=@target(41) [durable=0, 
> timeout=0, dynamic=false], initial-delivery-count=0, properties={}]
> [0x55ae05a3f1b0]:0 <- @attach(18) 
> [name="396bbe81-3d21-4f89-9121-0923d04fa850-726bcf6d-dc7d-45a5-aff5-bd92f735fa8f",
>  handle=1, role=true, snd-settle-mode=2, rcv-settle-mode=0, 
> source=@source(40) [durable=0, timeout=0, dynamic=false], target=@target(41) 
> [durable=0, timeout=0, dynamic=false, 
> capabilities=@PN_SYMBOL[:"REJECT_UNROUTABLE"]], properties={}]
> [0x55ae05a3f1b0]:0 <- @flow(19) [next-incoming-id=0, incoming-window=2048, 
> next-outgoing-id=0, outgoing-window=2048, handle=1, delivery-count=0, 
> link-credit=2, echo=false]
> [0x55ae05a3f1b0]:0 <- @transfer(20) [handle=0, delivery-id=0, 
> delivery-tag=b"\x00\x00\x00\x00\x00\x00\x00\x00", message-format=0] (137) 
> "\x00Sp\xd0\x00\x00\x00\x0b\x00\x00\x00\x05BP\x04@BR\x00\x00Ss\xd0\x00\x00\x00G\x00\x00\x00\x0d\xa1$805bb984-5ee1-43d6-b052-7b166c986d9a@@@\x83\x00\x00\x00\x00\x00\x00\x00\x00\x83\x00\x00\x00\x00\x00\x00\x00\x00@R\x00@\x00Sw\xa1"Twas
>  brillig, and the slithy toves"
> Received Message{reply_to="805bb984-5ee1-43d6-b052-7b166c986d9a", body="Twas 
> brillig, and the slithy toves"}
> [0x55ae05a3f1b0]:0 -> @transfer(20) [handle=1, delivery-id=0, 
> delivery-tag=b"1", message-format=0, settled=false, more=false] (137) 
> "\x00Sp\xd0\x00\x00\x00\x0b\x00\x00\x00\x05BP\x04@BR\x00\x00Ss\xd0\x00\x00\x00G\x00\x00\x00\x0d@@\xa1$805bb984-5ee1-43d6-b052-7b166c986d9a@\x83\x00\x00\x00\x00\x00\x00\x00\x00\x83\x00\x00\x00\x00\x00\x00\x00\x00@R\x00@\x00Sw\xa1"TWAS
>  BRILLIG, AND THE SLITHY TOVES"
> [0x55ae05a3f1b0]:0 -> @disposition(21) [role=true, first=0, last=0, 
> settled=true, state=@accepted(36) []]
> [0x55ae05a3f1b0]:0 <- @disposition(21) [role=true, first=0, last=0, 
> settled=true, state=@rejected(37) []]
> [0x55ae05a3f1b0]:0 <- @flow(19) 

Re: AMQP 1.0/Python - Question re. encoding of maps and lists : failing qpid_tests.broker_1_0.translation.TranslationTests.test_translate* against Java Broker

[Keith W]

>> https://qpid.apache.org/components/messaging-api/index.html
>
>
> The qpid.messaging python client (pure python) is of course supported.
> However at present it only speak AMQP 0-10 and no-one has indicated any
> plans to add 1.0 support to it.
>
> The swigged version of the c++ equivalent is a different library (though
> they look very similar obviously), and that is the one we have never pushed
> as an actual end-usable client library (because there already was a pure
> python equivalent).

Ok - I understand the distinction now.

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-6028) [Java Broker] Configured model objects should have only one parent

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15772644#comment-15772644
 ] 

ASF subversion and git services commented on QPID-6028:
---

Commit 1775819 from [~k-wall] in branch 'java/trunk'
[ https://svn.apache.org/r1775819 ]

QPID-6028 : [Java Broker] PublishingLink is a generalisation of Binding

> [Java Broker] Configured model objects should have only one parent
> --
>
> Key: QPID-6028
> URL: https://issues.apache.org/jira/browse/QPID-6028
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Reporter: Rob Godfrey
>Assignee: Keith Wall
> Fix For: qpid-java-7.0.0
>
>
> Currently it is possible for a configured object to be defined as having 
> multiple parents (of different classes)
> Thus a binding has a "queue" parent and an "exchange" parent, a consumer has 
> a "session" parent and a "queue" parent, a virtualhostalias has a "port" 
> parent and a virtialhost parent.
> This design should be changed.
> h5. Bindings
> Bindings should have a single exchange parent with the queue being an 
> attribute (note that this probably also requires adding binding-key as an 
> attribute and setting the name to queue/binding-key or some such.  
> Exchange-wide validation on the binding-key will be required)
> h5. Consumers
> Since in AMQP 1.0 a link endpoint may outlive the session that created it, it 
> makes sense for the parent of the Consumer to be the Queue.  The Session will 
> be a (derived) attribute of the Consumer.
> h5. VirtualhostAliases
> The primary parent of the virtualhostalias should be the (amqp) port.  The 
> virtualHost should be an attribute.  On creating a VirtualHost we should 
> offer to create an alias for the virtual host on all existing ports with the 
> host name as the alias.  On creating a port we should offer to create aliases 
> for each of the existing virtualhosts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-6028) [Java Broker] Configured model objects should have only one parent

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15772643#comment-15772643
 ] 

ASF subversion and git services commented on QPID-6028:
---

Commit 1775818 from [~k-wall] in branch 'java/trunk'
[ https://svn.apache.org/r1775818 ]

QPID-6028 : Queue caches binding count

> [Java Broker] Configured model objects should have only one parent
> --
>
> Key: QPID-6028
> URL: https://issues.apache.org/jira/browse/QPID-6028
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Reporter: Rob Godfrey
>Assignee: Keith Wall
> Fix For: qpid-java-7.0.0
>
>
> Currently it is possible for a configured object to be defined as having 
> multiple parents (of different classes)
> Thus a binding has a "queue" parent and an "exchange" parent, a consumer has 
> a "session" parent and a "queue" parent, a virtualhostalias has a "port" 
> parent and a virtialhost parent.
> This design should be changed.
> h5. Bindings
> Bindings should have a single exchange parent with the queue being an 
> attribute (note that this probably also requires adding binding-key as an 
> attribute and setting the name to queue/binding-key or some such.  
> Exchange-wide validation on the binding-key will be required)
> h5. Consumers
> Since in AMQP 1.0 a link endpoint may outlive the session that created it, it 
> makes sense for the parent of the Consumer to be the Queue.  The Session will 
> be a (derived) attribute of the Consumer.
> h5. VirtualhostAliases
> The primary parent of the virtualhostalias should be the (amqp) port.  The 
> virtualHost should be an attribute.  On creating a VirtualHost we should 
> offer to create an alias for the virtual host on all existing ports with the 
> host name as the alias.  On creating a port we should offer to create aliases 
> for each of the existing virtualhosts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-6028) [Java Broker] Configured model objects should have only one parent

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15772524#comment-15772524
 ] 

ASF subversion and git services commented on QPID-6028:
---

Commit 1775810 from [~k-wall] in branch 'java/trunk'
[ https://svn.apache.org/r1775810 ]

QPID-6028 : Refactor ACO constructors etc to accept only a single parent

> [Java Broker] Configured model objects should have only one parent
> --
>
> Key: QPID-6028
> URL: https://issues.apache.org/jira/browse/QPID-6028
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Reporter: Rob Godfrey
>Assignee: Keith Wall
> Fix For: qpid-java-7.0.0
>
>
> Currently it is possible for a configured object to be defined as having 
> multiple parents (of different classes)
> Thus a binding has a "queue" parent and an "exchange" parent, a consumer has 
> a "session" parent and a "queue" parent, a virtualhostalias has a "port" 
> parent and a virtialhost parent.
> This design should be changed.
> h5. Bindings
> Bindings should have a single exchange parent with the queue being an 
> attribute (note that this probably also requires adding binding-key as an 
> attribute and setting the name to queue/binding-key or some such.  
> Exchange-wide validation on the binding-key will be required)
> h5. Consumers
> Since in AMQP 1.0 a link endpoint may outlive the session that created it, it 
> makes sense for the parent of the Consumer to be the Queue.  The Session will 
> be a (derived) attribute of the Consumer.
> h5. VirtualhostAliases
> The primary parent of the virtualhostalias should be the (amqp) port.  The 
> virtualHost should be an attribute.  On creating a VirtualHost we should 
> offer to create an alias for the virtual host on all existing ports with the 
> host name as the alias.  On creating a port we should offer to create aliases 
> for each of the existing virtualhosts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Created] (QPID-7596) client-server example from proton python doesn't work

[Gordon Sim (JIRA)]

Gordon Sim created QPID-7596:


 Summary: client-server example from proton python doesn't work
 Key: QPID-7596
 URL: https://issues.apache.org/jira/browse/QPID-7596
 Project: Qpid
  Issue Type: Bug
  Components: Java Broker
Affects Versions: qpid-java-6.1
Reporter: Gordon Sim


I.e. using 
https://qpid.apache.org/releases/qpid-proton-0.16.0/proton/python/examples/server.py.html
 and 
https://qpid.apache.org/releases/qpid-proton-0.16.0/proton/python/examples/client.py.html

(Broker needs a queue called examples, may need to modify the url used by the 
server, to avoid getting an error on connect due to the hostname in the open 
frame.)

{noformat}
$ PN_TRACE_FRM=1 ./server.py 
Listening on localhost:amqp
[0x55ae05a3f1b0]:  -> SASL
[0x55ae05a3f1b0]:  <- SASL
[0x55ae05a3f1b0]:0 <- @sasl-mechanisms(64) 
[sasl-server-mechanisms=@PN_SYMBOL[:ANONYMOUS]]
[0x55ae05a3f1b0]:0 -> @sasl-init(65) [mechanism=:ANONYMOUS, 
initial-response=b"anonymous@localhost.localdomain"]
[0x55ae05a3f1b0]:0 <- @sasl-outcome(68) [code=0]
[0x55ae05a3f1b0]:  -> AMQP
[0x55ae05a3f1b0]:0 -> @open(16) 
[container-id="396bbe81-3d21-4f89-9121-0923d04fa850", hostname="localhost", 
channel-max=32767]
[0x55ae05a3f1b0]:0 -> @begin(17) [next-outgoing-id=0, 
incoming-window=2147483647, outgoing-window=2147483647]
[0x55ae05a3f1b0]:0 -> @attach(18) 
[name="396bbe81-3d21-4f89-9121-0923d04fa850-examples", handle=0, role=true, 
snd-settle-mode=2, rcv-settle-mode=0, source=@source(40) [address="examples", 
durable=0, timeout=0, dynamic=false], target=@target(41) [durable=0, timeout=0, 
dynamic=false], initial-delivery-count=0]
[0x55ae05a3f1b0]:0 -> @attach(18) 
[name="396bbe81-3d21-4f89-9121-0923d04fa850-726bcf6d-dc7d-45a5-aff5-bd92f735fa8f",
 handle=1, role=false, snd-settle-mode=2, rcv-settle-mode=0, source=@source(40) 
[durable=0, timeout=0, dynamic=false], target=@target(41) [durable=0, 
timeout=0, dynamic=false], initial-delivery-count=0]
[0x55ae05a3f1b0]:0 -> @flow(19) [incoming-window=2147483647, 
next-outgoing-id=0, outgoing-window=2147483647, handle=0, delivery-count=0, 
link-credit=10, drain=false]
[0x55ae05a3f1b0]:  <- AMQP
[0x55ae05a3f1b0]:0 <- @open(16) 
[container-id="82345187-1927-467f-87ae-a40e218e3899", max-frame-size=32768, 
channel-max=255, idle-time-out=0, properties={:product="qpid", 
:version="6.1.1", :"qpid.build"="Unversioned directory", 
:"qpid.instance_name"="Broker"}]
[0x55ae05a3f1b0]:0 <- @begin(17) [remote-channel=0, next-outgoing-id=0, 
incoming-window=2048, outgoing-window=2048]
[0x55ae05a3f1b0]:0 <- @attach(18) 
[name="396bbe81-3d21-4f89-9121-0923d04fa850-examples", handle=0, role=false, 
snd-settle-mode=2, rcv-settle-mode=0, source=@source(40) [address="examples", 
durable=0, timeout=0, dynamic=false], target=@target(41) [durable=0, timeout=0, 
dynamic=false], initial-delivery-count=0, properties={}]
[0x55ae05a3f1b0]:0 <- @attach(18) 
[name="396bbe81-3d21-4f89-9121-0923d04fa850-726bcf6d-dc7d-45a5-aff5-bd92f735fa8f",
 handle=1, role=true, snd-settle-mode=2, rcv-settle-mode=0, source=@source(40) 
[durable=0, timeout=0, dynamic=false], target=@target(41) [durable=0, 
timeout=0, dynamic=false, capabilities=@PN_SYMBOL[:"REJECT_UNROUTABLE"]], 
properties={}]
[0x55ae05a3f1b0]:0 <- @flow(19) [next-incoming-id=0, incoming-window=2048, 
next-outgoing-id=0, outgoing-window=2048, handle=1, delivery-count=0, 
link-credit=2, echo=false]
[0x55ae05a3f1b0]:0 <- @transfer(20) [handle=0, delivery-id=0, 
delivery-tag=b"\x00\x00\x00\x00\x00\x00\x00\x00", message-format=0] (137) 
"\x00Sp\xd0\x00\x00\x00\x0b\x00\x00\x00\x05BP\x04@BR\x00\x00Ss\xd0\x00\x00\x00G\x00\x00\x00\x0d\xa1$805bb984-5ee1-43d6-b052-7b166c986d9a@@@\x83\x00\x00\x00\x00\x00\x00\x00\x00\x83\x00\x00\x00\x00\x00\x00\x00\x00@R\x00@\x00Sw\xa1"Twas
 brillig, and the slithy toves"
Received Message{reply_to="805bb984-5ee1-43d6-b052-7b166c986d9a", body="Twas 
brillig, and the slithy toves"}
[0x55ae05a3f1b0]:0 -> @transfer(20) [handle=1, delivery-id=0, 
delivery-tag=b"1", message-format=0, settled=false, more=false] (137) 
"\x00Sp\xd0\x00\x00\x00\x0b\x00\x00\x00\x05BP\x04@BR\x00\x00Ss\xd0\x00\x00\x00G\x00\x00\x00\x0d@@\xa1$805bb984-5ee1-43d6-b052-7b166c986d9a@\x83\x00\x00\x00\x00\x00\x00\x00\x00\x83\x00\x00\x00\x00\x00\x00\x00\x00@R\x00@\x00Sw\xa1"TWAS
 BRILLIG, AND THE SLITHY TOVES"
[0x55ae05a3f1b0]:0 -> @disposition(21) [role=true, first=0, last=0, 
settled=true, state=@accepted(36) []]
[0x55ae05a3f1b0]:0 <- @disposition(21) [role=true, first=0, last=0, 
settled=true, state=@rejected(37) []]
[0x55ae05a3f1b0]:0 <- @flow(19) [next-incoming-id=1, incoming-window=2048, 
next-outgoing-id=1, outgoing-window=2048, handle=0, delivery-count=1, 
link-credit=9, available=0, drain=false, echo=false]
[0x55ae05a3f1b0]:0 -> @flow(19) [next-incoming-id=1, 
incoming-window=2147483647, next-outgoing-id=1, outgoing-window=2147483647, 
handle=0, delivery-count=1, 

Re: AMQP 1.0/Python - Question re. encoding of maps and lists : failing qpid_tests.broker_1_0.translation.TranslationTests.test_translate* against Java Broker

[Gordon Sim]

On 23/12/16 08:34, Keith W wrote:

On 22 December 2016 at 12:11, Gordon Sim  wrote:

On 21/12/16 17:51, Keith W wrote:


I believed that Python Messaging derived its AMQP 1.0 support by way
of the swigged client.  Are we saying this is deprecated?



It is more that it has never been considered a recommended client. It was
just something we used in testing.


Ok - I see.  I think we should re-visit this page.  As an end user I
would believe the opposite.

https://qpid.apache.org/components/messaging-api/index.html


The qpid.messaging python client (pure python) is of course supported. 
However at present it only speak AMQP 0-10 and no-one has indicated any 
plans to add 1.0 support to it.


The swigged version of the c++ equivalent is a different library (though 
they look very similar obviously), and that is the one we have never 
pushed as an actual end-usable client library (because there already was 
a pure python equivalent).




-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

[jira] [Commented] (QPID-6028) [Java Broker] Configured model objects should have only one parent

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/QPID-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15772352#comment-15772352
 ] 

ASF subversion and git services commented on QPID-6028:
---

Commit 1775803 from [~k-wall] in branch 'java/trunk'
[ https://svn.apache.org/r1775803 ]

QPID-6028 : Prevent ClassCastException causing test failures on persistent 
profiles

> [Java Broker] Configured model objects should have only one parent
> --
>
> Key: QPID-6028
> URL: https://issues.apache.org/jira/browse/QPID-6028
> Project: Qpid
>  Issue Type: Improvement
>  Components: Java Broker
>Reporter: Rob Godfrey
>Assignee: Keith Wall
> Fix For: qpid-java-7.0.0
>
>
> Currently it is possible for a configured object to be defined as having 
> multiple parents (of different classes)
> Thus a binding has a "queue" parent and an "exchange" parent, a consumer has 
> a "session" parent and a "queue" parent, a virtualhostalias has a "port" 
> parent and a virtialhost parent.
> This design should be changed.
> h5. Bindings
> Bindings should have a single exchange parent with the queue being an 
> attribute (note that this probably also requires adding binding-key as an 
> attribute and setting the name to queue/binding-key or some such.  
> Exchange-wide validation on the binding-key will be required)
> h5. Consumers
> Since in AMQP 1.0 a link endpoint may outlive the session that created it, it 
> makes sense for the parent of the Consumer to be the Queue.  The Session will 
> be a (derived) attribute of the Consumer.
> h5. VirtualhostAliases
> The primary parent of the virtualhostalias should be the (amqp) port.  The 
> virtualHost should be an attribute.  On creating a VirtualHost we should 
> offer to create an alias for the virtual host on all existing ports with the 
> host name as the alias.  On creating a port we should offer to create aliases 
> for each of the existing virtualhosts.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Re: AMQP 1.0/Python - Question re. encoding of maps and lists : failing qpid_tests.broker_1_0.translation.TranslationTests.test_translate* against Java Broker

[Keith W]

On 22 December 2016 at 12:11, Gordon Sim  wrote:
> On 21/12/16 17:51, Keith W wrote:
>>
>> I believed that Python Messaging derived its AMQP 1.0 support by way
>> of the swigged client.  Are we saying this is deprecated?
>
>
> It is more that it has never been considered a recommended client. It was
> just something we used in testing.

Ok - I see.  I think we should re-visit this page.  As an end user I
would believe the opposite.

https://qpid.apache.org/components/messaging-api/index.html

>
>>  If so,
>> what is the preferred Qpid Python client for AMQP 1.0?
>
>
> The proton client:
> https://qpid.apache.org/releases/qpid-proton-0.16.0/proton/python/book/overview.html
>
>

Understood.  Thanks for the clarification.


> -
> To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
> For additional commands, e-mail: dev-h...@qpid.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org