[jira] [Commented] (PROTON-1409) Expose delivery size
[ https://issues.apache.org/jira/browse/PROTON-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15895549#comment-15895549 ] ASF GitHub Bot commented on PROTON-1409: Github user clebertsuconic commented on the issue: https://github.com/apache/qpid-proton-j/pull/7 @gemmellr if you could help me by fixing this any way you like and get it by next release? I'm currently having to allocate a bigger Netty buffer than required when receiving Deliveries through my loop on Artemis. I'm about to make a big commit, and if this was release it would be great. Thanks > Expose delivery size > > > Key: PROTON-1409 > URL: https://issues.apache.org/jira/browse/PROTON-1409 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-j >Reporter: clebert suconic > > When I'm receiving the Delivery on the broker, I have to pre-create a buffer > to copy the byte array inside the Delivery. > I would like to have it exposed so I only allocated the required bytes. > I will follow up with a PR on this -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-proton-j issue #7: PROTON-1409 Exposing delivery length
Github user clebertsuconic commented on the issue: https://github.com/apache/qpid-proton-j/pull/7 @gemmellr if you could help me by fixing this any way you like and get it by next release? I'm currently having to allocate a bigger Netty buffer than required when receiving Deliveries through my loop on Artemis. I'm about to make a big commit, and if this was release it would be great. Thanks --- 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-1409) Expose delivery size
[ https://issues.apache.org/jira/browse/PROTON-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15895547#comment-15895547 ] ASF GitHub Bot commented on PROTON-1409: Github user clebertsuconic commented on the issue: https://github.com/apache/qpid-proton-j/pull/7 getReadableBytes is in line with other buffers.. I thought it would be more intuitive. > Expose delivery size > > > Key: PROTON-1409 > URL: https://issues.apache.org/jira/browse/PROTON-1409 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-j >Reporter: clebert suconic > > When I'm receiving the Delivery on the broker, I have to pre-create a buffer > to copy the byte array inside the Delivery. > I would like to have it exposed so I only allocated the required bytes. > I will follow up with a PR on this -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-proton-j issue #7: PROTON-1409 Exposing delivery length
Github user clebertsuconic commented on the issue: https://github.com/apache/qpid-proton-j/pull/7 getReadableBytes is in line with other buffers.. I thought it would be more intuitive. --- 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
[GitHub] qpid-proton-j issue #7: PROTON-1409 Exposing delivery length
Github user clebertsuconic commented on the issue: https://github.com/apache/qpid-proton-j/pull/7 @gemmellr since the current method is not part of the api, I renamed it to getReadableBytes, changed a test to allocate the exact number of bytes available before the recv was called, and added some javadoc. Let me know if you see any edits on the javadoc I wrote. Or feel free to commit on top of that of course. --- 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-1409) Expose delivery size
[ https://issues.apache.org/jira/browse/PROTON-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15895546#comment-15895546 ] ASF GitHub Bot commented on PROTON-1409: Github user clebertsuconic commented on the issue: https://github.com/apache/qpid-proton-j/pull/7 @gemmellr since the current method is not part of the api, I renamed it to getReadableBytes, changed a test to allocate the exact number of bytes available before the recv was called, and added some javadoc. Let me know if you see any edits on the javadoc I wrote. Or feel free to commit on top of that of course. > Expose delivery size > > > Key: PROTON-1409 > URL: https://issues.apache.org/jira/browse/PROTON-1409 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-j >Reporter: clebert suconic > > When I'm receiving the Delivery on the broker, I have to pre-create a buffer > to copy the byte array inside the Delivery. > I would like to have it exposed so I only allocated the required bytes. > I will follow up with a PR on this -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-6211) Maintain version information in the python messaging API
[ https://issues.apache.org/jira/browse/QPID-6211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-6211: -- Fix Version/s: (was: qpid-python-1.36.0) qpid-python-1.37.0 > Maintain version information in the python messaging API > > > Key: QPID-6211 > URL: https://issues.apache.org/jira/browse/QPID-6211 > Project: Qpid > Issue Type: Improvement > Components: Python Client >Affects Versions: 0.30 >Reporter: Justin Ross > Fix For: qpid-python-1.37.0 > > > Use setup.py to set a __version__ attribute on the main messaging API module. > http://legacy.python.org/dev/peps/pep-0396/#id26 > http://legacy.python.org/dev/peps/pep-0008/#version-bookkeeping -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7463) [Python Client for AMQP 0-8,0-9] Race condition when creating session
[
https://issues.apache.org/jira/browse/QPID-7463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross updated QPID-7463:
--
Fix Version/s: (was: qpid-python-1.36.0)
qpid-python-1.37.0
> [Python Client for AMQP 0-8,0-9] Race condition when creating session
> -
>
> Key: QPID-7463
> URL: https://issues.apache.org/jira/browse/QPID-7463
> Project: Qpid
> Issue Type: Bug
> Components: Python Client
>Affects Versions: qpid-python-1.35.0
>Reporter: Lorenz Quack
> Fix For: qpid-python-1.37.0
>
>
> It seems that {{Client.session()}} is not thread safe. There seems to be a
> race condition that means two concurrent calls can actually share the same
> underlying session.
> {{Client.session()}} acquires {{self.lock}} and determines a free session id.
> It then releases the lock before calling {{self.channel(id)}} which acquires
> the lock again and allocates the id and creates the session.
> If a second call to {{Client.session()}} happens in the moment the lock is
> released but before {{self.channel(id)}} reacquires it the second call will
> find the same free {{id}} and will then subsequently return the same session
> object from {{self.channel(id)}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-6693) qpid-python setup.py syntax error when raising DistutilsFileError
[ https://issues.apache.org/jira/browse/QPID-6693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-6693: -- Fix Version/s: (was: qpid-python-1.36.0) qpid-python-1.37.0 > qpid-python setup.py syntax error when raising DistutilsFileError > - > > Key: QPID-6693 > URL: https://issues.apache.org/jira/browse/QPID-6693 > Project: Qpid > Issue Type: Bug > Components: Python Client >Affects Versions: 0.26 > Environment: pip on openSUSE >Reporter: Adam Williamson >Assignee: Justin Ross > Fix For: qpid-python-1.37.0 > > Original Estimate: 0.25h > Remaining Estimate: 0.25h > > Trying 'pip install qpid-python' on openSUSE 13.2, I get this: > openqa:/opt/openqa_fedora_tools/tools/openqa_trigger # pip install qpid-python > Downloading/unpacking qpid-python > Downloading qpid-python-0.26.tar.gz (146kB): 146kB downloaded > Running setup.py (path:/tmp/pip_build_root/qpid-python/setup.py) egg_info > for package qpid-python > Traceback (most recent call last): > File "", line 17, in > File "/tmp/pip_build_root/qpid-python/setup.py", line 42 > raise DistutilsFileError, \ > ^ > SyntaxError: invalid syntax > Complete output from command python setup.py egg_info: > Traceback (most recent call last): > File "", line 17, in > File "/tmp/pip_build_root/qpid-python/setup.py", line 42 > raise DistutilsFileError, \ > ^ > SyntaxError: invalid syntax > > Cleaning up... > there's an obvious syntax error in the attempt to raise the exception...so I > can't tell why the install is failing :) -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-6166) [python] Disable SSLv3 support in pure-python client
[ https://issues.apache.org/jira/browse/QPID-6166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-6166: -- Fix Version/s: (was: qpid-python-1.36.0) qpid-python-1.37.0 > [python] Disable SSLv3 support in pure-python client > > > Key: QPID-6166 > URL: https://issues.apache.org/jira/browse/QPID-6166 > Project: Qpid > Issue Type: Bug > Components: Python Client >Affects Versions: 0.30 >Reporter: Ken Giusti >Assignee: Ken Giusti > Fix For: qpid-python-1.37.0 > > > In light of the padding vulnerability of SSLv3, we should prevent the python > client from allowing the SSL handshake to downgrade to SSLv3. > Unfortunately, the latest release of python 2.7.8 does not give us the > ability to disable just the SSLv3 capability. The next release of python > (2.7.9) should allow this according to the documentation: > https://docs.python.org/2/library/ssl.html#ssl.OP_NO_SSLv3 > This vulnerability can be disabled merely by eliminating support for SSLv3 on > one end of the connection. Given that QPID-6160 will disable SSLv3 on the > broker, simply fixing this on the broker side will mitigate the issue. So > until the next version of Python is made available, we should recommend > QPID-6160 be adopted as the fix to this problem. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7691) Qpid Python 1.36.0 release tasks
[ https://issues.apache.org/jira/browse/QPID-7691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15895327#comment-15895327 ] ASF subversion and git services commented on QPID-7691: --- Commit 11bc3d7b976a63d1baa7950e84d95d0bc5c67e78 in qpid-python's branch refs/heads/master from [~jr...@redhat.com] [ https://git-wip-us.apache.org/repos/asf?p=qpid-python.git;h=11bc3d7 ] QPID-7691: Bump the version on master > Qpid Python 1.36.0 release tasks > > > Key: QPID-7691 > URL: https://issues.apache.org/jira/browse/QPID-7691 > Project: Qpid > Issue Type: Task > Components: Python Client, Python Test Suite >Reporter: Justin Ross >Assignee: Justin Ross > Fix For: qpid-python-1.36.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7691) Qpid Python 1.36.0 release tasks
[ https://issues.apache.org/jira/browse/QPID-7691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15895323#comment-15895323 ] ASF subversion and git services commented on QPID-7691: --- Commit a763394938a4530f9a3ee9dc6e129e293babd121 in qpid-python's branch refs/heads/1.36.x from [~jr...@redhat.com] [ https://git-wip-us.apache.org/repos/asf?p=qpid-python.git;h=a763394 ] QPID-7691: Restore snapshot version > Qpid Python 1.36.0 release tasks > > > Key: QPID-7691 > URL: https://issues.apache.org/jira/browse/QPID-7691 > Project: Qpid > Issue Type: Task > Components: Python Client, Python Test Suite >Reporter: Justin Ross >Assignee: Justin Ross > Fix For: qpid-python-1.36.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7691) Qpid Python 1.36.0 release tasks
[ https://issues.apache.org/jira/browse/QPID-7691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15895318#comment-15895318 ] ASF subversion and git services commented on QPID-7691: --- Commit d87998ce11a988ff04ac87f3b56c3aacfbfcf033 in qpid-python's branch refs/heads/1.36.x from [~jr...@redhat.com] [ https://git-wip-us.apache.org/repos/asf?p=qpid-python.git;h=d87998c ] QPID-7691: Update the release branch version for RC1 > Qpid Python 1.36.0 release tasks > > > Key: QPID-7691 > URL: https://issues.apache.org/jira/browse/QPID-7691 > Project: Qpid > Issue Type: Task > Components: Python Client, Python Test Suite >Reporter: Justin Ross >Assignee: Justin Ross > Fix For: qpid-python-1.36.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7691) Qpid Python 1.36.0 release tasks
[ https://issues.apache.org/jira/browse/QPID-7691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated QPID-7691: -- Fix Version/s: (was: qpid-python-1.35.0) qpid-python-1.36.0 > Qpid Python 1.36.0 release tasks > > > Key: QPID-7691 > URL: https://issues.apache.org/jira/browse/QPID-7691 > Project: Qpid > Issue Type: Task > Components: Python Client, Python Test Suite >Reporter: Justin Ross >Assignee: Justin Ross > Fix For: qpid-python-1.36.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-7691) Qpid Python 1.36.0 release tasks
Justin Ross created QPID-7691: - Summary: Qpid Python 1.36.0 release tasks Key: QPID-7691 URL: https://issues.apache.org/jira/browse/QPID-7691 Project: Qpid Issue Type: Task Components: Python Client, Python Test Suite Reporter: Justin Ross Assignee: Justin Ross Fix For: qpid-python-1.35.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-621) Add missing string.h include for Solaris compiler
[ https://issues.apache.org/jira/browse/DISPATCH-621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15895109#comment-15895109 ] ASF subversion and git services commented on DISPATCH-621: -- Commit 468b38d2882d2c56fadef3eec12d16bbb9a8cb31 in qpid-dispatch's branch refs/heads/master from [~ganeshmurthy] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=468b38d ] DISPATCH-621 - Thanks Adel Boutros - Add missing string.h include for Solaris compiler > Add missing string.h include for Solaris compiler > - > > Key: DISPATCH-621 > URL: https://issues.apache.org/jira/browse/DISPATCH-621 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 0.7.0 >Reporter: Adel Boutros > Fix For: 0.8.0 > > Attachments: > 0011-Add-missing-string.h-include-for-Solaris-compiler.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-621) Add missing string.h include for Solaris compiler
[ https://issues.apache.org/jira/browse/DISPATCH-621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy resolved DISPATCH-621. Resolution: Fixed Fix Version/s: 0.8.0 > Add missing string.h include for Solaris compiler > - > > Key: DISPATCH-621 > URL: https://issues.apache.org/jira/browse/DISPATCH-621 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 0.7.0 >Reporter: Adel Boutros >Assignee: Ganesh Murthy > Fix For: 0.8.0 > > Attachments: > 0011-Add-missing-string.h-include-for-Solaris-compiler.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (DISPATCH-621) Add missing string.h include for Solaris compiler
[ https://issues.apache.org/jira/browse/DISPATCH-621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy reassigned DISPATCH-621: -- Assignee: Ganesh Murthy > Add missing string.h include for Solaris compiler > - > > Key: DISPATCH-621 > URL: https://issues.apache.org/jira/browse/DISPATCH-621 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 0.7.0 >Reporter: Adel Boutros >Assignee: Ganesh Murthy > Fix For: 0.8.0 > > Attachments: > 0011-Add-missing-string.h-include-for-Solaris-compiler.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-626) Add hints for getaddrinfo on Solaris
[ https://issues.apache.org/jira/browse/DISPATCH-626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15895077#comment-15895077 ] ASF subversion and git services commented on DISPATCH-626: -- Commit 037904579d47b742c9017c4adfa07fa4e36d019c in qpid-dispatch's branch refs/heads/master from [~ganeshmurthy] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=0379045 ] DISPATCH-626 - Add hints for getaddrinfo on Solaris > Add hints for getaddrinfo on Solaris > > > Key: DISPATCH-626 > URL: https://issues.apache.org/jira/browse/DISPATCH-626 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 0.7.0 >Reporter: Adel Boutros > Fix For: 0.8.0 > > Attachments: 0001-Add-hints-for-getaddrinfo-on-Solaris.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (DISPATCH-626) Add hints for getaddrinfo on Solaris
[ https://issues.apache.org/jira/browse/DISPATCH-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy reassigned DISPATCH-626: -- Assignee: Ganesh Murthy > Add hints for getaddrinfo on Solaris > > > Key: DISPATCH-626 > URL: https://issues.apache.org/jira/browse/DISPATCH-626 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 0.7.0 >Reporter: Adel Boutros >Assignee: Ganesh Murthy > Fix For: 0.8.0 > > Attachments: 0001-Add-hints-for-getaddrinfo-on-Solaris.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-626) Add hints for getaddrinfo on Solaris
[ https://issues.apache.org/jira/browse/DISPATCH-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy resolved DISPATCH-626. Resolution: Fixed Fix Version/s: 0.8.0 > Add hints for getaddrinfo on Solaris > > > Key: DISPATCH-626 > URL: https://issues.apache.org/jira/browse/DISPATCH-626 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 0.7.0 >Reporter: Adel Boutros >Assignee: Ganesh Murthy > Fix For: 0.8.0 > > Attachments: 0001-Add-hints-for-getaddrinfo-on-Solaris.patch > > -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-615) SunStudio doesn't convert pointers to bool correctly
[ https://issues.apache.org/jira/browse/DISPATCH-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy resolved DISPATCH-615. Resolution: Fixed > SunStudio doesn't convert pointers to bool correctly > > > Key: DISPATCH-615 > URL: https://issues.apache.org/jira/browse/DISPATCH-615 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 0.7.0 >Reporter: Adel Boutros >Assignee: Ganesh Murthy > Attachments: > 0005-SunStudio-doesn-t-convert-pointers-to-bool-correctly.patch > > > improper pointer/integer combination: op "=" (PyObject * to bool) -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (DISPATCH-615) SunStudio doesn't convert pointers to bool correctly
[ https://issues.apache.org/jira/browse/DISPATCH-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy reassigned DISPATCH-615: -- Assignee: Ganesh Murthy > SunStudio doesn't convert pointers to bool correctly > > > Key: DISPATCH-615 > URL: https://issues.apache.org/jira/browse/DISPATCH-615 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 0.7.0 >Reporter: Adel Boutros >Assignee: Ganesh Murthy > Fix For: 0.8.0 > > Attachments: > 0005-SunStudio-doesn-t-convert-pointers-to-bool-correctly.patch > > > improper pointer/integer combination: op "=" (PyObject * to bool) -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-615) SunStudio doesn't convert pointers to bool correctly
[ https://issues.apache.org/jira/browse/DISPATCH-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-615: --- Fix Version/s: 0.8.0 > SunStudio doesn't convert pointers to bool correctly > > > Key: DISPATCH-615 > URL: https://issues.apache.org/jira/browse/DISPATCH-615 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 0.7.0 >Reporter: Adel Boutros >Assignee: Ganesh Murthy > Fix For: 0.8.0 > > Attachments: > 0005-SunStudio-doesn-t-convert-pointers-to-bool-correctly.patch > > > improper pointer/integer combination: op "=" (PyObject * to bool) -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-615) SunStudio doesn't convert pointers to bool correctly
[ https://issues.apache.org/jira/browse/DISPATCH-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15895046#comment-15895046 ] ASF subversion and git services commented on DISPATCH-615: -- Commit a333a5039eb3a709e279f7fda6a73c2a358aa715 in qpid-dispatch's branch refs/heads/master from [~ganeshmurthy] [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=a333a50 ] DISPATCH-615 - Return proper boolean in qd_entity_has() function > SunStudio doesn't convert pointers to bool correctly > > > Key: DISPATCH-615 > URL: https://issues.apache.org/jira/browse/DISPATCH-615 > Project: Qpid Dispatch > Issue Type: Bug >Affects Versions: 0.7.0 >Reporter: Adel Boutros > Attachments: > 0005-SunStudio-doesn-t-convert-pointers-to-bool-correctly.patch > > > improper pointer/integer combination: op "=" (PyObject * to bool) -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-301) Some unit tests fail with workerThreads are set to 4
[
https://issues.apache.org/jira/browse/DISPATCH-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-301.
Resolution: Duplicate
Fix Version/s: 0.8.0
The workerThreads have been set back to 4. The only test that fails after
setting the workerThreads to 4 is the drain related link route tests. This is
already being tracked in DISPATCH-646
> Some unit tests fail with workerThreads are set to 4
>
>
> Key: DISPATCH-301
> URL: https://issues.apache.org/jira/browse/DISPATCH-301
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Affects Versions: 0.6.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
> Fix For: 0.8.0
>
>
> Python tests like system_tests_user_id and system_tests_qdstat fail when the
> workerThreads are set to more than 1 (in my test case I had workerThreads set
> to 4)
> I see the following output -
> {noformat}
> [gmurthy@localhost build]$ PN_TRACE_FRM=1
> "/home/gmurthy/opensource/dispatch/build/tests/run.py" "-m" "unittest" "-v"
> "system_tests_user_id"
> test_ssl_user_id (system_tests_user_id.QdSSLUseridTest) ... [0x55a742167ee0]:
> -> SASL
> [0x55a742167ee0]: <- SASL
> [0x55a742167ee0]:0 <- @sasl-mechanisms(64)
> [sasl-server-mechanisms=@PN_SYMBOL[:EXTERNAL]]
> [0x55a742167ee0]:0 -> @sasl-init(65) [mechanism=:EXTERNAL,
> initial-response=b""]
> [0x55a742167ee0]:0 <- @sasl-outcome(68) [code=0]
> [0x55a742167ee0]: -> AMQP
> [0x55a742167ee0]:0 -> @open(16)
> [container-id="473eaeaf-c3af-43d9-91ed-f10b53b38084", channel-max=32767]
> [0x55a742167ee0]: <- AMQP
> [0x55a742167ee0]:0 <- @open(16) [container-id="QDR", max-frame-size=16384,
> channel-max=32767, idle-time-out=6,
> offered-capabilities=:"ANONYMOUS-RELAY",
> properties={:product="qpid-dispatch-router", :version="0.6.0"}]
> [0x55a742167ee0]:0 -> @begin(17) [next-outgoing-id=0,
> incoming-window=2147483647, outgoing-window=2147483647]
> [0x55a742167ee0]:0 -> @attach(18)
> [name="473eaeaf-c3af-43d9-91ed-f10b53b38084-$management", handle=0,
> role=false, snd-settle-mode=2, rcv-settle-mode=0, source=@source(40)
> [durable=0, timeout=0, dynamic=false], target=@target(41)
> [address="$management", durable=0, timeout=0, dynamic=false],
> initial-delivery-count=0]
> [0x55a742167ee0]:0 -> @close(24) [error=@error(29)
> [condition=:"amqp:connection:framing-error", description="SSL Failure:
> Unknown error."]]
> [0x55a742167ee0]: <- EOS
> [0x55a742167ee0]: -> EOS
> ERROR
> ==
> ERROR: test_ssl_user_id (system_tests_user_id.QdSSLUseridTest)
> --
> Traceback (most recent call last):
> File "/home/gmurthy/opensource/dispatch/tests/system_tests_user_id.py",
> line 220, in test_ssl_user_id
> node = Node.connect(addr, ssl_domain=domain)
> File
> "/home/gmurthy/opensource/dispatch/python/qpid_dispatch/management/client.py",
> line 98, in connect
> return Node(Node.connection(url, router, timeout, ssl_domain))
> File
> "/home/gmurthy/opensource/dispatch/python/qpid_dispatch/management/client.py",
> line 112, in __init__
> self.client = SyncRequestResponse(connection, self.url.path)
> File
> "/opt/qpid-proton/qpid-proton/lib64/proton/bindings/python/proton/utils.py",
> line 321, in __init__
> self.sender = self.connection.create_sender(self.address)
> File
> "/opt/qpid-proton/qpid-proton/lib64/proton/bindings/python/proton/utils.py",
> line 211, in create_sender
> return BlockingSender(self, self.container.create_sender(self.conn,
> address, name=name, handler=handler, options=options))
> File
> "/opt/qpid-proton/qpid-proton/lib64/proton/bindings/python/proton/utils.py",
> line 68, in __init__
> super(BlockingSender, self).__init__(connection, sender)
> File
> "/opt/qpid-proton/qpid-proton/lib64/proton/bindings/python/proton/utils.py",
> line 32, in __init__
> msg="Opening link %s" % link.name)
> File
> "/opt/qpid-proton/qpid-proton/lib64/proton/bindings/python/proton/utils.py",
> line 264, in wait
> raise ConnectionException("Connection %s disconnected" % self.url)
> ConnectionException: Connection amqps://0.0.0.0:27216/$management disconnected
> --
> Ran 1 test in 2.144s
> FAILED (errors=1)
> [gmurthy@localhost build]$
> {noformat}
> Switch the workerThreads back to 1 and the tests will pass
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Reopened] (DISPATCH-301) Some unit tests fail with workerThreads are set to 4
[
https://issues.apache.org/jira/browse/DISPATCH-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy reopened DISPATCH-301:
> Some unit tests fail with workerThreads are set to 4
>
>
> Key: DISPATCH-301
> URL: https://issues.apache.org/jira/browse/DISPATCH-301
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Affects Versions: 0.6.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>
> Python tests like system_tests_user_id and system_tests_qdstat fail when the
> workerThreads are set to more than 1 (in my test case I had workerThreads set
> to 4)
> I see the following output -
> {noformat}
> [gmurthy@localhost build]$ PN_TRACE_FRM=1
> "/home/gmurthy/opensource/dispatch/build/tests/run.py" "-m" "unittest" "-v"
> "system_tests_user_id"
> test_ssl_user_id (system_tests_user_id.QdSSLUseridTest) ... [0x55a742167ee0]:
> -> SASL
> [0x55a742167ee0]: <- SASL
> [0x55a742167ee0]:0 <- @sasl-mechanisms(64)
> [sasl-server-mechanisms=@PN_SYMBOL[:EXTERNAL]]
> [0x55a742167ee0]:0 -> @sasl-init(65) [mechanism=:EXTERNAL,
> initial-response=b""]
> [0x55a742167ee0]:0 <- @sasl-outcome(68) [code=0]
> [0x55a742167ee0]: -> AMQP
> [0x55a742167ee0]:0 -> @open(16)
> [container-id="473eaeaf-c3af-43d9-91ed-f10b53b38084", channel-max=32767]
> [0x55a742167ee0]: <- AMQP
> [0x55a742167ee0]:0 <- @open(16) [container-id="QDR", max-frame-size=16384,
> channel-max=32767, idle-time-out=6,
> offered-capabilities=:"ANONYMOUS-RELAY",
> properties={:product="qpid-dispatch-router", :version="0.6.0"}]
> [0x55a742167ee0]:0 -> @begin(17) [next-outgoing-id=0,
> incoming-window=2147483647, outgoing-window=2147483647]
> [0x55a742167ee0]:0 -> @attach(18)
> [name="473eaeaf-c3af-43d9-91ed-f10b53b38084-$management", handle=0,
> role=false, snd-settle-mode=2, rcv-settle-mode=0, source=@source(40)
> [durable=0, timeout=0, dynamic=false], target=@target(41)
> [address="$management", durable=0, timeout=0, dynamic=false],
> initial-delivery-count=0]
> [0x55a742167ee0]:0 -> @close(24) [error=@error(29)
> [condition=:"amqp:connection:framing-error", description="SSL Failure:
> Unknown error."]]
> [0x55a742167ee0]: <- EOS
> [0x55a742167ee0]: -> EOS
> ERROR
> ==
> ERROR: test_ssl_user_id (system_tests_user_id.QdSSLUseridTest)
> --
> Traceback (most recent call last):
> File "/home/gmurthy/opensource/dispatch/tests/system_tests_user_id.py",
> line 220, in test_ssl_user_id
> node = Node.connect(addr, ssl_domain=domain)
> File
> "/home/gmurthy/opensource/dispatch/python/qpid_dispatch/management/client.py",
> line 98, in connect
> return Node(Node.connection(url, router, timeout, ssl_domain))
> File
> "/home/gmurthy/opensource/dispatch/python/qpid_dispatch/management/client.py",
> line 112, in __init__
> self.client = SyncRequestResponse(connection, self.url.path)
> File
> "/opt/qpid-proton/qpid-proton/lib64/proton/bindings/python/proton/utils.py",
> line 321, in __init__
> self.sender = self.connection.create_sender(self.address)
> File
> "/opt/qpid-proton/qpid-proton/lib64/proton/bindings/python/proton/utils.py",
> line 211, in create_sender
> return BlockingSender(self, self.container.create_sender(self.conn,
> address, name=name, handler=handler, options=options))
> File
> "/opt/qpid-proton/qpid-proton/lib64/proton/bindings/python/proton/utils.py",
> line 68, in __init__
> super(BlockingSender, self).__init__(connection, sender)
> File
> "/opt/qpid-proton/qpid-proton/lib64/proton/bindings/python/proton/utils.py",
> line 32, in __init__
> msg="Opening link %s" % link.name)
> File
> "/opt/qpid-proton/qpid-proton/lib64/proton/bindings/python/proton/utils.py",
> line 264, in wait
> raise ConnectionException("Connection %s disconnected" % self.url)
> ConnectionException: Connection amqps://0.0.0.0:27216/$management disconnected
> --
> Ran 1 test in 2.144s
> FAILED (errors=1)
> [gmurthy@localhost build]$
> {noformat}
> Switch the workerThreads back to 1 and the tests will pass
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-301) Some unit tests fail with workerThreads are set to 4
[
https://issues.apache.org/jira/browse/DISPATCH-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-301.
Resolution: Fixed
> Some unit tests fail with workerThreads are set to 4
>
>
> Key: DISPATCH-301
> URL: https://issues.apache.org/jira/browse/DISPATCH-301
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Affects Versions: 0.6.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>
> Python tests like system_tests_user_id and system_tests_qdstat fail when the
> workerThreads are set to more than 1 (in my test case I had workerThreads set
> to 4)
> I see the following output -
> {noformat}
> [gmurthy@localhost build]$ PN_TRACE_FRM=1
> "/home/gmurthy/opensource/dispatch/build/tests/run.py" "-m" "unittest" "-v"
> "system_tests_user_id"
> test_ssl_user_id (system_tests_user_id.QdSSLUseridTest) ... [0x55a742167ee0]:
> -> SASL
> [0x55a742167ee0]: <- SASL
> [0x55a742167ee0]:0 <- @sasl-mechanisms(64)
> [sasl-server-mechanisms=@PN_SYMBOL[:EXTERNAL]]
> [0x55a742167ee0]:0 -> @sasl-init(65) [mechanism=:EXTERNAL,
> initial-response=b""]
> [0x55a742167ee0]:0 <- @sasl-outcome(68) [code=0]
> [0x55a742167ee0]: -> AMQP
> [0x55a742167ee0]:0 -> @open(16)
> [container-id="473eaeaf-c3af-43d9-91ed-f10b53b38084", channel-max=32767]
> [0x55a742167ee0]: <- AMQP
> [0x55a742167ee0]:0 <- @open(16) [container-id="QDR", max-frame-size=16384,
> channel-max=32767, idle-time-out=6,
> offered-capabilities=:"ANONYMOUS-RELAY",
> properties={:product="qpid-dispatch-router", :version="0.6.0"}]
> [0x55a742167ee0]:0 -> @begin(17) [next-outgoing-id=0,
> incoming-window=2147483647, outgoing-window=2147483647]
> [0x55a742167ee0]:0 -> @attach(18)
> [name="473eaeaf-c3af-43d9-91ed-f10b53b38084-$management", handle=0,
> role=false, snd-settle-mode=2, rcv-settle-mode=0, source=@source(40)
> [durable=0, timeout=0, dynamic=false], target=@target(41)
> [address="$management", durable=0, timeout=0, dynamic=false],
> initial-delivery-count=0]
> [0x55a742167ee0]:0 -> @close(24) [error=@error(29)
> [condition=:"amqp:connection:framing-error", description="SSL Failure:
> Unknown error."]]
> [0x55a742167ee0]: <- EOS
> [0x55a742167ee0]: -> EOS
> ERROR
> ==
> ERROR: test_ssl_user_id (system_tests_user_id.QdSSLUseridTest)
> --
> Traceback (most recent call last):
> File "/home/gmurthy/opensource/dispatch/tests/system_tests_user_id.py",
> line 220, in test_ssl_user_id
> node = Node.connect(addr, ssl_domain=domain)
> File
> "/home/gmurthy/opensource/dispatch/python/qpid_dispatch/management/client.py",
> line 98, in connect
> return Node(Node.connection(url, router, timeout, ssl_domain))
> File
> "/home/gmurthy/opensource/dispatch/python/qpid_dispatch/management/client.py",
> line 112, in __init__
> self.client = SyncRequestResponse(connection, self.url.path)
> File
> "/opt/qpid-proton/qpid-proton/lib64/proton/bindings/python/proton/utils.py",
> line 321, in __init__
> self.sender = self.connection.create_sender(self.address)
> File
> "/opt/qpid-proton/qpid-proton/lib64/proton/bindings/python/proton/utils.py",
> line 211, in create_sender
> return BlockingSender(self, self.container.create_sender(self.conn,
> address, name=name, handler=handler, options=options))
> File
> "/opt/qpid-proton/qpid-proton/lib64/proton/bindings/python/proton/utils.py",
> line 68, in __init__
> super(BlockingSender, self).__init__(connection, sender)
> File
> "/opt/qpid-proton/qpid-proton/lib64/proton/bindings/python/proton/utils.py",
> line 32, in __init__
> msg="Opening link %s" % link.name)
> File
> "/opt/qpid-proton/qpid-proton/lib64/proton/bindings/python/proton/utils.py",
> line 264, in wait
> raise ConnectionException("Connection %s disconnected" % self.url)
> ConnectionException: Connection amqps://0.0.0.0:27216/$management disconnected
> --
> Ran 1 test in 2.144s
> FAILED (errors=1)
> [gmurthy@localhost build]$
> {noformat}
> Switch the workerThreads back to 1 and the tests will pass
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (DISPATCH-301) Some unit tests fail with workerThreads are set to 4
[
https://issues.apache.org/jira/browse/DISPATCH-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy reassigned DISPATCH-301:
--
Assignee: Ganesh Murthy
> Some unit tests fail with workerThreads are set to 4
>
>
> Key: DISPATCH-301
> URL: https://issues.apache.org/jira/browse/DISPATCH-301
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Affects Versions: 0.6.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>
> Python tests like system_tests_user_id and system_tests_qdstat fail when the
> workerThreads are set to more than 1 (in my test case I had workerThreads set
> to 4)
> I see the following output -
> {noformat}
> [gmurthy@localhost build]$ PN_TRACE_FRM=1
> "/home/gmurthy/opensource/dispatch/build/tests/run.py" "-m" "unittest" "-v"
> "system_tests_user_id"
> test_ssl_user_id (system_tests_user_id.QdSSLUseridTest) ... [0x55a742167ee0]:
> -> SASL
> [0x55a742167ee0]: <- SASL
> [0x55a742167ee0]:0 <- @sasl-mechanisms(64)
> [sasl-server-mechanisms=@PN_SYMBOL[:EXTERNAL]]
> [0x55a742167ee0]:0 -> @sasl-init(65) [mechanism=:EXTERNAL,
> initial-response=b""]
> [0x55a742167ee0]:0 <- @sasl-outcome(68) [code=0]
> [0x55a742167ee0]: -> AMQP
> [0x55a742167ee0]:0 -> @open(16)
> [container-id="473eaeaf-c3af-43d9-91ed-f10b53b38084", channel-max=32767]
> [0x55a742167ee0]: <- AMQP
> [0x55a742167ee0]:0 <- @open(16) [container-id="QDR", max-frame-size=16384,
> channel-max=32767, idle-time-out=6,
> offered-capabilities=:"ANONYMOUS-RELAY",
> properties={:product="qpid-dispatch-router", :version="0.6.0"}]
> [0x55a742167ee0]:0 -> @begin(17) [next-outgoing-id=0,
> incoming-window=2147483647, outgoing-window=2147483647]
> [0x55a742167ee0]:0 -> @attach(18)
> [name="473eaeaf-c3af-43d9-91ed-f10b53b38084-$management", handle=0,
> role=false, snd-settle-mode=2, rcv-settle-mode=0, source=@source(40)
> [durable=0, timeout=0, dynamic=false], target=@target(41)
> [address="$management", durable=0, timeout=0, dynamic=false],
> initial-delivery-count=0]
> [0x55a742167ee0]:0 -> @close(24) [error=@error(29)
> [condition=:"amqp:connection:framing-error", description="SSL Failure:
> Unknown error."]]
> [0x55a742167ee0]: <- EOS
> [0x55a742167ee0]: -> EOS
> ERROR
> ==
> ERROR: test_ssl_user_id (system_tests_user_id.QdSSLUseridTest)
> --
> Traceback (most recent call last):
> File "/home/gmurthy/opensource/dispatch/tests/system_tests_user_id.py",
> line 220, in test_ssl_user_id
> node = Node.connect(addr, ssl_domain=domain)
> File
> "/home/gmurthy/opensource/dispatch/python/qpid_dispatch/management/client.py",
> line 98, in connect
> return Node(Node.connection(url, router, timeout, ssl_domain))
> File
> "/home/gmurthy/opensource/dispatch/python/qpid_dispatch/management/client.py",
> line 112, in __init__
> self.client = SyncRequestResponse(connection, self.url.path)
> File
> "/opt/qpid-proton/qpid-proton/lib64/proton/bindings/python/proton/utils.py",
> line 321, in __init__
> self.sender = self.connection.create_sender(self.address)
> File
> "/opt/qpid-proton/qpid-proton/lib64/proton/bindings/python/proton/utils.py",
> line 211, in create_sender
> return BlockingSender(self, self.container.create_sender(self.conn,
> address, name=name, handler=handler, options=options))
> File
> "/opt/qpid-proton/qpid-proton/lib64/proton/bindings/python/proton/utils.py",
> line 68, in __init__
> super(BlockingSender, self).__init__(connection, sender)
> File
> "/opt/qpid-proton/qpid-proton/lib64/proton/bindings/python/proton/utils.py",
> line 32, in __init__
> msg="Opening link %s" % link.name)
> File
> "/opt/qpid-proton/qpid-proton/lib64/proton/bindings/python/proton/utils.py",
> line 264, in wait
> raise ConnectionException("Connection %s disconnected" % self.url)
> ConnectionException: Connection amqps://0.0.0.0:27216/$management disconnected
> --
> Ran 1 test in 2.144s
> FAILED (errors=1)
> [gmurthy@localhost build]$
> {noformat}
> Switch the workerThreads back to 1 and the tests will pass
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-646) Link route tests which test the drain feature fail intermittently
Ganesh Murthy created DISPATCH-646:
--
Summary: Link route tests which test the drain feature fail
intermittently
Key: DISPATCH-646
URL: https://issues.apache.org/jira/browse/DISPATCH-646
Project: Qpid Dispatch
Issue Type: Bug
Components: Container
Affects Versions: 0.8.0
Reporter: Ganesh Murthy
Assignee: Ted Ross
There is test called test_www_drain_support_all_messages in
system_tests_link_routes that fails intermittently. Here is the output of the
test
{noformat}
[gmurthy@localhost build]$ /usr/bin/python
"/home/gmurthy/opensource/dispatch/build/tests/run.py" "-m" "unittest" "-v"
"system_tests_link_routes.LinkRouteTest.test_www_drain_support_all_messages"
test_www_drain_support_all_messages (system_tests_link_routes.LinkRouteTest)
...
FAIL
==
FAIL: test_www_drain_support_all_messages
(system_tests_link_routes.LinkRouteTest)
--
Traceback (most recent call last):
File "/home/gmurthy/opensource/dispatch/tests/system_tests_link_routes.py",
line 542, in test_www_drain_support_all_messages
self.assertEqual(None, drain_support.error)
AssertionError: None != 'Timeout Expired: sent: 10 rcvd: 7'
--
Ran 1 test in 9.421s
FAILED (failures=1)
{noformat}
The test uses 3 routers (routers A, B and C) with router A acting as the broker
and the senders and receivers connected router C and they send/receive on link
routed addresses. The messages sent to router C are link-routed to router B and
go on to router A and are eventually link routed back to router B and finally
to a receiver attached to router C.
The sender sends 10 messages and the receiver initially issues a flow of 4
followed by a drain of 20. This means that the remaining 6 messages must come
thru to the receiver. The problem in that in router B, the 6 transfers from
router A to router B are followed by a response flow frame (drain=true). In
router B, this flow frame sometimes gets ahead of the transfers and shuts down
the remaining transfers.
The following frame trace shows the flow frame coming in from router C and
being sent to router A which followed by 6 transfer frames and a response flow
frame arriving from router A. Note now that the router B forwards 3 of the 6
transfers to router C and tries sending the response flow frame before the
remaining 3 transfers. Because of this the receiver is not seeing all 10
messages.
{noformat}
Fri Mar 3 13:49:11 2017 SERVER (trace) [3]:4 <- @flow(19) [next-incoming-id=4,
incoming-window=2147483647, next-outgoing-id=0, outgoing-window=2147483647,
handle=0, delivery-count=4, link-credit=20, drain=true]
(/home/gmurthy/opensource/dispatch/src/server.c:197)
Fri Mar 3 13:49:11 2017 ROUTER_CORE (trace) Core action 'link_flow'
(/home/gmurthy/opensource/dispatch/src/router_core/router_core_thread.c:82)
Fri Mar 3 13:49:11 2017 SERVER (trace) [2]:0 -> @flow(19) [next-incoming-id=4,
incoming-window=2147483647, next-outgoing-id=0, outgoing-window=2147483647,
handle=0, delivery-count=4, link-credit=20, drain=true]
(/home/gmurthy/opensource/dispatch/src/server.c:197)
Fri Mar 3 13:49:11 2017 SERVER (trace) [2]:0 <- @transfer(20) [handle=0,
delivery-id=4, delivery-tag=b"\x04\x00\x00\x00\x00\x00\x00\x00",
message-format=0, settled=true, more=false] (96)
"\x00Sp\xd0\x00\x00\x00\x0b\x00\x00\x00\x05BP\x04@BR\x00\x00Ss\xd0\x00\x00\x00"\x00\x00\x00\x0d\x83\x00\x00\x00\x00\x00\x00\x00\x00\x83\x00\x00\x00\x00\x00\x00\x00\x00@R\x00@\x00St\xd1\x00\x00\x00\x0b\x00\x00\x00\x02\xa0\x03seqT\x04\x00Sw\xa0\x0bHello
World" (/home/gmurthy/opensource/dispatch/src/server.c:197)
Fri Mar 3 13:49:11 2017 SERVER (trace) [2]:0 <- @transfer(20) [handle=0,
delivery-id=5, delivery-tag=b"\x05\x00\x00\x00\x00\x00\x00\x00",
message-format=0, settled=true, more=false] (96)
"\x00Sp\xd0\x00\x00\x00\x0b\x00\x00\x00\x05BP\x04@BR\x00\x00Ss\xd0\x00\x00\x00"\x00\x00\x00\x0d\x83\x00\x00\x00\x00\x00\x00\x00\x00\x83\x00\x00\x00\x00\x00\x00\x00\x00@R\x00@\x00St\xd1\x00\x00\x00\x0b\x00\x00\x00\x02\xa0\x03seqT\x05\x00Sw\xa0\x0bHello
World" (/home/gmurthy/opensource/dispatch/src/server.c:197)
Fri Mar 3 13:49:11 2017 SERVER (trace) [2]:0 <- @transfer(20) [handle=0,
delivery-id=6, delivery-tag=b"\x06\x00\x00\x00\x00\x00\x00\x00",
message-format=0, settled=true, more=false] (96)
"\x00Sp\xd0\x00\x00\x00\x0b\x00\x00\x00\x05BP\x04@BR\x00\x00Ss\xd0\x00\x00\x00"\x00\x00\x00\x0d\x83\x00\x00\x00\x00\x00\x00\x00\x00\x83\x00\x00\x00\x00\x00\x00\x00\x00@R\x00@\x00St\xd1\x00\x00\x00\x0b\x00\x00\x00\x02\xa0\x03seqT\x06\x00Sw\xa0\x0bHello
World" (/home/gmurthy/opensource/dispatch/src/server.c:197)
Fri Mar 3 13:49:11 2017 SERVER (trace) [2]:0 <- @transfer(20) [handle
[jira] [Resolved] (QPIDJMS-269) Performance regression affecting MessageProducer on transacted Sessions.
[ https://issues.apache.org/jira/browse/QPIDJMS-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved QPIDJMS-269. -- Resolution: Fixed > Performance regression affecting MessageProducer on transacted Sessions. > > > Key: QPIDJMS-269 > URL: https://issues.apache.org/jira/browse/QPIDJMS-269 > Project: Qpid JMS > Issue Type: Bug > Components: qpid-jms-client >Affects Versions: 0.20.0 >Reporter: Timothy Bish >Assignee: Timothy Bish > Fix For: 0.21.0 > > > The addition of support for JMS 2.0 async senders added some unnecessary > accounting that is causing a regression in performance for transacted message > sends. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDJMS-269) Performance regression affecting MessageProducer on transacted Sessions.
[ https://issues.apache.org/jira/browse/QPIDJMS-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894734#comment-15894734 ] ASF subversion and git services commented on QPIDJMS-269: - Commit 1819bb277f42a895c98c3b764299c0b7371af2e1 in qpid-jms's branch refs/heads/master from [~tabish121] [ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=1819bb2 ] QPIDJMS-269 Resolve performance regression for transacted sends Remove some unnecessary accounting on transacted sends that leads to a performance degradation compared to previous releases. > Performance regression affecting MessageProducer on transacted Sessions. > > > Key: QPIDJMS-269 > URL: https://issues.apache.org/jira/browse/QPIDJMS-269 > Project: Qpid JMS > Issue Type: Bug > Components: qpid-jms-client >Affects Versions: 0.20.0 >Reporter: Timothy Bish >Assignee: Timothy Bish > Fix For: 0.21.0 > > > The addition of support for JMS 2.0 async senders added some unnecessary > accounting that is causing a regression in performance for transacted message > sends. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Comment Edited] (QPIDIT-75) Install QPIDIT correctly in a Docker image
[
https://issues.apache.org/jira/browse/QPIDIT-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894709#comment-15894709
]
Jiri Danek edited comment on QPIDIT-75 at 3/3/17 5:01 PM:
--
In the last iteration is seems to be a broker enhancement ;) see
https://issues.jboss.org/browse/ENTMQBR-558
My understanding is that QPIDIT needs to ensure that receiver starts listening
before sender does the sending, otherwise the message will be lost.
Alternatively, running QPIDIT may require that queues be precreated on the
Artemis 2.0.0 broker.
edit: I previously linked wrong issue
was (Author: jdanek):
In the last iteration is seems to be a broker enhancement ;) see
https://issues.jboss.org/browse/ENTMQBR-520
My understanding is that QPIDIT needs to ensure that receiver starts listening
before sender does the sending, otherwise the message will be lost.
Alternatively, running QPIDIT may require that queues be precreated on the
Artemis 2.0.0 broker.
> Install QPIDIT correctly in a Docker image
> --
>
> Key: QPIDIT-75
> URL: https://issues.apache.org/jira/browse/QPIDIT-75
> Project: Apache QPID IT
> Issue Type: Test
> Components: Installation
>Reporter: Jiri Danek
>Assignee: Kim van der Riet
>Priority: Minor
> Attachments: Dockerfile
>
>
> I checked out QPID-IT and wanted to run it for myself. I decided to use
> Fedora 25 in docker, because I wanted to have a reproducible setup.
> I created a Dockerfile which installs prerequisites and QPID-IT. When I run
> tests, it always freezes after few tests.
> Is there anything wrong about the install?
> Steps to use the Dockerfile
> 1) place the Dockerfile in the top directory of qpid-interop-test
> 2) {{% docker build -t interop .}}
> 3) {{% docker run --rm -it interop bash -c "/artemis200i0/bin/artemis-service
> start; sleep 10; export PYTHONPATH=/usr/lib64/proton/bindings/python/; export
> QIT_INSTALL_PREFIX=/usr; src/python/qpid_interop_test/amqp_types_test.py
> --exclude-shim RheaJs"}}
> {noformat}
> Starting artemis-service
> artemis-service is now running (14)
> WARNING: AMQP DotNetLite shims not installed
> Test Broker: apache-activemq-artemis v.2.0.0-SNAPSHOT on
> test_binary_ProtonCpp->ProtonCpp (__main__.BinaryTestCase) ... ok
> test_binary_ProtonCpp->ProtonPython (__main__.BinaryTestCase) ... ok
> test_binary_ProtonPython->ProtonCpp (__main__.BinaryTestCase) ... ok
> test_binary_ProtonPython->ProtonPython (__main__.BinaryTestCase) ... ok
> test_boolean_ProtonCpp->ProtonCpp (__main__.BooleanTestCase) ...
> {noformat}
> And it stays stuck for quite long time. The output is the same every time I
> run this. I did not wait for long enough to see if it gets unstuck, I admit.
> If I run this with the 1.5.3 broker, meaning in step 3) I do {{% docker run
> --rm -it interop bash -c "/artemis153i0/bin/artemis-service start; sleep 10;
> export PYTHONPATH=/usr/lib64/proton/bindings/python/; export
> QIT_INSTALL_PREFIX=/usr; src/python/qpid_interop_test/amqp_types_test.py
> --exclude-shim RheaJs"}} then the tests seem to succeed, so maybe it is just
> incompatible with Artemis 2.0.0...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDIT-75) Install QPIDIT correctly in a Docker image
[
https://issues.apache.org/jira/browse/QPIDIT-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894710#comment-15894710
]
Jiri Danek commented on QPIDIT-75:
--
So in other words the problem has nothing to do with Docker.
> Install QPIDIT correctly in a Docker image
> --
>
> Key: QPIDIT-75
> URL: https://issues.apache.org/jira/browse/QPIDIT-75
> Project: Apache QPID IT
> Issue Type: Test
> Components: Installation
>Reporter: Jiri Danek
>Assignee: Kim van der Riet
>Priority: Minor
> Attachments: Dockerfile
>
>
> I checked out QPID-IT and wanted to run it for myself. I decided to use
> Fedora 25 in docker, because I wanted to have a reproducible setup.
> I created a Dockerfile which installs prerequisites and QPID-IT. When I run
> tests, it always freezes after few tests.
> Is there anything wrong about the install?
> Steps to use the Dockerfile
> 1) place the Dockerfile in the top directory of qpid-interop-test
> 2) {{% docker build -t interop .}}
> 3) {{% docker run --rm -it interop bash -c "/artemis200i0/bin/artemis-service
> start; sleep 10; export PYTHONPATH=/usr/lib64/proton/bindings/python/; export
> QIT_INSTALL_PREFIX=/usr; src/python/qpid_interop_test/amqp_types_test.py
> --exclude-shim RheaJs"}}
> {noformat}
> Starting artemis-service
> artemis-service is now running (14)
> WARNING: AMQP DotNetLite shims not installed
> Test Broker: apache-activemq-artemis v.2.0.0-SNAPSHOT on
> test_binary_ProtonCpp->ProtonCpp (__main__.BinaryTestCase) ... ok
> test_binary_ProtonCpp->ProtonPython (__main__.BinaryTestCase) ... ok
> test_binary_ProtonPython->ProtonCpp (__main__.BinaryTestCase) ... ok
> test_binary_ProtonPython->ProtonPython (__main__.BinaryTestCase) ... ok
> test_boolean_ProtonCpp->ProtonCpp (__main__.BooleanTestCase) ...
> {noformat}
> And it stays stuck for quite long time. The output is the same every time I
> run this. I did not wait for long enough to see if it gets unstuck, I admit.
> If I run this with the 1.5.3 broker, meaning in step 3) I do {{% docker run
> --rm -it interop bash -c "/artemis153i0/bin/artemis-service start; sleep 10;
> export PYTHONPATH=/usr/lib64/proton/bindings/python/; export
> QIT_INSTALL_PREFIX=/usr; src/python/qpid_interop_test/amqp_types_test.py
> --exclude-shim RheaJs"}} then the tests seem to succeed, so maybe it is just
> incompatible with Artemis 2.0.0...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDIT-75) Install QPIDIT correctly in a Docker image
[
https://issues.apache.org/jira/browse/QPIDIT-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894709#comment-15894709
]
Jiri Danek commented on QPIDIT-75:
--
In the last iteration is seems to be a broker enhancement ;) see
https://issues.jboss.org/browse/ENTMQBR-520
My understanding is that QPIDIT needs to ensure that receiver starts listening
before sender does the sending, otherwise the message will be lost.
Alternatively, running QPIDIT may require that queues be precreated on the
Artemis 2.0.0 broker.
> Install QPIDIT correctly in a Docker image
> --
>
> Key: QPIDIT-75
> URL: https://issues.apache.org/jira/browse/QPIDIT-75
> Project: Apache QPID IT
> Issue Type: Test
> Components: Installation
>Reporter: Jiri Danek
>Assignee: Kim van der Riet
>Priority: Minor
> Attachments: Dockerfile
>
>
> I checked out QPID-IT and wanted to run it for myself. I decided to use
> Fedora 25 in docker, because I wanted to have a reproducible setup.
> I created a Dockerfile which installs prerequisites and QPID-IT. When I run
> tests, it always freezes after few tests.
> Is there anything wrong about the install?
> Steps to use the Dockerfile
> 1) place the Dockerfile in the top directory of qpid-interop-test
> 2) {{% docker build -t interop .}}
> 3) {{% docker run --rm -it interop bash -c "/artemis200i0/bin/artemis-service
> start; sleep 10; export PYTHONPATH=/usr/lib64/proton/bindings/python/; export
> QIT_INSTALL_PREFIX=/usr; src/python/qpid_interop_test/amqp_types_test.py
> --exclude-shim RheaJs"}}
> {noformat}
> Starting artemis-service
> artemis-service is now running (14)
> WARNING: AMQP DotNetLite shims not installed
> Test Broker: apache-activemq-artemis v.2.0.0-SNAPSHOT on
> test_binary_ProtonCpp->ProtonCpp (__main__.BinaryTestCase) ... ok
> test_binary_ProtonCpp->ProtonPython (__main__.BinaryTestCase) ... ok
> test_binary_ProtonPython->ProtonCpp (__main__.BinaryTestCase) ... ok
> test_binary_ProtonPython->ProtonPython (__main__.BinaryTestCase) ... ok
> test_boolean_ProtonCpp->ProtonCpp (__main__.BooleanTestCase) ...
> {noformat}
> And it stays stuck for quite long time. The output is the same every time I
> run this. I did not wait for long enough to see if it gets unstuck, I admit.
> If I run this with the 1.5.3 broker, meaning in step 3) I do {{% docker run
> --rm -it interop bash -c "/artemis153i0/bin/artemis-service start; sleep 10;
> export PYTHONPATH=/usr/lib64/proton/bindings/python/; export
> QIT_INSTALL_PREFIX=/usr; src/python/qpid_interop_test/amqp_types_test.py
> --exclude-shim RheaJs"}} then the tests seem to succeed, so maybe it is just
> incompatible with Artemis 2.0.0...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7618) Ring policy type
[ https://issues.apache.org/jira/browse/QPID-7618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894695#comment-15894695 ] ASF subversion and git services commented on QPID-7618: --- Commit 1785348 from oru...@apache.org in branch 'java/trunk' [ https://svn.apache.org/r1785348 ] QPID-7618: Address review comments from Keith Wall > Ring policy type > > > Key: QPID-7618 > URL: https://issues.apache.org/jira/browse/QPID-7618 > Project: Qpid > Issue Type: New Feature > Components: Java Broker >Affects Versions: qpid-java-6.1.1, qpid-java-7.0 >Reporter: Tomas Vavricka >Assignee: Keith Wall > Labels: policy-type, queue, ring > Fix For: qpid-java-7.0 > > Attachments: 0001-QPID-7569-Ring-policy-type.patch > > > It would be good if Java Broker will support ring policy. > Ring policy - delete oldest message(s) when queue capacity is reached > Queue capacity can be defined by maximum count of message and maximum size of > messages (including header). -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPIDIT-78) Add AMQP local transaction test
Kim van der Riet created QPIDIT-78: -- Summary: Add AMQP local transaction test Key: QPIDIT-78 URL: https://issues.apache.org/jira/browse/QPIDIT-78 Project: Apache QPID IT Issue Type: New Feature Reporter: Kim van der Riet Assignee: Kim van der Riet Add an AMQP local transaction test. This will test a local transaction where the scope of the transaction will be limited to a single client. Multiple actions may be performed on multiple queues and need to comply with the atomic constraints imposed by the transaction. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPIDIT-75) Install QPIDIT correctly in a Docker image
[
https://issues.apache.org/jira/browse/QPIDIT-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim van der Riet reassigned QPIDIT-75:
--
Assignee: Kim van der Riet
> Install QPIDIT correctly in a Docker image
> --
>
> Key: QPIDIT-75
> URL: https://issues.apache.org/jira/browse/QPIDIT-75
> Project: Apache QPID IT
> Issue Type: Test
> Components: Installation
>Reporter: Jiri Danek
>Assignee: Kim van der Riet
>Priority: Minor
> Attachments: Dockerfile
>
>
> I checked out QPID-IT and wanted to run it for myself. I decided to use
> Fedora 25 in docker, because I wanted to have a reproducible setup.
> I created a Dockerfile which installs prerequisites and QPID-IT. When I run
> tests, it always freezes after few tests.
> Is there anything wrong about the install?
> Steps to use the Dockerfile
> 1) place the Dockerfile in the top directory of qpid-interop-test
> 2) {{% docker build -t interop .}}
> 3) {{% docker run --rm -it interop bash -c "/artemis200i0/bin/artemis-service
> start; sleep 10; export PYTHONPATH=/usr/lib64/proton/bindings/python/; export
> QIT_INSTALL_PREFIX=/usr; src/python/qpid_interop_test/amqp_types_test.py
> --exclude-shim RheaJs"}}
> {noformat}
> Starting artemis-service
> artemis-service is now running (14)
> WARNING: AMQP DotNetLite shims not installed
> Test Broker: apache-activemq-artemis v.2.0.0-SNAPSHOT on
> test_binary_ProtonCpp->ProtonCpp (__main__.BinaryTestCase) ... ok
> test_binary_ProtonCpp->ProtonPython (__main__.BinaryTestCase) ... ok
> test_binary_ProtonPython->ProtonCpp (__main__.BinaryTestCase) ... ok
> test_binary_ProtonPython->ProtonPython (__main__.BinaryTestCase) ... ok
> test_boolean_ProtonCpp->ProtonCpp (__main__.BooleanTestCase) ...
> {noformat}
> And it stays stuck for quite long time. The output is the same every time I
> run this. I did not wait for long enough to see if it gets unstuck, I admit.
> If I run this with the 1.5.3 broker, meaning in step 3) I do {{% docker run
> --rm -it interop bash -c "/artemis153i0/bin/artemis-service start; sleep 10;
> export PYTHONPATH=/usr/lib64/proton/bindings/python/; export
> QIT_INSTALL_PREFIX=/usr; src/python/qpid_interop_test/amqp_types_test.py
> --exclude-shim RheaJs"}} then the tests seem to succeed, so maybe it is just
> incompatible with Artemis 2.0.0...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Assigned] (QPIDIT-76) Add Qpid Proton Go shim for amqp_types_test
[ https://issues.apache.org/jira/browse/QPIDIT-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet reassigned QPIDIT-76: -- Assignee: Kim van der Riet > Add Qpid Proton Go shim for amqp_types_test > --- > > Key: QPIDIT-76 > URL: https://issues.apache.org/jira/browse/QPIDIT-76 > Project: Apache QPID IT > Issue Type: New Feature > Environment: go 1.7, 1.8, maybe 1.6 >Reporter: Jiri Danek >Assignee: Kim van der Riet >Priority: Minor > > Qpid Proton Go is a AMQP client currently in development. Some AMQP types are > not yet supported. > (my personal motivation for looking into this is to eventually write shim for > activemq-client (an OpenWire protocol library); not sure if interop with > other protocols is even in the scope of the QPIDIT project; so I want to get > more familiar with it first) -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDIT-77) Shims always send list items as well as map values and keys encoded as string
[
https://issues.apache.org/jira/browse/QPIDIT-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894653#comment-15894653
]
Jiri Danek commented on QPIDIT-77:
--
Yes, it is a duplicate of QPIDIT-46
> Shims always send list items as well as map values and keys encoded as string
> -
>
> Key: QPIDIT-77
> URL: https://issues.apache.org/jira/browse/QPIDIT-77
> Project: Apache QPID IT
> Issue Type: Bug
> Components: Proton C++ Shim, Proton Python Shim
>Reporter: Jiri Danek
>
> While examining the project and writing my own shim (see QPIDIT-76) I noticed
> that the existing shims seem to behave differently than I would expect.
> When sending the following message
> bq. #
> /usr/libexec/qpid_interop_test/shims/qpid-proton-python/amqp_types_test/Sender.py
> 'localhost:5672'
> 'jms.queue.qpid-interop.amqp_types_test.map.ProtonPython.ProtonGot' 'map'
> '[{}, {"string:one": "ubyte:1", "string:two": "ushort:2"}, {"string:One":
> "long:-1234567890", "none:": "string:None", "short:2": "int:2", "string:map":
> {"char:A": "int:1", "char:B": "int:2"}, "boolean:True": "string:True",
> "string:False": "boolean:False", "string:None": "none:"}]'
> and receiving it with
> {{#
> /usr/libexec/qpid_interop_test/shims/qpid-proton-go/amqp_types_test/Receiver
> 'localhost:5672'
> 'jms.queue.qpid-interop.amqp_types_test.map.ProtonPython.ProtonGot' 'map'
> '3'}}
> My shim printed wrong message, with keys and values looking like
> {{string:boolean:True}}
> {noformat}
> map
> [{},{"string:string:one":"string:ubyte:1","string:string:two":"string:ushort:2"},{"string:boolean:True":"string:string:True","string:none:":"string:string:None","string:short:2":"string:int:2","string:string:False":"string:boolean:False","string:string:None":"string:none:","string:string:One":"string:long:-1234567890","string:string:map":{"string:char:A":"string:int:1","string:char:B":"string:int:2"}}]
> {noformat}
> I suspected my code, but when I deliberately made my code "wrong", see commit
> https://github.com/jdanekrh/qpid-interop-test/commit/bdaca47959083ef0c54656adb38285486316553b,
> the shim started working.
> For the above reason, I suspect that when shims (at least the Python one and
> C++ one, these I tried) put data into map keys, map values and list items as
> strings, without bothering to convert them.
> This sounds sort of incredible how could this happen, but having no tool to
> print messages in-flight and given that the change in the commit above fixed
> my shim, I think it is plausible.
> -I looked at code of the other shims, but could not confirm or deny my
> suspicion. The code is for me hard to penetrate.- I think C++ code really
> does what I described above. The question is, is that a bug?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (QPIDIT-77) Shims always send list items as well as map values and keys encoded as string
[
https://issues.apache.org/jira/browse/QPIDIT-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Danek closed QPIDIT-77.
Resolution: Duplicate
> Shims always send list items as well as map values and keys encoded as string
> -
>
> Key: QPIDIT-77
> URL: https://issues.apache.org/jira/browse/QPIDIT-77
> Project: Apache QPID IT
> Issue Type: Bug
> Components: Proton C++ Shim, Proton Python Shim
>Reporter: Jiri Danek
>
> While examining the project and writing my own shim (see QPIDIT-76) I noticed
> that the existing shims seem to behave differently than I would expect.
> When sending the following message
> bq. #
> /usr/libexec/qpid_interop_test/shims/qpid-proton-python/amqp_types_test/Sender.py
> 'localhost:5672'
> 'jms.queue.qpid-interop.amqp_types_test.map.ProtonPython.ProtonGot' 'map'
> '[{}, {"string:one": "ubyte:1", "string:two": "ushort:2"}, {"string:One":
> "long:-1234567890", "none:": "string:None", "short:2": "int:2", "string:map":
> {"char:A": "int:1", "char:B": "int:2"}, "boolean:True": "string:True",
> "string:False": "boolean:False", "string:None": "none:"}]'
> and receiving it with
> {{#
> /usr/libexec/qpid_interop_test/shims/qpid-proton-go/amqp_types_test/Receiver
> 'localhost:5672'
> 'jms.queue.qpid-interop.amqp_types_test.map.ProtonPython.ProtonGot' 'map'
> '3'}}
> My shim printed wrong message, with keys and values looking like
> {{string:boolean:True}}
> {noformat}
> map
> [{},{"string:string:one":"string:ubyte:1","string:string:two":"string:ushort:2"},{"string:boolean:True":"string:string:True","string:none:":"string:string:None","string:short:2":"string:int:2","string:string:False":"string:boolean:False","string:string:None":"string:none:","string:string:One":"string:long:-1234567890","string:string:map":{"string:char:A":"string:int:1","string:char:B":"string:int:2"}}]
> {noformat}
> I suspected my code, but when I deliberately made my code "wrong", see commit
> https://github.com/jdanekrh/qpid-interop-test/commit/bdaca47959083ef0c54656adb38285486316553b,
> the shim started working.
> For the above reason, I suspect that when shims (at least the Python one and
> C++ one, these I tried) put data into map keys, map values and list items as
> strings, without bothering to convert them.
> This sounds sort of incredible how could this happen, but having no tool to
> print messages in-flight and given that the change in the commit above fixed
> my shim, I think it is plausible.
> -I looked at code of the other shims, but could not confirm or deny my
> suspicion. The code is for me hard to penetrate.- I think C++ code really
> does what I described above. The question is, is that a bug?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDIT-75) Install QPIDIT correctly in a Docker image
[
https://issues.apache.org/jira/browse/QPIDIT-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894652#comment-15894652
]
Kim van der Riet commented on QPIDIT-75:
Is this an Artemis bug?
> Install QPIDIT correctly in a Docker image
> --
>
> Key: QPIDIT-75
> URL: https://issues.apache.org/jira/browse/QPIDIT-75
> Project: Apache QPID IT
> Issue Type: Test
> Components: Installation
>Reporter: Jiri Danek
>Priority: Minor
> Attachments: Dockerfile
>
>
> I checked out QPID-IT and wanted to run it for myself. I decided to use
> Fedora 25 in docker, because I wanted to have a reproducible setup.
> I created a Dockerfile which installs prerequisites and QPID-IT. When I run
> tests, it always freezes after few tests.
> Is there anything wrong about the install?
> Steps to use the Dockerfile
> 1) place the Dockerfile in the top directory of qpid-interop-test
> 2) {{% docker build -t interop .}}
> 3) {{% docker run --rm -it interop bash -c "/artemis200i0/bin/artemis-service
> start; sleep 10; export PYTHONPATH=/usr/lib64/proton/bindings/python/; export
> QIT_INSTALL_PREFIX=/usr; src/python/qpid_interop_test/amqp_types_test.py
> --exclude-shim RheaJs"}}
> {noformat}
> Starting artemis-service
> artemis-service is now running (14)
> WARNING: AMQP DotNetLite shims not installed
> Test Broker: apache-activemq-artemis v.2.0.0-SNAPSHOT on
> test_binary_ProtonCpp->ProtonCpp (__main__.BinaryTestCase) ... ok
> test_binary_ProtonCpp->ProtonPython (__main__.BinaryTestCase) ... ok
> test_binary_ProtonPython->ProtonCpp (__main__.BinaryTestCase) ... ok
> test_binary_ProtonPython->ProtonPython (__main__.BinaryTestCase) ... ok
> test_boolean_ProtonCpp->ProtonCpp (__main__.BooleanTestCase) ...
> {noformat}
> And it stays stuck for quite long time. The output is the same every time I
> run this. I did not wait for long enough to see if it gets unstuck, I admit.
> If I run this with the 1.5.3 broker, meaning in step 3) I do {{% docker run
> --rm -it interop bash -c "/artemis153i0/bin/artemis-service start; sleep 10;
> export PYTHONPATH=/usr/lib64/proton/bindings/python/; export
> QIT_INSTALL_PREFIX=/usr; src/python/qpid_interop_test/amqp_types_test.py
> --exclude-shim RheaJs"}} then the tests seem to succeed, so maybe it is just
> incompatible with Artemis 2.0.0...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPIDIT-77) Shims always send list items as well as map values and keys encoded as string
[
https://issues.apache.org/jira/browse/QPIDIT-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894650#comment-15894650
]
Kim van der Riet commented on QPIDIT-77:
This is a bug. I think it is a duplicate of QPIDIT-46. Can you review that bug
and see if you agree. If so, please mark this as a dup of that bug.
> Shims always send list items as well as map values and keys encoded as string
> -
>
> Key: QPIDIT-77
> URL: https://issues.apache.org/jira/browse/QPIDIT-77
> Project: Apache QPID IT
> Issue Type: Bug
> Components: Proton C++ Shim, Proton Python Shim
>Reporter: Jiri Danek
>
> While examining the project and writing my own shim (see QPIDIT-76) I noticed
> that the existing shims seem to behave differently than I would expect.
> When sending the following message
> bq. #
> /usr/libexec/qpid_interop_test/shims/qpid-proton-python/amqp_types_test/Sender.py
> 'localhost:5672'
> 'jms.queue.qpid-interop.amqp_types_test.map.ProtonPython.ProtonGot' 'map'
> '[{}, {"string:one": "ubyte:1", "string:two": "ushort:2"}, {"string:One":
> "long:-1234567890", "none:": "string:None", "short:2": "int:2", "string:map":
> {"char:A": "int:1", "char:B": "int:2"}, "boolean:True": "string:True",
> "string:False": "boolean:False", "string:None": "none:"}]'
> and receiving it with
> {{#
> /usr/libexec/qpid_interop_test/shims/qpid-proton-go/amqp_types_test/Receiver
> 'localhost:5672'
> 'jms.queue.qpid-interop.amqp_types_test.map.ProtonPython.ProtonGot' 'map'
> '3'}}
> My shim printed wrong message, with keys and values looking like
> {{string:boolean:True}}
> {noformat}
> map
> [{},{"string:string:one":"string:ubyte:1","string:string:two":"string:ushort:2"},{"string:boolean:True":"string:string:True","string:none:":"string:string:None","string:short:2":"string:int:2","string:string:False":"string:boolean:False","string:string:None":"string:none:","string:string:One":"string:long:-1234567890","string:string:map":{"string:char:A":"string:int:1","string:char:B":"string:int:2"}}]
> {noformat}
> I suspected my code, but when I deliberately made my code "wrong", see commit
> https://github.com/jdanekrh/qpid-interop-test/commit/bdaca47959083ef0c54656adb38285486316553b,
> the shim started working.
> For the above reason, I suspect that when shims (at least the Python one and
> C++ one, these I tried) put data into map keys, map values and list items as
> strings, without bothering to convert them.
> This sounds sort of incredible how could this happen, but having no tool to
> print messages in-flight and given that the change in the commit above fixed
> my shim, I think it is plausible.
> -I looked at code of the other shims, but could not confirm or deny my
> suspicion. The code is for me hard to penetrate.- I think C++ code really
> does what I described above. The question is, is that a bug?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPIDJMS-269) Performance regression affecting MessageProducer on transacted Sessions.
Timothy Bish created QPIDJMS-269: Summary: Performance regression affecting MessageProducer on transacted Sessions. Key: QPIDJMS-269 URL: https://issues.apache.org/jira/browse/QPIDJMS-269 Project: Qpid JMS Issue Type: Bug Components: qpid-jms-client Affects Versions: 0.20.0 Reporter: Timothy Bish Assignee: Timothy Bish Fix For: 0.21.0 The addition of support for JMS 2.0 async senders added some unnecessary accounting that is causing a regression in performance for transacted message sends. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (PROTON-1408) long-lived connections suffer large performance hit after many messages
[ https://issues.apache.org/jira/browse/PROTON-1408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated PROTON-1408: Huh! Well you did find a real bug, albeit by a twisty road so well done there. Any idea what other variables might be in play? Changed versions of proton? OS upgrades? Other stuff running on the box? Gamma rays? Interference from Warrior-level network access? Mysterious. > long-lived connections suffer large performance hit after many messages > --- > > Key: PROTON-1408 > URL: https://issues.apache.org/jira/browse/PROTON-1408 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Reporter: michael goulish >Assignee: Alan Conway > > In long-running soak tests, in which connections are never taken down, I am > seeing a sudden & severe performance degradation when the number of messages > over the connection reaches about 6.4 billion. > This is happening in tests with two senders, two receivers & one router > intermediating. > I have tried C libUV clients as well as CPP clients. Behavior is not > identical, but I see sudden performance drop, ie. 8x throughput decrease or > worse, in both cases. > Alan / Ted / Ken see an issue in use of improper comparison logic in > pn_do_disposition(), in transport.c . I am trying to prove this now. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7647) [Java Broker] fix handling of broker type in configuration
[
https://issues.apache.org/jira/browse/QPID-7647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894454#comment-15894454
]
ASF subversion and git services commented on QPID-7647:
---
Commit 1785311 from oru...@apache.org in branch 'java/trunk'
[ https://svn.apache.org/r1785311 ]
QPID-7647: [Java Broker] Address review comments from Keith Wall
> [Java Broker] fix handling of broker type in configuration
> --
>
> Key: QPID-7647
> URL: https://issues.apache.org/jira/browse/QPID-7647
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: qpid-java-6.0, qpid-java-6.1, qpid-java-6.0.6,
> qpid-java-6.1.1, qpid-java-7.0
>Reporter: Lorenz Quack
>Priority: Minor
> Fix For: qpid-java-7.0, qpid-java-6.1.2, qpid-java-6.0.7
>
>
> In the default configuration the broker does store its own type explicitly.
> In this case there is not problem.
> If an explicit "type" is set in the config there might be one of a number of
> issues. The root of the problem is that the default type pre v6 was "broker"
> but in QPID-6911 this was changed to "Broker" for trunk (6.1.x at the time)
> and backported to 6.0. There was no upgrader added.
> If the "type" is set to "broker" in the 0.32 config and an upgrade to 6.0 is
> attempted it will fail with the following error:
> {noformat}
> 13:33:26.203 [main] ERROR org.apache.qpid.server.Broker - Exception during
> startup
> org.apache.qpid.server.configuration.IllegalConfigurationException: Provided
> type is broker but calculated type is Broker
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.(AbstractConfiguredObject.java:264)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.(AbstractConfiguredObject.java:205)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.(AbstractConfiguredObject.java:197)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at
> org.apache.qpid.server.model.adapter.BrokerAdapter.(BrokerAdapter.java:138)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at
> org.apache.qpid.server.model.adapter.BrokerAdapterFactory.createInstance(BrokerAdapterFactory.java:39)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at
> org.apache.qpid.server.model.adapter.BrokerAdapterFactory.createInstance(BrokerAdapterFactory.java:28)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at
> org.apache.qpid.server.model.AbstractConfiguredObjectTypeFactory$GenericUnresolvedConfiguredObject.resolve(AbstractConfiguredObjectTypeFactory.java:145)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at
> org.apache.qpid.server.model.AbstractConfiguredObjectTypeFactory$GenericUnresolvedConfiguredObject.resolve(AbstractConfiguredObjectTypeFactory.java:125)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at
> org.apache.qpid.server.store.GenericRecoverer.resolveObjects(GenericRecoverer.java:186)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at
> org.apache.qpid.server.store.GenericRecoverer.performRecover(GenericRecoverer.java:91)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at
> org.apache.qpid.server.store.GenericRecoverer.access$000(GenericRecoverer.java:41)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at
> org.apache.qpid.server.store.GenericRecoverer$1.execute(GenericRecoverer.java:59)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at
> org.apache.qpid.server.store.GenericRecoverer$1.execute(GenericRecoverer.java:55)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:270)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl.submitWrappedTask(TaskExecutorImpl.java:154)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl.run(TaskExecutorImpl.java:182)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at
> org.apache.qpid.server.store.GenericRecoverer.recover(GenericRecoverer.java:54)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at
> org.apache.qpid.server.store.BrokerStoreUpgraderAndRecoverer.perform(BrokerStoreUpgraderAndRecoverer.java:791)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at
> org.apache.qpid.server.model.AbstractSystemConfig.activate(AbstractSystemConfig.java:231)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[na:1.8.0_111]
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[na:1.8.0_111]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[na:1.8.0_111]
> at jav
[jira] [Commented] (QPID-7558) [Java Broker] Allow Multiple JDBC Virtual Hosts / Message Stores to share the same database
[ https://issues.apache.org/jira/browse/QPID-7558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894421#comment-15894421 ] ASF subversion and git services commented on QPID-7558: --- Commit 1785308 from oru...@apache.org in branch 'java/branches/6.1.x' [ https://svn.apache.org/r1785308 ] QPID-7558: [Java Broker] Make attributes for table name prefix unsecure and immutable, and modify corresponding UI to allow entering of table prefixes. merged from trunk using svn merge -c 1785269 ^/qpid/java/trunk merge conflicts resolved manually > [Java Broker] Allow Multiple JDBC Virtual Hosts / Message Stores to share the > same database > --- > > Key: QPID-7558 > URL: https://issues.apache.org/jira/browse/QPID-7558 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Rob Godfrey > Fix For: qpid-java-7.0, qpid-java-6.1.2 > > Attachments: > 0001-QPID-7558-Java-Broker-whitelist-validValuePattern-fo.patch, > QPID-7558_v6.1.patch > > > As per the e-mail discussion on the users list > [here|http://mail-archives.apache.org/mod_mbox/qpid-users/201611.mbox/%3CCACMpbT81LATE1d2M4L%2B%3D1uq_CDPnx8y56Md0w362xS54-yGVeg%40mail.gmail.com%3E] > it may sometimes be useful for the user to be able to configure a JDBC > store to use a per-instance table name prefix to allow multiple instances to > be run against the same database/schema. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7668) [Java Broker] Add MySQL configuration to the set of known DBMS types in JDBCDetails
[ https://issues.apache.org/jira/browse/QPID-7668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894405#comment-15894405 ] ASF subversion and git services commented on QPID-7668: --- Commit 1785304 from oru...@apache.org in branch 'java/branches/6.1.x' [ https://svn.apache.org/r1785304 ] QPID-7668: [Java Broker] Add suport for another port of MySQL - MariaDB merged from trunk using svn merge -c 1785270 ^/qpid/java/trunk > [Java Broker] Add MySQL configuration to the set of known DBMS types in > JDBCDetails > --- > > Key: QPID-7668 > URL: https://issues.apache.org/jira/browse/QPID-7668 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey >Priority: Minor > Fix For: qpid-java-7.0, qpid-java-6.1.2 > > > JDBCDetails.java contains configurations for the JDBC store for popular (SQL) > database types. Add configuration for MySQL to that list. > (From a pull request on the github mirror: > https://github.com/apache/qpid-java/pull/2 ) -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7690) [Java Broker] Cannot create VirtualHostLogger with certain ACLs in place
[
https://issues.apache.org/jira/browse/QPID-7690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894404#comment-15894404
]
Lorenz Quack commented on QPID-7690:
Alex suggested the bug might be in the {{isVirtualHostType()}} branch of
{{LegacyAccessControlAdapter#getACLObjectProperties}} where we should be adding
the {{ObjectProperties.Property.VIRTUALHOST_NAME}} property.
> [Java Broker] Cannot create VirtualHostLogger with certain ACLs in place
>
>
> Key: QPID-7690
> URL: https://issues.apache.org/jira/browse/QPID-7690
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Reporter: Lorenz Quack
> Fix For: qpid-java-7.0, qpid-java-6.1.2
>
>
> If the following ACL is in place
> {noformat}
> ACL ALLOW foo ALL ALL virtualhost_name="test"
> ACL DENY-LOG ALL ALL
> {noformat}
> the first rule should allow the user {{foo}} to create VirtualHostLoggers on
> the virtual host called {{test}}.
> However this currently fails with a 403 Access Denied error.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7690) [Java Broker] Cannot create VirtualHostLogger with certain ACLs in place
[
https://issues.apache.org/jira/browse/QPID-7690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lorenz Quack updated QPID-7690:
---
Fix Version/s: qpid-java-6.1.2
qpid-java-7.0
> [Java Broker] Cannot create VirtualHostLogger with certain ACLs in place
>
>
> Key: QPID-7690
> URL: https://issues.apache.org/jira/browse/QPID-7690
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Reporter: Lorenz Quack
> Fix For: qpid-java-7.0, qpid-java-6.1.2
>
>
> If the following ACL is in place
> {noformat}
> ACL ALLOW foo ALL ALL virtualhost_name="test"
> ACL DENY-LOG ALL ALL
> {noformat}
> the first rule should allow the user {{foo}} to create VirtualHostLoggers on
> the virtual host called {{test}}.
> However this currently fails with a 403 Access Denied error.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-7690) [Java Broker] Cannot create VirtualHostLogger with certain ACLs in place
Lorenz Quack created QPID-7690:
--
Summary: [Java Broker] Cannot create VirtualHostLogger with
certain ACLs in place
Key: QPID-7690
URL: https://issues.apache.org/jira/browse/QPID-7690
Project: Qpid
Issue Type: Bug
Components: Java Broker
Reporter: Lorenz Quack
If the following ACL is in place
{noformat}
ACL ALLOW foo ALL ALL virtualhost_name="test"
ACL DENY-LOG ALL ALL
{noformat}
the first rule should allow the user {{foo}} to create VirtualHostLoggers on
the virtual host called {{test}}.
However this currently fails with a 403 Access Denied error.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7643) Cannot login using SASL PLAIN against Base64MD5PasswordFilePrincipalDatabase
[
https://issues.apache.org/jira/browse/QPID-7643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894317#comment-15894317
]
ASF subversion and git services commented on QPID-7643:
---
Commit 1785293 from oru...@apache.org in branch 'java/branches/6.0.x'
[ https://svn.apache.org/r1785293 ]
QPID-7643: [Java Broker] Fix support for SASL mechanism 'PLAIN' in
Base64MD5PasswordFile authentication provider
merged from 6.1.x branch using
svn merge -c 1785143 ^/qpid/java/branches/6.1.x
merge conflicts resolved manually
> Cannot login using SASL PLAIN against Base64MD5PasswordFilePrincipalDatabase
>
>
> Key: QPID-7643
> URL: https://issues.apache.org/jira/browse/QPID-7643
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: qpid-java-6.0.6, qpid-java-6.1.1
>Reporter: Keith Wall
>Priority: Minor
> Fix For: qpid-java-6.1.2, qpid-java-6.0.7
>
>
> There is a defect in Base64MD5PasswordFilePrincipalDatabase that means that
> whilst the a authentication provider of type {{Base64MD5PasswordFile}}
> advertises {{PLAIN}} at attempt to use it fails later with following stack
> trace reported by the client.
> The user who wishes to use PLAIN can work around by using an alternative
> authentication provider that offers plain support e.g. SCRAM.
> {noformat}
> /Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/bin/java
> -Dqpid.amqp.version=0-10 -Dqpid.sasl_mechs=PLAIN -Didea.launcher.port=7537
> "-Didea.launcher.bin.path=/Applications/IntelliJ IDEA.app/Contents/bin"
> -Dfile.encoding=UTF-8 -classpath
> "/Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/jre/lib/charsets.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/jre/lib/deploy.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/jre/lib/ext/cldrdata.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/jre/lib/ext/dnsns.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/jre/lib/ext/jaccess.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/jre/lib/ext/jfxrt.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/jre/lib/ext/localedata.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/jre/lib/ext/nashorn.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/jre/lib/ext/sunec.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/jre/lib/ext/sunjce_provider.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/jre/lib/ext/sunpkcs11.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/jre/lib/ext/zipfs.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/jre/lib/javaws.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/jre/lib/jce.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/jre/lib/jfr.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/jre/lib/jfxswt.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/jre/lib/jsse.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/jre/lib/management-agent.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/jre/lib/plugin.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/jre/lib/resources.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/jre/lib/rt.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/lib/ant-javafx.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/lib/dt.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/lib/javafx-mx.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/lib/jconsole.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/lib/packager.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/lib/sa-jdi.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_121.jdk/Contents/Home/lib/tools.jar:/Users/keith/src/qpid-java/client/example/target/classes:/Users/keith/src/qpid-java/client/target/classes:/Users/keith/src/qpid-java/common/target/classes:/Users/keith/.m2/repository/org/apache/geronimo/specs/geronimo-jms_1.1_spec/1.1.1/geronimo-jms_1.1_spec-1.1.1.jar:/Users/keith/.m2/repository/org/slf4j/slf4j-api/1.7.12/slf4j-api-1.7.12.jar:/Applications/IntelliJ
> IDEA.app/Contents/lib/idea_rt.jar"
> com.intellij.rt.execution.application.AppMain org.apache.qpid.example.Hello
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
> details.
> javax.jms.JMSException: Error creating connection: Unsupported
[jira] [Commented] (QPID-7631) [Java Broker, WMC] In BDBHA 2-node group you should be able to configure priority
[ https://issues.apache.org/jira/browse/QPID-7631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894275#comment-15894275 ] ASF subversion and git services commented on QPID-7631: --- Commit 1785284 from oru...@apache.org in branch 'java/branches/6.0.x' [ https://svn.apache.org/r1785284 ] QPID-7631: Enable changing of BDB HA node priority regadless the size of the group merged from 6.1.x branch using svn merge -c 1785279 ^/qpid/java/branches/6.1.x merge conflicts resolved manually > [Java Broker, WMC] In BDBHA 2-node group you should be able to configure > priority > - > > Key: QPID-7631 > URL: https://issues.apache.org/jira/browse/QPID-7631 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Lorenz Quack >Assignee: Alex Rudyy >Priority: Minor > Fix For: qpid-java-7.0, qpid-java-6.1.2 > > > Currently, we disable the edit field for priority when there are only two > nodes in the HA group. I don't see a reason to do this. > Note that priority is different from "designated primary"/"allow to run solo". > This is a UI issue only -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7631) [Java Broker, WMC] In BDBHA 2-node group you should be able to configure priority
[ https://issues.apache.org/jira/browse/QPID-7631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894236#comment-15894236 ] ASF subversion and git services commented on QPID-7631: --- Commit 1785279 from oru...@apache.org in branch 'java/branches/6.1.x' [ https://svn.apache.org/r1785279 ] QPID-7631: Enable changing of BDB HA node priority regadless the size of the group svn merge -c 1785117 ^/qpid/java/trunk > [Java Broker, WMC] In BDBHA 2-node group you should be able to configure > priority > - > > Key: QPID-7631 > URL: https://issues.apache.org/jira/browse/QPID-7631 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Lorenz Quack >Assignee: Alex Rudyy >Priority: Minor > Fix For: qpid-java-7.0, qpid-java-6.1.2 > > > Currently, we disable the edit field for priority when there are only two > nodes in the HA group. I don't see a reason to do this. > Note that priority is different from "designated primary"/"allow to run solo". > This is a UI issue only -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7668) [Java Broker] Add MySQL configuration to the set of known DBMS types in JDBCDetails
[ https://issues.apache.org/jira/browse/QPID-7668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894196#comment-15894196 ] ASF subversion and git services commented on QPID-7668: --- Commit 1785270 from oru...@apache.org in branch 'java/trunk' [ https://svn.apache.org/r1785270 ] QPID-7668: [Java Broker] Add suport for another port of MySQL - MariaDB > [Java Broker] Add MySQL configuration to the set of known DBMS types in > JDBCDetails > --- > > Key: QPID-7668 > URL: https://issues.apache.org/jira/browse/QPID-7668 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Rob Godfrey >Assignee: Rob Godfrey >Priority: Minor > Fix For: qpid-java-7.0, qpid-java-6.1.2 > > > JDBCDetails.java contains configurations for the JDBC store for popular (SQL) > database types. Add configuration for MySQL to that list. > (From a pull request on the github mirror: > https://github.com/apache/qpid-java/pull/2 ) -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7558) [Java Broker] Allow Multiple JDBC Virtual Hosts / Message Stores to share the same database
[ https://issues.apache.org/jira/browse/QPID-7558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894195#comment-15894195 ] ASF subversion and git services commented on QPID-7558: --- Commit 1785269 from oru...@apache.org in branch 'java/trunk' [ https://svn.apache.org/r1785269 ] QPID-7558: [Java Broker] Make attributes for table name prefix unsecure and immutable, and modify corresponding UI to allow entering of table prefixes. > [Java Broker] Allow Multiple JDBC Virtual Hosts / Message Stores to share the > same database > --- > > Key: QPID-7558 > URL: https://issues.apache.org/jira/browse/QPID-7558 > Project: Qpid > Issue Type: Improvement > Components: Java Broker >Reporter: Rob Godfrey > Fix For: qpid-java-7.0, qpid-java-6.1.2 > > Attachments: > 0001-QPID-7558-Java-Broker-whitelist-validValuePattern-fo.patch, > QPID-7558_v6.1.patch > > > As per the e-mail discussion on the users list > [here|http://mail-archives.apache.org/mod_mbox/qpid-users/201611.mbox/%3CCACMpbT81LATE1d2M4L%2B%3D1uq_CDPnx8y56Md0w362xS54-yGVeg%40mail.gmail.com%3E] > it may sometimes be useful for the user to be able to configure a JDBC > store to use a per-instance table name prefix to allow multiple instances to > be run against the same database/schema. -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-7689) Queue depth alerting should consider header size too
Keith Wall created QPID-7689: Summary: Queue depth alerting should consider header size too Key: QPID-7689 URL: https://issues.apache.org/jira/browse/QPID-7689 Project: Qpid Issue Type: Improvement Components: Java Broker Reporter: Keith Wall Fix For: qpid-java-7.0 The changes introduced by QPID-7618 have the broker track the size of each queue including header.The new ring queue policy and producer flow control now consider messages sizes including header. The queue depth alerting ought to be consistent. Is there actually value tracking queue size and queue size including header separately? -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Comment Edited] (QPID-7618) Ring policy type
[ https://issues.apache.org/jira/browse/QPID-7618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894134#comment-15894134 ] Keith Wall edited comment on QPID-7618 at 3/3/17 11:24 AM: --- Hi Alex, As discussed - a couple of comments on UI consistency: * Queue tab ** we use queue "depth" and queue "size" interchangeable. Suggest we standardise on the former. ** the presentation of "Maximum Queue Depth" attribute should follow Size attribute i.e. : ( ) ** drop "Size" attribute from RHS ** rename "Size including header" to simply "Size" (Depth in the parlance). ** Message table - rename "Size" to "Payload size". * Queue edit dialoge ** Remove words "including headers" * Message dialogue ** Rename field "Size" to "Payload Size" Documentation: * Move the Overflow Policies Operational Log Messages detail to "Operational Logging" and simply reference from the new content. * Update Managing Entities / Queue to refer to overflow policy a high level and the new associated attributes. * Add summary of the police * Talking about BURLs or ADDRs or 0-8..0-10 wire arguments in the Broker documentation is something we should remove. I imagine a separate section talking about of the queue/exchange arguments understood by 0-8..0-10. I am happy to defer this work for another day. was (Author: k-wall): Hi Alex, As discussed - a couple of comments on UI consistency: * Queue tab ** we use queue "depth" and queue "size" interchangeable. Suggest we standardise on the former. ** the presentation of "Maximum Queue Depth" attribute should follow Size attribute i.e. : ( ) ** drop "Size" attribute from RHS ** rename "Size including header" to simply "Size" (Depth in the parlance). ** Message table - rename "Size" to "Payload size". * Queue edit dialoge ** Remove words "including headers" * Message dialogue ** Rename field "Size" to "Payload Size" > Ring policy type > > > Key: QPID-7618 > URL: https://issues.apache.org/jira/browse/QPID-7618 > Project: Qpid > Issue Type: New Feature > Components: Java Broker >Affects Versions: qpid-java-6.1.1, qpid-java-7.0 >Reporter: Tomas Vavricka >Assignee: Keith Wall > Labels: policy-type, queue, ring > Fix For: qpid-java-7.0 > > Attachments: 0001-QPID-7569-Ring-policy-type.patch > > > It would be good if Java Broker will support ring policy. > Ring policy - delete oldest message(s) when queue capacity is reached > Queue capacity can be defined by maximum count of message and maximum size of > messages (including header). -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7618) Ring policy type
[ https://issues.apache.org/jira/browse/QPID-7618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15894134#comment-15894134 ] Keith Wall commented on QPID-7618: -- Hi Alex, As discussed - a couple of comments on UI consistency: * Queue tab ** we use queue "depth" and queue "size" interchangeable. Suggest we standardise on the former. ** the presentation of "Maximum Queue Depth" attribute should follow Size attribute i.e. : ( ) ** drop "Size" attribute from RHS ** rename "Size including header" to simply "Size" (Depth in the parlance). ** Message table - rename "Size" to "Payload size". * Queue edit dialoge ** Remove words "including headers" * Message dialogue ** Rename field "Size" to "Payload Size" > Ring policy type > > > Key: QPID-7618 > URL: https://issues.apache.org/jira/browse/QPID-7618 > Project: Qpid > Issue Type: New Feature > Components: Java Broker >Affects Versions: qpid-java-6.1.1, qpid-java-7.0 >Reporter: Tomas Vavricka >Assignee: Keith Wall > Labels: policy-type, queue, ring > Fix For: qpid-java-7.0 > > Attachments: 0001-QPID-7569-Ring-policy-type.patch > > > It would be good if Java Broker will support ring policy. > Ring policy - delete oldest message(s) when queue capacity is reached > Queue capacity can be defined by maximum count of message and maximum size of > messages (including header). -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7647) [Java Broker] fix handling of broker type in configuration
[
https://issues.apache.org/jira/browse/QPID-7647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15893973#comment-15893973
]
Keith Wall commented on QPID-7647:
--
I don't think this change is right. I think you conflate two concepts:
category (record.getType()) with the discriminator
(brokerAttributes.put("type"). I think the problem is with the discriminator -
not the category. So..
* I think the equalIgnoreCase on line 317 is redundant.
* I think that the discriminator at the Broker level is redundant. In the
phase 3.0 detects it - it should remove it.
> [Java Broker] fix handling of broker type in configuration
> --
>
> Key: QPID-7647
> URL: https://issues.apache.org/jira/browse/QPID-7647
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: qpid-java-6.0, qpid-java-6.1, qpid-java-6.0.6,
> qpid-java-6.1.1, qpid-java-7.0
>Reporter: Lorenz Quack
>Priority: Minor
> Fix For: qpid-java-7.0, qpid-java-6.1.2, qpid-java-6.0.7
>
>
> In the default configuration the broker does store its own type explicitly.
> In this case there is not problem.
> If an explicit "type" is set in the config there might be one of a number of
> issues. The root of the problem is that the default type pre v6 was "broker"
> but in QPID-6911 this was changed to "Broker" for trunk (6.1.x at the time)
> and backported to 6.0. There was no upgrader added.
> If the "type" is set to "broker" in the 0.32 config and an upgrade to 6.0 is
> attempted it will fail with the following error:
> {noformat}
> 13:33:26.203 [main] ERROR org.apache.qpid.server.Broker - Exception during
> startup
> org.apache.qpid.server.configuration.IllegalConfigurationException: Provided
> type is broker but calculated type is Broker
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.(AbstractConfiguredObject.java:264)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.(AbstractConfiguredObject.java:205)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.(AbstractConfiguredObject.java:197)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at
> org.apache.qpid.server.model.adapter.BrokerAdapter.(BrokerAdapter.java:138)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at
> org.apache.qpid.server.model.adapter.BrokerAdapterFactory.createInstance(BrokerAdapterFactory.java:39)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at
> org.apache.qpid.server.model.adapter.BrokerAdapterFactory.createInstance(BrokerAdapterFactory.java:28)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at
> org.apache.qpid.server.model.AbstractConfiguredObjectTypeFactory$GenericUnresolvedConfiguredObject.resolve(AbstractConfiguredObjectTypeFactory.java:145)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at
> org.apache.qpid.server.model.AbstractConfiguredObjectTypeFactory$GenericUnresolvedConfiguredObject.resolve(AbstractConfiguredObjectTypeFactory.java:125)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at
> org.apache.qpid.server.store.GenericRecoverer.resolveObjects(GenericRecoverer.java:186)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at
> org.apache.qpid.server.store.GenericRecoverer.performRecover(GenericRecoverer.java:91)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at
> org.apache.qpid.server.store.GenericRecoverer.access$000(GenericRecoverer.java:41)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at
> org.apache.qpid.server.store.GenericRecoverer$1.execute(GenericRecoverer.java:59)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at
> org.apache.qpid.server.store.GenericRecoverer$1.execute(GenericRecoverer.java:55)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:270)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl.submitWrappedTask(TaskExecutorImpl.java:154)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl.run(TaskExecutorImpl.java:182)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at
> org.apache.qpid.server.store.GenericRecoverer.recover(GenericRecoverer.java:54)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at
> org.apache.qpid.server.store.BrokerStoreUpgraderAndRecoverer.perform(BrokerStoreUpgraderAndRecoverer.java:791)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at
> org.apache.qpid.server.model.AbstractSystemConfig.activate(AbstractSystemConfig.java:231)
> ~[qpid-broker-core-6.0.2.jar:6.0.2]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ~[na:1.8.0_111]
> at
> sun.reflect.NativeMethodAc
[jira] [Commented] (QPID-7631) [Java Broker, WMC] In BDBHA 2-node group you should be able to configure priority
[ https://issues.apache.org/jira/browse/QPID-7631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15893942#comment-15893942 ] Keith Wall commented on QPID-7631: -- Changes look good, okay for porting. > [Java Broker, WMC] In BDBHA 2-node group you should be able to configure > priority > - > > Key: QPID-7631 > URL: https://issues.apache.org/jira/browse/QPID-7631 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Lorenz Quack >Assignee: Alex Rudyy > Fix For: qpid-java-7.0, qpid-java-6.1.2 > > > Currently, we disable the edit field for priority when there are only two > nodes in the HA group. I don't see a reason to do this. > Note that priority is different from "designated primary"/"allow to run solo". > This is a UI issue only -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-7631) [Java Broker, WMC] In BDBHA 2-node group you should be able to configure priority
[ https://issues.apache.org/jira/browse/QPID-7631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-7631: - Priority: Minor (was: Major) > [Java Broker, WMC] In BDBHA 2-node group you should be able to configure > priority > - > > Key: QPID-7631 > URL: https://issues.apache.org/jira/browse/QPID-7631 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Reporter: Lorenz Quack >Assignee: Alex Rudyy >Priority: Minor > Fix For: qpid-java-7.0, qpid-java-6.1.2 > > > Currently, we disable the edit field for priority when there are only two > nodes in the HA group. I don't see a reason to do this. > Note that priority is different from "designated primary"/"allow to run solo". > This is a UI issue only -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
