[jira] [Created] (QPID-6821) Python tools scripts should specify correct python version in shebang
Chris Richardson created QPID-6821: -- Summary: Python tools scripts should specify correct python version in shebang Key: QPID-6821 URL: https://issues.apache.org/jira/browse/QPID-6821 Project: Qpid Issue Type: Bug Components: Python Tools Affects Versions: 0.32 Environment: Linux, python 2.7 and python 3.4 Reporter: Chris Richardson Fix For: qpid-tools-next In systems with both python2 and python3 installed, with python3 as the default, qpid-tools scripts (qpid-stat, qpid-config etc) fail due to being executed with the unsupported python3 VM. If the scripts require python2, should they not specify this in their shebangs, eg: #!/bin/env python2 rather than #!/bin/env python ? -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-6821) Python tools scripts should specify correct python version in shebang
[ https://issues.apache.org/jira/browse/QPID-6821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Richardson updated QPID-6821: --- Description: In systems with both python2 and python3 installed, with python3 as the default, qpid-tools scripts (qpid-stat, qpid-config etc) fail due to being executed with the unsupported python3 VM. If the scripts require python2, should they not specify this in their shebangs, eg: #!/bin/env python2.7 rather than #!/bin/env python ? was: In systems with both python2 and python3 installed, with python3 as the default, qpid-tools scripts (qpid-stat, qpid-config etc) fail due to being executed with the unsupported python3 VM. If the scripts require python2, should they not specify this in their shebangs, eg: #!/bin/env python2 rather than #!/bin/env python ? > Python tools scripts should specify correct python version in shebang > - > > Key: QPID-6821 > URL: https://issues.apache.org/jira/browse/QPID-6821 > Project: Qpid > Issue Type: Bug > Components: Python Tools >Affects Versions: 0.32 > Environment: Linux, python 2.7 and python 3.4 >Reporter: Chris Richardson > Fix For: qpid-tools-next > > > In systems with both python2 and python3 installed, with python3 as the > default, qpid-tools scripts (qpid-stat, qpid-config etc) fail due to being > executed with the unsupported python3 VM. If the scripts require python2, > should they not specify this in their shebangs, eg: > #!/bin/env python2.7 > rather than > #!/bin/env python > ? -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-6820) [Java Broker] State change listeners on non-acquired messages do not get removed when consumers are closed
[ https://issues.apache.org/jira/browse/QPID-6820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-6820: - Component/s: Java Broker > [Java Broker] State change listeners on non-acquired messages do not get > removed when consumers are closed > -- > > Key: QPID-6820 > URL: https://issues.apache.org/jira/browse/QPID-6820 > Project: Qpid > Issue Type: Bug > Components: Java Broker >Affects Versions: 0.32 >Reporter: Rob Godfrey >Assignee: Keith Wall > Attachments: QPID-6820.patch > > > See: > http://qpid.2158936.n2.nabble.com/Unconsumed-messages-can-still-prevent-GC-of-consumed-messages-td7633133.html -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-6822) Failure on: qpid-config add queue --durable "queue-id"
[
https://issues.apache.org/jira/browse/QPID-6822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Lacko updated QPID-6822:
--
Summary: Failure on: qpid-config add queue --durable "queue-id" (was:
Failure when: qpid-config add queue --durable "queue-id")
> Failure on: qpid-config add queue --durable "queue-id"
> --
>
> Key: QPID-6822
> URL: https://issues.apache.org/jira/browse/QPID-6822
> Project: Qpid
> Issue Type: Bug
>Affects Versions: 0.32
> Environment: RedHat 7.1
>Reporter: Peter Lacko
>
> Attempt to create durable queue fails with:
> {noformat}
> $ qpid-config add queue --durable "queue"
> Failed: Exception: Exception from Agent: {u'error_code': 7, u'error_text':
> 'Queue queue: create() failed: jexception 0x010c
> EmptyFilePool::createSymLink() threw JERR__SYMLINK: Symbolic link
> operation failed (file=/var/lib/qpidd/.qpidd/qls/p001/efp/2048k/in_use
> /85570c5b-b2ca-4883-bf86-8df746ac6ee4.jrnl symlink=/var/lib/qpidd/.qpidd
> /qls/jrnl2/queue/85570c5b-b2ca-4883-bf86-8df746ac6ee4.jrnl errno=13
> (Permission denied)) (/builddir/build/BUILD/qpid-cpp-0.34/src/qpid/linearstore
> /MessageStoreImpl.cpp:425)'}
> {noformat}
> Problem occures after doing {{yum update}}. All qpid packages version listed
> here below, before and after update:
> {noformat}
> $ diff qpid-before-update.txt qpid-after-update.txt
> 1,10c1,10
> < python-gofer-qpid.noarch 2.6.6-1.git.48.3141846.el7
> < python-qpid.x86_64 0.32-3.el7 @epel
> < python-qpid-common.x86_64 0.32-3.el7 @epel
> < python-qpid-qmf.x86_64 0.28-29.el7 @epel
> < qpid-cpp-client.x86_64 0.32-3.el7 @epel
> < qpid-cpp-server.x86_64 0.32-3.el7 @epel
> < qpid-cpp-server-store.x86_64
> < qpid-proton-c.x86_64 0.9-3.el7 @epel
> < qpid-qmf.x86_640.28-29.el7 @epel
> < qpid-tools.x86_64 0.32-3.el7 @epel
> ---
> > python-gofer-qpid.noarch 2.6.6-2.el7 @pulp-2.7-beta
> > python-qpid.noarch 0.32-9.el7 @epel
> > python-qpid-common.noarch 0.32-9.el7 @epel
> > python-qpid-qmf.x86_64 0.32-1.el7 @epel
> > qpid-cpp-client.x86_64 0.34-4.el7 @epel
> > qpid-cpp-server.x86_64 0.34-4.el7 @epel
> > qpid-cpp-server-linearstore.x86_64
> > qpid-proton-c.x86_64 0.10-2.el7 @epel
> > qpid-qmf.x86_640.32-1.el7 @epel
> > qpid-tools.noarch 0.32-9.el7 @epel
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-6822) Failure when: qpid-config add queue --durable "queue-id"
Peter Lacko created QPID-6822:
-
Summary: Failure when: qpid-config add queue --durable "queue-id"
Key: QPID-6822
URL: https://issues.apache.org/jira/browse/QPID-6822
Project: Qpid
Issue Type: Bug
Affects Versions: 0.32
Environment: RedHat 7.1
Reporter: Peter Lacko
Attempt to create durable queue fails with:
{noformat}
$ qpid-config add queue --durable "queue"
Failed: Exception: Exception from Agent: {u'error_code': 7, u'error_text':
'Queue queue: create() failed: jexception 0x010c
EmptyFilePool::createSymLink() threw JERR__SYMLINK: Symbolic link
operation failed (file=/var/lib/qpidd/.qpidd/qls/p001/efp/2048k/in_use
/85570c5b-b2ca-4883-bf86-8df746ac6ee4.jrnl symlink=/var/lib/qpidd/.qpidd
/qls/jrnl2/queue/85570c5b-b2ca-4883-bf86-8df746ac6ee4.jrnl errno=13
(Permission denied)) (/builddir/build/BUILD/qpid-cpp-0.34/src/qpid/linearstore
/MessageStoreImpl.cpp:425)'}
{noformat}
Problem occures after doing {{yum update}}. All qpid packages version listed
here below, before and after update:
{noformat}
$ diff qpid-before-update.txt qpid-after-update.txt
1,10c1,10
< python-gofer-qpid.noarch 2.6.6-1.git.48.3141846.el7
< python-qpid.x86_64 0.32-3.el7 @epel
< python-qpid-common.x86_64 0.32-3.el7 @epel
< python-qpid-qmf.x86_64 0.28-29.el7 @epel
< qpid-cpp-client.x86_64 0.32-3.el7 @epel
< qpid-cpp-server.x86_64 0.32-3.el7 @epel
< qpid-cpp-server-store.x86_64
< qpid-proton-c.x86_64 0.9-3.el7 @epel
< qpid-qmf.x86_640.28-29.el7 @epel
< qpid-tools.x86_64 0.32-3.el7 @epel
---
> python-gofer-qpid.noarch 2.6.6-2.el7 @pulp-2.7-beta
> python-qpid.noarch 0.32-9.el7 @epel
> python-qpid-common.noarch 0.32-9.el7 @epel
> python-qpid-qmf.x86_64 0.32-1.el7 @epel
> qpid-cpp-client.x86_64 0.34-4.el7 @epel
> qpid-cpp-server.x86_64 0.34-4.el7 @epel
> qpid-cpp-server-linearstore.x86_64
> qpid-proton-c.x86_64 0.10-2.el7 @epel
> qpid-qmf.x86_640.32-1.el7 @epel
> qpid-tools.noarch 0.32-9.el7 @epel
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (QPID-6822) Failure on: qpid-config add queue --durable "queue-id"
[
https://issues.apache.org/jira/browse/QPID-6822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Lacko updated QPID-6822:
--
Description:
Attempt to create durable queue fails with:
{noformat}
$ qpid-config add queue --durable "queue"
Failed: Exception: Exception from Agent: {u'error_code': 7, u'error_text':
'Queue queue: create() failed: jexception 0x010c
EmptyFilePool::createSymLink() threw JERR__SYMLINK: Symbolic link
operation failed (file=/var/lib/qpidd/.qpidd/qls/p001/efp/2048k/in_use
/85570c5b-b2ca-4883-bf86-8df746ac6ee4.jrnl symlink=/var/lib/qpidd/.qpidd
/qls/jrnl2/queue/85570c5b-b2ca-4883-bf86-8df746ac6ee4.jrnl errno=13
(Permission denied)) (/builddir/build/BUILD/qpid-cpp-0.34/src/qpid/linearstore
/MessageStoreImpl.cpp:425)'}
{noformat}
Problem occures after doing {{yum update}}. All qpid packages versions listed
below, before and after performing update:
{noformat}
$ diff qpid-before-update.txt qpid-after-update.txt
1,10c1,10
< python-gofer-qpid.noarch 2.6.6-1.git.48.3141846.el7
< python-qpid.x86_64 0.32-3.el7 @epel
< python-qpid-common.x86_64 0.32-3.el7 @epel
< python-qpid-qmf.x86_64 0.28-29.el7 @epel
< qpid-cpp-client.x86_64 0.32-3.el7 @epel
< qpid-cpp-server.x86_64 0.32-3.el7 @epel
< qpid-cpp-server-store.x86_64
< qpid-proton-c.x86_64 0.9-3.el7 @epel
< qpid-qmf.x86_640.28-29.el7 @epel
< qpid-tools.x86_64 0.32-3.el7 @epel
---
> python-gofer-qpid.noarch 2.6.6-2.el7 @pulp-2.7-beta
> python-qpid.noarch 0.32-9.el7 @epel
> python-qpid-common.noarch 0.32-9.el7 @epel
> python-qpid-qmf.x86_64 0.32-1.el7 @epel
> qpid-cpp-client.x86_64 0.34-4.el7 @epel
> qpid-cpp-server.x86_64 0.34-4.el7 @epel
> qpid-cpp-server-linearstore.x86_64
> qpid-proton-c.x86_64 0.10-2.el7 @epel
> qpid-qmf.x86_640.32-1.el7 @epel
> qpid-tools.noarch 0.32-9.el7 @epel
{noformat}
was:
Attempt to create durable queue fails with:
{noformat}
$ qpid-config add queue --durable "queue"
Failed: Exception: Exception from Agent: {u'error_code': 7, u'error_text':
'Queue queue: create() failed: jexception 0x010c
EmptyFilePool::createSymLink() threw JERR__SYMLINK: Symbolic link
operation failed (file=/var/lib/qpidd/.qpidd/qls/p001/efp/2048k/in_use
/85570c5b-b2ca-4883-bf86-8df746ac6ee4.jrnl symlink=/var/lib/qpidd/.qpidd
/qls/jrnl2/queue/85570c5b-b2ca-4883-bf86-8df746ac6ee4.jrnl errno=13
(Permission denied)) (/builddir/build/BUILD/qpid-cpp-0.34/src/qpid/linearstore
/MessageStoreImpl.cpp:425)'}
{noformat}
Problem occures after doing {{yum update}}. All qpid packages version listed
here below, before and after update:
{noformat}
$ diff qpid-before-update.txt qpid-after-update.txt
1,10c1,10
< python-gofer-qpid.noarch 2.6.6-1.git.48.3141846.el7
< python-qpid.x86_64 0.32-3.el7 @epel
< python-qpid-common.x86_64 0.32-3.el7 @epel
< python-qpid-qmf.x86_64 0.28-29.el7 @epel
< qpid-cpp-client.x86_64 0.32-3.el7 @epel
< qpid-cpp-server.x86_64 0.32-3.el7 @epel
< qpid-cpp-server-store.x86_64
< qpid-proton-c.x86_64 0.9-3.el7 @epel
< qpid-qmf.x86_640.28-29.el7 @epel
< qpid-tools.x86_64 0.32-3.el7 @epel
---
> python-gofer-qpid.noarch 2.6.6-2.el7 @pulp-2.7-beta
> python-qpid.noarch 0.32-9.el7 @epel
> python-qpid-common.noarch 0.32-9.el7 @epel
> python-qpid-qmf.x86_64 0.32-1.el7 @epel
> qpid-cpp-client.x86_64 0.34-4.el7 @epel
> qpid-cpp-server.x86_64 0.34-4.el7 @epel
> qpid-cpp-server-linearstore.x86_64
> qpid-proton-c.x86_64 0.10-2.el7 @epel
> qpid-qmf.x86_640.32-1.el7 @epel
> qpid-tools.noarch 0.32-9.el7 @epel
{noformat}
> Failure on: qpid-config add queue --durable "queue-id"
> --
>
> Key: QPID-6822
> URL: https://issues.apache.org/jira/browse/QPID-6822
> Project: Qpid
> Issue Type: Bug
>Affects Versions: 0.32
> Environment: RedHat 7.1
>Reporter: Peter Lacko
>
> Attempt to create durable queue fails with:
> {noformat}
> $ qpid-config add queue --durable "queue"
> Failed: Exception: Exception from Agent: {u'error_code': 7, u'error_text':
> 'Queue queue: create() failed: jexception 0x010c
> EmptyFilePool::createSymLink() threw JERR__SYMLINK: Symbolic link
> operation failed (file=/var/lib/qpidd/.qpidd/qls/p001/efp/2048k/in_use
> /85570c5b-b2ca-4883-bf86-8df746ac6ee4.jrnl symlink=/var/lib/qpidd/.qpidd
> /qls/jrnl2/queue/85570c5b-b2ca-4883-bf86-8df746ac6ee4.jrnl errno=13
> (Permission denied)) (/builddir/build/BUILD/qpid-cpp-0.34/src/qpid/linearstore
> /Messag
[jira] [Updated] (QPID-6822) Failure on: qpid-config add queue --durable "queue-id"
[
https://issues.apache.org/jira/browse/QPID-6822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Lacko updated QPID-6822:
--
Description:
Attempt to create durable queue fails with:
{noformat}
$ qpid-config add queue --durable "queue"
Failed: Exception: Exception from Agent: {u'error_code': 7, u'error_text':
'Queue queue: create() failed: jexception 0x010c
EmptyFilePool::createSymLink() threw JERR__SYMLINK: Symbolic link
operation failed (file=/var/lib/qpidd/.qpidd/qls/p001/efp/2048k/in_use
/85570c5b-b2ca-4883-bf86-8df746ac6ee4.jrnl symlink=/var/lib/qpidd/.qpidd
/qls/jrnl2/queue/85570c5b-b2ca-4883-bf86-8df746ac6ee4.jrnl errno=13
(Permission denied)) (/builddir/build/BUILD/qpid-cpp-0.34/src/qpid/linearstore
/MessageStoreImpl.cpp:425)'}
{noformat}
Queue is created succesfully without {{--durable}} parameter.
Problem occures after doing {{yum update}}. All qpid packages versions listed
below, before and after performing update:
{noformat}
$ diff qpid-before-update.txt qpid-after-update.txt
1,10c1,10
< python-gofer-qpid.noarch 2.6.6-1.git.48.3141846.el7
< python-qpid.x86_64 0.32-3.el7 @epel
< python-qpid-common.x86_64 0.32-3.el7 @epel
< python-qpid-qmf.x86_64 0.28-29.el7 @epel
< qpid-cpp-client.x86_64 0.32-3.el7 @epel
< qpid-cpp-server.x86_64 0.32-3.el7 @epel
< qpid-cpp-server-store.x86_64
< qpid-proton-c.x86_64 0.9-3.el7 @epel
< qpid-qmf.x86_640.28-29.el7 @epel
< qpid-tools.x86_64 0.32-3.el7 @epel
---
> python-gofer-qpid.noarch 2.6.6-2.el7 @pulp-2.7-beta
> python-qpid.noarch 0.32-9.el7 @epel
> python-qpid-common.noarch 0.32-9.el7 @epel
> python-qpid-qmf.x86_64 0.32-1.el7 @epel
> qpid-cpp-client.x86_64 0.34-4.el7 @epel
> qpid-cpp-server.x86_64 0.34-4.el7 @epel
> qpid-cpp-server-linearstore.x86_64
> qpid-proton-c.x86_64 0.10-2.el7 @epel
> qpid-qmf.x86_640.32-1.el7 @epel
> qpid-tools.noarch 0.32-9.el7 @epel
{noformat}
was:
Attempt to create durable queue fails with:
{noformat}
$ qpid-config add queue --durable "queue"
Failed: Exception: Exception from Agent: {u'error_code': 7, u'error_text':
'Queue queue: create() failed: jexception 0x010c
EmptyFilePool::createSymLink() threw JERR__SYMLINK: Symbolic link
operation failed (file=/var/lib/qpidd/.qpidd/qls/p001/efp/2048k/in_use
/85570c5b-b2ca-4883-bf86-8df746ac6ee4.jrnl symlink=/var/lib/qpidd/.qpidd
/qls/jrnl2/queue/85570c5b-b2ca-4883-bf86-8df746ac6ee4.jrnl errno=13
(Permission denied)) (/builddir/build/BUILD/qpid-cpp-0.34/src/qpid/linearstore
/MessageStoreImpl.cpp:425)'}
{noformat}
Problem occures after doing {{yum update}}. All qpid packages versions listed
below, before and after performing update:
{noformat}
$ diff qpid-before-update.txt qpid-after-update.txt
1,10c1,10
< python-gofer-qpid.noarch 2.6.6-1.git.48.3141846.el7
< python-qpid.x86_64 0.32-3.el7 @epel
< python-qpid-common.x86_64 0.32-3.el7 @epel
< python-qpid-qmf.x86_64 0.28-29.el7 @epel
< qpid-cpp-client.x86_64 0.32-3.el7 @epel
< qpid-cpp-server.x86_64 0.32-3.el7 @epel
< qpid-cpp-server-store.x86_64
< qpid-proton-c.x86_64 0.9-3.el7 @epel
< qpid-qmf.x86_640.28-29.el7 @epel
< qpid-tools.x86_64 0.32-3.el7 @epel
---
> python-gofer-qpid.noarch 2.6.6-2.el7 @pulp-2.7-beta
> python-qpid.noarch 0.32-9.el7 @epel
> python-qpid-common.noarch 0.32-9.el7 @epel
> python-qpid-qmf.x86_64 0.32-1.el7 @epel
> qpid-cpp-client.x86_64 0.34-4.el7 @epel
> qpid-cpp-server.x86_64 0.34-4.el7 @epel
> qpid-cpp-server-linearstore.x86_64
> qpid-proton-c.x86_64 0.10-2.el7 @epel
> qpid-qmf.x86_640.32-1.el7 @epel
> qpid-tools.noarch 0.32-9.el7 @epel
{noformat}
> Failure on: qpid-config add queue --durable "queue-id"
> --
>
> Key: QPID-6822
> URL: https://issues.apache.org/jira/browse/QPID-6822
> Project: Qpid
> Issue Type: Bug
>Affects Versions: 0.32
> Environment: RedHat 7.1
>Reporter: Peter Lacko
>
> Attempt to create durable queue fails with:
> {noformat}
> $ qpid-config add queue --durable "queue"
> Failed: Exception: Exception from Agent: {u'error_code': 7, u'error_text':
> 'Queue queue: create() failed: jexception 0x010c
> EmptyFilePool::createSymLink() threw JERR__SYMLINK: Symbolic link
> operation failed (file=/var/lib/qpidd/.qpidd/qls/p001/efp/2048k/in_use
> /85570c5b-b2ca-4883-bf86-8df746ac6ee4.jrnl symlink=/var/lib/qpidd/.qpidd
> /qls/jrnl2/queue/85570c5b-b2ca-4883-bf86-8df746ac6ee4.jrnl errno=13
> (Permission denied))
[jira] [Commented] (QPID-6822) Failure on: qpid-config add queue --durable "queue-id"
[
https://issues.apache.org/jira/browse/QPID-6822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985205#comment-14985205
]
Pavel Moravec commented on QPID-6822:
-
There was some linearstore directory structure change between 0.32 and 0.34 (
kpvdr / Kim van Der Riet would know).
Just a guess - have you restarted the broker after the upgrade? And did you
follow the upgrade steps (I can find it now only in Red Hat manuals
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_MRG/3/html-single/Messaging_Installation_and_Configuration_Guide/index.html#Manually_Upgrade_Linearstore
).
> Failure on: qpid-config add queue --durable "queue-id"
> --
>
> Key: QPID-6822
> URL: https://issues.apache.org/jira/browse/QPID-6822
> Project: Qpid
> Issue Type: Bug
>Affects Versions: 0.32
> Environment: RedHat 7.1
>Reporter: Peter Lacko
>
> Attempt to create durable queue fails with:
> {noformat}
> $ qpid-config add queue --durable "queue"
> Failed: Exception: Exception from Agent: {u'error_code': 7, u'error_text':
> 'Queue queue: create() failed: jexception 0x010c
> EmptyFilePool::createSymLink() threw JERR__SYMLINK: Symbolic link
> operation failed (file=/var/lib/qpidd/.qpidd/qls/p001/efp/2048k/in_use
> /85570c5b-b2ca-4883-bf86-8df746ac6ee4.jrnl symlink=/var/lib/qpidd/.qpidd
> /qls/jrnl2/queue/85570c5b-b2ca-4883-bf86-8df746ac6ee4.jrnl errno=13
> (Permission denied)) (/builddir/build/BUILD/qpid-cpp-0.34/src/qpid/linearstore
> /MessageStoreImpl.cpp:425)'}
> {noformat}
> Queue is created succesfully without {{--durable}} parameter.
> Problem occures after doing {{yum update}}. All qpid packages versions listed
> below, before and after performing update:
> {noformat}
> $ diff qpid-before-update.txt qpid-after-update.txt
> 1,10c1,10
> < python-gofer-qpid.noarch 2.6.6-1.git.48.3141846.el7
> < python-qpid.x86_64 0.32-3.el7 @epel
> < python-qpid-common.x86_64 0.32-3.el7 @epel
> < python-qpid-qmf.x86_64 0.28-29.el7 @epel
> < qpid-cpp-client.x86_64 0.32-3.el7 @epel
> < qpid-cpp-server.x86_64 0.32-3.el7 @epel
> < qpid-cpp-server-store.x86_64
> < qpid-proton-c.x86_64 0.9-3.el7 @epel
> < qpid-qmf.x86_640.28-29.el7 @epel
> < qpid-tools.x86_64 0.32-3.el7 @epel
> ---
> > python-gofer-qpid.noarch 2.6.6-2.el7 @pulp-2.7-beta
> > python-qpid.noarch 0.32-9.el7 @epel
> > python-qpid-common.noarch 0.32-9.el7 @epel
> > python-qpid-qmf.x86_64 0.32-1.el7 @epel
> > qpid-cpp-client.x86_64 0.34-4.el7 @epel
> > qpid-cpp-server.x86_64 0.34-4.el7 @epel
> > qpid-cpp-server-linearstore.x86_64
> > qpid-proton-c.x86_64 0.10-2.el7 @epel
> > qpid-qmf.x86_640.32-1.el7 @epel
> > qpid-tools.noarch 0.32-9.el7 @epel
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Comment Edited] (QPID-6822) Failure on: qpid-config add queue --durable "queue-id"
[
https://issues.apache.org/jira/browse/QPID-6822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985205#comment-14985205
]
Pavel Moravec edited comment on QPID-6822 at 11/2/15 1:26 PM:
--
There was some linearstore directory structure change between 0.32 and 0.34 (
kpvdr / Kim van Der Riet would know).
Just a guess - have you restarted the broker after the upgrade? And did you
follow the upgrade steps (I can find it now only in Red Hat manuals
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_MRG/3/html-single/Messaging_Installation_and_Configuration_Guide/index.html#Manually_Upgrade_Linearstore
)?
was (Author: pmoravec):
There was some linearstore directory structure change between 0.32 and 0.34 (
kpvdr / Kim van Der Riet would know).
Just a guess - have you restarted the broker after the upgrade? And did you
follow the upgrade steps (I can find it now only in Red Hat manuals
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_MRG/3/html-single/Messaging_Installation_and_Configuration_Guide/index.html#Manually_Upgrade_Linearstore
).
> Failure on: qpid-config add queue --durable "queue-id"
> --
>
> Key: QPID-6822
> URL: https://issues.apache.org/jira/browse/QPID-6822
> Project: Qpid
> Issue Type: Bug
>Affects Versions: 0.32
> Environment: RedHat 7.1
>Reporter: Peter Lacko
>
> Attempt to create durable queue fails with:
> {noformat}
> $ qpid-config add queue --durable "queue"
> Failed: Exception: Exception from Agent: {u'error_code': 7, u'error_text':
> 'Queue queue: create() failed: jexception 0x010c
> EmptyFilePool::createSymLink() threw JERR__SYMLINK: Symbolic link
> operation failed (file=/var/lib/qpidd/.qpidd/qls/p001/efp/2048k/in_use
> /85570c5b-b2ca-4883-bf86-8df746ac6ee4.jrnl symlink=/var/lib/qpidd/.qpidd
> /qls/jrnl2/queue/85570c5b-b2ca-4883-bf86-8df746ac6ee4.jrnl errno=13
> (Permission denied)) (/builddir/build/BUILD/qpid-cpp-0.34/src/qpid/linearstore
> /MessageStoreImpl.cpp:425)'}
> {noformat}
> Queue is created succesfully without {{--durable}} parameter.
> Problem occures after doing {{yum update}}. All qpid packages versions listed
> below, before and after performing update:
> {noformat}
> $ diff qpid-before-update.txt qpid-after-update.txt
> 1,10c1,10
> < python-gofer-qpid.noarch 2.6.6-1.git.48.3141846.el7
> < python-qpid.x86_64 0.32-3.el7 @epel
> < python-qpid-common.x86_64 0.32-3.el7 @epel
> < python-qpid-qmf.x86_64 0.28-29.el7 @epel
> < qpid-cpp-client.x86_64 0.32-3.el7 @epel
> < qpid-cpp-server.x86_64 0.32-3.el7 @epel
> < qpid-cpp-server-store.x86_64
> < qpid-proton-c.x86_64 0.9-3.el7 @epel
> < qpid-qmf.x86_640.28-29.el7 @epel
> < qpid-tools.x86_64 0.32-3.el7 @epel
> ---
> > python-gofer-qpid.noarch 2.6.6-2.el7 @pulp-2.7-beta
> > python-qpid.noarch 0.32-9.el7 @epel
> > python-qpid-common.noarch 0.32-9.el7 @epel
> > python-qpid-qmf.x86_64 0.32-1.el7 @epel
> > qpid-cpp-client.x86_64 0.34-4.el7 @epel
> > qpid-cpp-server.x86_64 0.34-4.el7 @epel
> > qpid-cpp-server-linearstore.x86_64
> > qpid-proton-c.x86_64 0.10-2.el7 @epel
> > qpid-qmf.x86_640.32-1.el7 @epel
> > qpid-tools.noarch 0.32-9.el7 @epel
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-6822) Failure on: qpid-config add queue --durable "queue-id"
[
https://issues.apache.org/jira/browse/QPID-6822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985220#comment-14985220
]
Brian Bouterse commented on QPID-6822:
--
Can someone link to the the upstream docs? I believe Peter was testing the
upstream based qpid packages published in epel7, not MRG.
> Failure on: qpid-config add queue --durable "queue-id"
> --
>
> Key: QPID-6822
> URL: https://issues.apache.org/jira/browse/QPID-6822
> Project: Qpid
> Issue Type: Bug
>Affects Versions: 0.32
> Environment: RedHat 7.1
>Reporter: Peter Lacko
>
> Attempt to create durable queue fails with:
> {noformat}
> $ qpid-config add queue --durable "queue"
> Failed: Exception: Exception from Agent: {u'error_code': 7, u'error_text':
> 'Queue queue: create() failed: jexception 0x010c
> EmptyFilePool::createSymLink() threw JERR__SYMLINK: Symbolic link
> operation failed (file=/var/lib/qpidd/.qpidd/qls/p001/efp/2048k/in_use
> /85570c5b-b2ca-4883-bf86-8df746ac6ee4.jrnl symlink=/var/lib/qpidd/.qpidd
> /qls/jrnl2/queue/85570c5b-b2ca-4883-bf86-8df746ac6ee4.jrnl errno=13
> (Permission denied)) (/builddir/build/BUILD/qpid-cpp-0.34/src/qpid/linearstore
> /MessageStoreImpl.cpp:425)'}
> {noformat}
> Queue is created succesfully without {{--durable}} parameter.
> Problem occures after doing {{yum update}}. All qpid packages versions listed
> below, before and after performing update:
> {noformat}
> $ diff qpid-before-update.txt qpid-after-update.txt
> 1,10c1,10
> < python-gofer-qpid.noarch 2.6.6-1.git.48.3141846.el7
> < python-qpid.x86_64 0.32-3.el7 @epel
> < python-qpid-common.x86_64 0.32-3.el7 @epel
> < python-qpid-qmf.x86_64 0.28-29.el7 @epel
> < qpid-cpp-client.x86_64 0.32-3.el7 @epel
> < qpid-cpp-server.x86_64 0.32-3.el7 @epel
> < qpid-cpp-server-store.x86_64
> < qpid-proton-c.x86_64 0.9-3.el7 @epel
> < qpid-qmf.x86_640.28-29.el7 @epel
> < qpid-tools.x86_64 0.32-3.el7 @epel
> ---
> > python-gofer-qpid.noarch 2.6.6-2.el7 @pulp-2.7-beta
> > python-qpid.noarch 0.32-9.el7 @epel
> > python-qpid-common.noarch 0.32-9.el7 @epel
> > python-qpid-qmf.x86_64 0.32-1.el7 @epel
> > qpid-cpp-client.x86_64 0.34-4.el7 @epel
> > qpid-cpp-server.x86_64 0.34-4.el7 @epel
> > qpid-cpp-server-linearstore.x86_64
> > qpid-proton-c.x86_64 0.10-2.el7 @epel
> > qpid-qmf.x86_640.32-1.el7 @epel
> > qpid-tools.noarch 0.32-9.el7 @epel
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-6823) [Java Broker] On failures to open ACL rules file the cause exception is not chained to the thrown IllegalConfigurationException making it is difficult to understand what e
Alex Rudyy created QPID-6823:
Summary: [Java Broker] On failures to open ACL rules file the
cause exception is not chained to the thrown IllegalConfigurationException
making it is difficult to understand what exactly caused the failure to open
ACL file
Key: QPID-6823
URL: https://issues.apache.org/jira/browse/QPID-6823
Project: Qpid
Issue Type: Bug
Components: Java Broker
Reporter: Alex Rudyy
On failures to open ACL rules file the cause exception is not chained to the
thrown IllegalConfigurationException making it is difficult to understand what
exactly caused the failure to open ACL file.
Here is an example of stack trace:
{noformat}
org.apache.qpid.server.configuration.IllegalConfigurationException: Cannot
convert /tmp/ExchangeRestACLTest9052195928623123673testDeleteExchangeAllowed to
a readable resource
at
org.apache.qpid.server.security.access.plugins.DefaultAccessControl.getReaderFromURLString(DefaultAccessControl.java:126)
~[qpid-broker-plugins-access-control-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT]
at
org.apache.qpid.server.security.access.plugins.DefaultAccessControl.open(DefaultAccessControl.java:80)
~[qpid-broker-plugins-access-control-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT]
at
org.apache.qpid.server.security.access.plugins.ACLFileAccessControlProviderImpl.activate(ACLFileAccessControlProviderImpl.java:172)
~[qpid-broker-plugins-access-control-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT]
at sun.reflect.GeneratedMethodAccessor81.invoke(Unknown Source) ~[na:na]
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
~[na:1.8.0_45]
at java.lang.reflect.Method.invoke(Method.java:497) ~[na:1.8.0_45]
at
org.apache.qpid.server.model.AbstractConfiguredObject.attainState(AbstractConfiguredObject.java:1239)
[qpid-broker-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT]
at
org.apache.qpid.server.model.AbstractConfiguredObject.attainState(AbstractConfiguredObject.java:1218)
[qpid-broker-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT]
at
org.apache.qpid.server.model.AbstractConfiguredObject$8.onSuccess(AbstractConfiguredObject.java:867)
[qpid-broker-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT]
at
org.apache.qpid.server.model.AbstractConfiguredObject$8.onSuccess(AbstractConfiguredObject.java:861)
[qpid-broker-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT]
at com.google.common.util.concurrent.Futures$6.run(Futures.java:1319)
[guava-18.0.jar:na]
at
com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:457)
[guava-18.0.jar:na]
at
com.google.common.util.concurrent.ExecutionList.executeListener(ExecutionList.java:156)
[guava-18.0.jar:na]
at
com.google.common.util.concurrent.ExecutionList.add(ExecutionList.java:101)
[guava-18.0.jar:na]
at
com.google.common.util.concurrent.AbstractFuture.addListener(AbstractFuture.java:170)
[guava-18.0.jar:na]
at
com.google.common.util.concurrent.Futures.addCallback(Futures.java:1322)
[guava-18.0.jar:na]
at
com.google.common.util.concurrent.Futures.addCallback(Futures.java:1258)
[guava-18.0.jar:na]
at
org.apache.qpid.server.model.AbstractConfiguredObject.doAttainState(AbstractConfiguredObject.java:860)
[qpid-broker-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT]
at
org.apache.qpid.server.model.AbstractConfiguredObject.access$300(AbstractConfiguredObject.java:78)
[qpid-broker-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT]
at
org.apache.qpid.server.model.AbstractConfiguredObject$7.performAction(AbstractConfiguredObject.java:851)
[qpid-broker-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT]
at
org.apache.qpid.server.model.AbstractConfiguredObject$7.performAction(AbstractConfiguredObject.java:843)
[qpid-broker-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT]
at
org.apache.qpid.server.model.AbstractConfiguredObject.applyToChildren(AbstractConfiguredObject.java:1053)
[qpid-broker-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT]
at
org.apache.qpid.server.model.AbstractConfiguredObject.doAttainState(AbstractConfiguredObject.java:842)
[qpid-broker-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT]
at
org.apache.qpid.server.model.AbstractConfiguredObject.access$300(AbstractConfiguredObject.java:78)
[qpid-broker-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT]
at
org.apache.qpid.server.model.AbstractConfiguredObject$1.execute(AbstractConfiguredObject.java:472)
[qpid-broker-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT]
at
org.apache.qpid.server.model.AbstractConfiguredObject$1.execute(AbstractConfiguredObject.java:459)
[qpid-broker-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT]
at
org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:520)
[qpid-broker-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT]
at
org.apache.qpid.
[jira] [Updated] (QPID-6823) [Java Broker] On failures to open ACL rules file the cause exception is not chained to the thrown IllegalConfigurationException making it is difficult to understand what e
[
https://issues.apache.org/jira/browse/QPID-6823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Rudyy updated QPID-6823:
-
Affects Version/s: qpid-java-6.0
> [Java Broker] On failures to open ACL rules file the cause exception is not
> chained to the thrown IllegalConfigurationException making it is difficult to
> understand what exactly caused the failure to open ACL file
> -
>
> Key: QPID-6823
> URL: https://issues.apache.org/jira/browse/QPID-6823
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: qpid-java-6.0
>Reporter: Alex Rudyy
>
> On failures to open ACL rules file the cause exception is not chained to the
> thrown IllegalConfigurationException making it is difficult to understand
> what exactly caused the failure to open ACL file.
> Here is an example of stack trace:
> {noformat}
> org.apache.qpid.server.configuration.IllegalConfigurationException: Cannot
> convert /tmp/ExchangeRestACLTest9052195928623123673testDeleteExchangeAllowed
> to a readable resource
> at
> org.apache.qpid.server.security.access.plugins.DefaultAccessControl.getReaderFromURLString(DefaultAccessControl.java:126)
> ~[qpid-broker-plugins-access-control-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT]
> at
> org.apache.qpid.server.security.access.plugins.DefaultAccessControl.open(DefaultAccessControl.java:80)
> ~[qpid-broker-plugins-access-control-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT]
> at
> org.apache.qpid.server.security.access.plugins.ACLFileAccessControlProviderImpl.activate(ACLFileAccessControlProviderImpl.java:172)
> ~[qpid-broker-plugins-access-control-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT]
> at sun.reflect.GeneratedMethodAccessor81.invoke(Unknown Source) ~[na:na]
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[na:1.8.0_45]
> at java.lang.reflect.Method.invoke(Method.java:497) ~[na:1.8.0_45]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.attainState(AbstractConfiguredObject.java:1239)
> [qpid-broker-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.attainState(AbstractConfiguredObject.java:1218)
> [qpid-broker-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$8.onSuccess(AbstractConfiguredObject.java:867)
> [qpid-broker-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$8.onSuccess(AbstractConfiguredObject.java:861)
> [qpid-broker-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT]
> at com.google.common.util.concurrent.Futures$6.run(Futures.java:1319)
> [guava-18.0.jar:na]
> at
> com.google.common.util.concurrent.MoreExecutors$DirectExecutor.execute(MoreExecutors.java:457)
> [guava-18.0.jar:na]
> at
> com.google.common.util.concurrent.ExecutionList.executeListener(ExecutionList.java:156)
> [guava-18.0.jar:na]
> at
> com.google.common.util.concurrent.ExecutionList.add(ExecutionList.java:101)
> [guava-18.0.jar:na]
> at
> com.google.common.util.concurrent.AbstractFuture.addListener(AbstractFuture.java:170)
> [guava-18.0.jar:na]
> at
> com.google.common.util.concurrent.Futures.addCallback(Futures.java:1322)
> [guava-18.0.jar:na]
> at
> com.google.common.util.concurrent.Futures.addCallback(Futures.java:1258)
> [guava-18.0.jar:na]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.doAttainState(AbstractConfiguredObject.java:860)
> [qpid-broker-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.access$300(AbstractConfiguredObject.java:78)
> [qpid-broker-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$7.performAction(AbstractConfiguredObject.java:851)
> [qpid-broker-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject$7.performAction(AbstractConfiguredObject.java:843)
> [qpid-broker-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.applyToChildren(AbstractConfiguredObject.java:1053)
> [qpid-broker-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.doAttainState(AbstractConfiguredObject.java:842)
> [qpid-broker-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT]
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.access$300(AbstractConfiguredObject.java:78)
> [qpid-broker-core-6.0.0-SNAPSHOT.jar:6.0.0-SNAPSHOT]
> at
> org
[jira] [Commented] (QPID-6794) [Java Broker] Reduce latency in IO by processing work immediately after select()
[
https://issues.apache.org/jira/browse/QPID-6794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14985455#comment-14985455
]
Keith Wall commented on QPID-6794:
--
NCS processConnection uses condition _running.get() == _poolSize to determine
if it should keep a connection running or schedule it again on the pool. In
light of the multiple selector changes (r1710010), this has been broken. The
{{_running}} accounting needs to be change to take into account the selection
task, and with, QPID-6819, the accept task too.
> [Java Broker] Reduce latency in IO by processing work immediately after
> select()
>
>
> Key: QPID-6794
> URL: https://issues.apache.org/jira/browse/QPID-6794
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
>Reporter: Rob Godfrey
>Assignee: Rob Godfrey
> Fix For: qpid-java-6.0
>
>
> Rather than having a dedicated SelectorThread which passes work to a thread
> pool, instead perform the select in the thread pool, continue immediately
> processing the results in the same thread, and dispatch the select task to be
> executed again in the thread pool.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (QPID-6813) Consumer tasks may run on the Broker thread leading to deadlock
[
https://issues.apache.org/jira/browse/QPID-6813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Godfrey resolved QPID-6813.
---
Resolution: Fixed
> Consumer tasks may run on the Broker thread leading to deadlock
> ---
>
> Key: QPID-6813
> URL: https://issues.apache.org/jira/browse/QPID-6813
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
>Affects Versions: qpid-java-6.0
>Reporter: Keith Wall
>Assignee: Rob Godfrey
>Priority: Blocker
> Fix For: qpid-java-6.0
>
>
> Since QPID-6597, a consumer's tasks may run on the Broker's task executor
> rather than the Virtualhost's as was intended. This may lead to deadlock.
> The problem occurs because ACO discovers its task executor from its parents.
> If a ACO has multiple parents, the chosen parent is non-deterministic. This
> didn't used to matter because Consumers parents Queue and Session both shared
> a Virtualhost ancestor, so the Virtualhost task executor was always selected.
> However, QPID-6597, re-homed Connection (the parent of Session) to be a
> child of Broker. Since that point the executor used has been
> non-deterministic, Consumers may end up with a Broker or Virtualhost task
> executor.
> Testing with very large numbers of connections exposed a deadlock between the
> Broker and Virtualhost configuration thread.
> {code:java}
> protected AbstractConfiguredObject(final Map ConfiguredObject>, ConfiguredObject> parents,
>Map attributes)
> {
> this(parents, attributes,
> parents.values().iterator().next().getChildExecutor());
> }
> {code}
> (The VH thread running an addConsumer blocks opening a Consumer using the
> Broker thread, meanwhile the Broker thread *running a consumer close* tries
> to use the VH executor to remove a queue. Deadlock.)
> {noformat}
> "VirtualHostNode-default-Config" prio=10 tid=0x7f48701a nid=0xd714
> waiting on condition [0x7f48ac728000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0xe7ecd4a8> (a
> com.google.common.util.concurrent.AbstractFuture$Sync)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
> at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
> at
> com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:285)
> at
> com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:116)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.doSync(AbstractConfiguredObject.java:1937)
> at
> org.apache.qpid.server.model.AbstractConfiguredObject.open(AbstractConfiguredObject.java:452)
> at
> org.apache.qpid.server.queue.QueueConsumerImpl.(QueueConsumerImpl.java:136)
> at
> org.apache.qpid.server.queue.AbstractQueue.addConsumerInternal(AbstractQueue.java:864)
> at
> org.apache.qpid.server.queue.AbstractQueue.access$200(AbstractQueue.java:119)
> at
> org.apache.qpid.server.queue.AbstractQueue$6.execute(AbstractQueue.java:695)
> at
> org.apache.qpid.server.queue.AbstractQueue$6.execute(AbstractQueue.java:691)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:270)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper$1.run(TaskExecutorImpl.java:342)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:356)
> at
> org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper.call(TaskExecutorImpl.java:335)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
>
>Locked ownable synchronizers:
> - <0xe5953fb0> (a
> java.util.concurrent.ThreadPoolExecutor$Worker)
>
> "Broker-Config" prio=10 tid=0x7f49c8f67000 nid=0xd70d waiting on
> condition [0x7f48ac95e000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for <0xea9a2940> (a
> com.goo
[jira] [Closed] (DISPATCH-189) Dispatch python tools fail to detect rejected connection
[
https://issues.apache.org/jira/browse/DISPATCH-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chuck Rolke closed DISPATCH-189.
Resolution: Not A Problem
The faulty code is in qpid-proton and not in qpid-dispatch.
> Dispatch python tools fail to detect rejected connection
>
>
> Key: DISPATCH-189
> URL: https://issues.apache.org/jira/browse/DISPATCH-189
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Management Agent
>Affects Versions: 0.5
> Environment: qdstat tool connecting to broker/router that rejects the
> connection
>Reporter: Chuck Rolke
>Assignee: Chuck Rolke
>
> Case 1: connection rejected by qdrouterd:
> -
> Testing out policy-based connection rejection shows qdstat tool
> mis-interpreting the connection failure. The order of events on the wire is:
> {noformat}
> Client sends
> Open
> Router sends
> Open
> Close(Arguments: Error: {
> Condition: 'amqp:resource-limit-exceeded',
> Description: 'connection disallowed by local policy',
> Info: ''}
> {noformat}
> Then the qdstat tool fails with message:
> {noformat}
> AttributeError: 'ConnectionClosed' object has no attribute 'url'
> {noformat}
> The expectation is for the tool to show the condition/description from the
> Close performative.
> Case 2: connection rejected by Apache Qpidd C++ broker
> -
> When Qpidd rejects a connection it summarily closes the connection with a TCP
> FIN and does not exchange AMQP Open. In this case the qdstat tool displays a
> reasonable message about connection failure to $management.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
