[jira] [Commented] (QPID-8286) [Broker-J] Add operation into priority queue to change message priority
[
https://issues.apache.org/jira/browse/QPID-8286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16802327#comment-16802327
]
Alex Rudyy commented on QPID-8286:
--
[~rgodfrey], I finally found some time to implement my ideas about changing
message priority. In PR22 I added 2 operations into priority queue :
{{reenqueueMessageForPriorityChange}} and
{{reenqueueMessagesForPriorityChange}}. In both operations the messages(s) are
replaced with new ones having given priority. I am planning to merge the
changes into 7.1.x and spin 7.1.2 release.
> [Broker-J] Add operation into priority queue to change message priority
> ---
>
> Key: QPID-8286
> URL: https://issues.apache.org/jira/browse/QPID-8286
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
>Reporter: Alex Rudyy
>Priority: Major
> Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.2
>
>
> The functionality to change message priority is required for some use case
> scenarios involving priority queues. At the moment, in order to change the
> priority, the messages need to be consumed (for example, using selector
> 'JMSMessageID=ID:XYZ') and re-published with a different priority. I
> management operation can be introduced on the priority queue which can simply
> dequeue the message and re-enqueue it with a provided priority.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8286) [Broker-J] Add operation into priority queue to change message priority
[ https://issues.apache.org/jira/browse/QPID-8286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16802326#comment-16802326 ] ASF GitHub Bot commented on QPID-8286: -- alex-rufous commented on pull request #22: QPID-8286: [Broker-J] Add operations into priority queue to change message priority URL: https://github.com/apache/qpid-broker-j/pull/22 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > [Broker-J] Add operation into priority queue to change message priority > --- > > Key: QPID-8286 > URL: https://issues.apache.org/jira/browse/QPID-8286 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Alex Rudyy >Priority: Major > Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.2 > > > The functionality to change message priority is required for some use case > scenarios involving priority queues. At the moment, in order to change the > priority, the messages need to be consumed (for example, using selector > 'JMSMessageID=ID:XYZ') and re-published with a different priority. I > management operation can be introduced on the priority queue which can simply > dequeue the message and re-enqueue it with a provided priority. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] [qpid-broker-j] alex-rufous opened a new pull request #22: QPID-8286: [Broker-J] Add operations into priority queue to change message priority
alex-rufous opened a new pull request #22: QPID-8286: [Broker-J] Add operations into priority queue to change message priority URL: https://github.com/apache/qpid-broker-j/pull/22 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2020) _io.py error path syntax error in python3
[ https://issues.apache.org/jira/browse/PROTON-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16802229#comment-16802229 ] Chuck Rolke commented on PROTON-2020: - [~astitcher] A qpid-dispatch self test has been running fine (for me) with Python 2 for about a year. [https://github.com/apache/qpid-dispatch/blob/master/tests/authservice.py.in] Whatever signal is being emitted by select it is "not iterable" and referring to it with 'e[0]' generates a new exception that hides the original exception. With that repaired by this issue the fundamental issue is exposed at PROTON-2022 > _io.py error path syntax error in python3 > - > > Key: PROTON-2020 > URL: https://issues.apache.org/jira/browse/PROTON-2020 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: proton-c-0.27.0 > Environment: python 3 > Fedora 29 > Proton master > qpid-dispatch master @88e25 > self test system_tests_authz_service_plugin >Reporter: Chuck Rolke >Priority: Major > Fix For: proton-c-0.28.0 > > > * > 39: File "/opt/local/lib64/proton/bindings/python/proton/_io.py", line 138, > in select > * > 39: if e[0] != errno.EINTR: > * > 39: TypeError: 'OSError' object is not subscriptable > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1862) idle timeout not working on linux
[ https://issues.apache.org/jira/browse/PROTON-1862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16802176#comment-16802176 ] Andrew Stitcher commented on PROTON-1862: - It's not valid to sleep in the middle of a handler. This will cause the event loop not to handle any more events until the sleep finishes. Whilst sleeping no timeout can happen as the execution thread is stuck in the sleep. > idle timeout not working on linux > -- > > Key: PROTON-1862 > URL: https://issues.apache.org/jira/browse/PROTON-1862 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Affects Versions: proton-c-0.22.0 >Reporter: Jeremy >Priority: Critical > Labels: reproducer > Attachments: proton_1862_tests.txt, test_case.cpp > > > We faced an issue with the idle timeout on linux. On windows, it seems to > work. > In our proton feature test suite, we test the idle timeout feature by doing a > sleep in the method on_session_open. > This should trigger a connection timeout. It works on windows, and it used to > work with proton v0.16.0 on windows and linux. > Removing the sleep from the on_session_open and putting it in > on_connection_open, yields the same result. > See attached file to reproduce. > Machines: > * Windows machine > ** OS: Windows 7 > ** Compiler: MSVC 2013 Version 12 Update 5 > * Linux machine > ** OS: Red Hat Enterprise Linux Server release 6.4 (Santiago) > ** Compiler: g++491 (GCC) 4.9.2 20150212 (Red Hat 4.9.2-6) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1993) Tests fail on Windows for release builds (without debug symbols)
[
https://issues.apache.org/jira/browse/PROTON-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16802168#comment-16802168
]
Andrew Stitcher commented on PROTON-1993:
-
[~roromo] Is it possible to get the test log file - this summary here doesn't
contain enough to be useful to diagnose the problem. The test log should be in
the {{Testing/Temporary/LastTest.log}} file (relative to the build directory).
Alternatively add {{-V}} to the {{ctest}} command line.
> Tests fail on Windows for release builds (without debug symbols)
>
>
> Key: PROTON-1993
> URL: https://issues.apache.org/jira/browse/PROTON-1993
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Affects Versions: proton-c-0.26.0, proton-c-0.27.0
> Environment: Windows 7 Pro 64 bit, as well as Windows 10 Pro 64 bit,
> up to date MSVC 2017 compiler, CMake build system.
>Reporter: Bogdan Bozi
>Priority: Major
>
> Environment: project created using CMake, building only the C and C++
> binding, for 64 bit architecture using the MS VS2017 compiler.
>
> Tests are ok for the following build configurations:
> * Debug
> * RelWithDebInfo
> Tests fail for the following build configurations:
> * Release
> * MinSizeRel
>
> Issue is present with the current head, as well as the released
> proton-c-0.26.0. Older versions were not tested but might fail too.
> Linux builds were not tested.
>
> Test results for builds with debug symbols:
> {noformat}
> 1>-- Build started: Project: RUN_TESTS, Configuration: Debug x64 --
> 1>Test project C:/Work/projects/qpid-proton/build
> 1> Start 1: c-example-tests
> 1> 1/22 Test #1: c-example-tests .. Passed 1.68 sec
> 1> Start 2: c-core-test
> 1> 2/22 Test #2: c-core-test .. Passed 0.11 sec
> 1> Start 3: c-extra-test
> 1> 3/22 Test #3: c-extra-test . Passed 0.07 sec
> 1> Start 4: c-proactor-test
> 1> 4/22 Test #4: c-proactor-test .. Passed 8.29 sec
> 1> Start 5: c-fdlimit-tests
> 1> 5/22 Test #5: c-fdlimit-tests .. Passed 0.10 sec
> 1> Start 6: fuzz-connection-driver
> 1> 6/22 Test #6: fuzz-connection-driver ... Passed 0.96 sec
> 1> Start 7: fuzz-message-decode
> 1> 7/22 Test #7: fuzz-message-decode .. Passed 0.28 sec
> 1> Start 8: fuzz-url
> 1> 8/22 Test #8: fuzz-url . Passed 0.10 sec
> 1> Start 9: fuzz-sniff-header
> 1> 9/22 Test #9: fuzz-sniff-header Passed 0.06 sec
> 1> Start 10: cpp-codec_test
> 1>10/22 Test #10: cpp-codec_test ... Passed 0.07 sec
> 1> Start 11: cpp-connection_driver_test
> 1>11/22 Test #11: cpp-connection_driver_test ... Passed 0.09 sec
> 1> Start 12: cpp-interop_test
> 1>12/22 Test #12: cpp-interop_test . Passed 0.06 sec
> 1> Start 13: cpp-message_test
> 1>13/22 Test #13: cpp-message_test . Passed 0.07 sec
> 1> Start 14: cpp-map_test
> 1>14/22 Test #14: cpp-map_test . Passed 0.07 sec
> 1> Start 15: cpp-scalar_test
> 1>15/22 Test #15: cpp-scalar_test .. Passed 0.07 sec
> 1> Start 16: cpp-value_test
> 1>16/22 Test #16: cpp-value_test ... Passed 0.08 sec
> 1> Start 17: cpp-container_test
> 1>17/22 Test #17: cpp-container_test ... Passed 0.60 sec
> 1> Start 18: cpp-reconnect_test
> 1>18/22 Test #18: cpp-reconnect_test ... Passed 8.58 sec
> 1> Start 19: cpp-link_test
> 1>19/22 Test #19: cpp-link_test Passed 1.10 sec
> 1> Start 20: cpp-url-test
> 1>20/22 Test #20: cpp-url-test . Passed 0.07 sec
> 1> Start 21: cpp-example-container
> 1>21/22 Test #21: cpp-example-container Passed 0.75 sec
> 1> Start 22: cpp-example-container-ssl
> 1>22/22 Test #22: cpp-example-container-ssl Passed 0.46 sec
> 1>
> 1>100% tests passed, 0 tests failed out of 22
> 1>
> 1>Total Test time (real) = 23.76 sec
> == Build: 1 succeeded, 0 failed, 1 up-to-date, 0 skipped ==
> {noformat}
> Test results for builds without debug symbols:
> {noformat}
> 1>-- Build started: Project: RUN_TESTS, Configuration: Release x64 --
> 1>Test project C:/Work/projects/qpid-proton/build
> 1> Start 1: c-example-tests
> 1> 1/22 Test #1: c-example-tests ..***Failed 0.95 sec
> 1> Start 2: c-core-test
> 1> 2/22 Test #2: c-core-test .. Passed 0.07 sec
> 1> Start 3: c-extra-test
> 1> 3/22 Test #3: c-extra-test . Passed 0.06 sec
> 1> Start 4: c-proactor-test
> 1> 4/22 Test #4: c-proactor-test ..***Failed 0.06 sec
> 1> Start 5: c-fdlimit-tests
> 1> 5/22 Test #5: c-fdlimit-tests .. Passed 0.10 sec
> 1> Start 6: fuzz-connection-driver
> 1> 6/22 Test #6:
[jira] [Commented] (PROTON-2020) _io.py error path syntax error in python3
[ https://issues.apache.org/jira/browse/PROTON-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16802159#comment-16802159 ] Andrew Stitcher commented on PROTON-2020: - [~chug] Could you say a little more about the circumstances here - select is not supposed to emit SIGINTR any more under python 3. It should just silently retry. Is this a different signal being emitted? > _io.py error path syntax error in python3 > - > > Key: PROTON-2020 > URL: https://issues.apache.org/jira/browse/PROTON-2020 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: proton-c-0.27.0 > Environment: python 3 > Fedora 29 > Proton master > qpid-dispatch master @88e25 > self test system_tests_authz_service_plugin >Reporter: Chuck Rolke >Priority: Major > Fix For: proton-c-0.28.0 > > > * > 39: File "/opt/local/lib64/proton/bindings/python/proton/_io.py", line 138, > in select > * > 39: if e[0] != errno.EINTR: > * > 39: TypeError: 'OSError' object is not subscriptable > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2006) Qpid Proton cannot connect to Azure Service Bus 'amqp:connection:framing-error'
[
https://issues.apache.org/jira/browse/PROTON-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Stitcher resolved PROTON-2006.
-
Resolution: Fixed
Fix Version/s: proton-c-0.28.0
> Qpid Proton cannot connect to Azure Service Bus
> 'amqp:connection:framing-error'
> ---
>
> Key: PROTON-2006
> URL: https://issues.apache.org/jira/browse/PROTON-2006
> Project: Qpid Proton
> Issue Type: Bug
> Components: cpp-binding, examples
>Affects Versions: proton-c-0.28.0
>Reporter: Oskar Christensson
>Priority: Major
> Fix For: proton-c-0.28.0
>
>
>
> {code:java}
> amqp:connection:framing-error: SASL header mismatch: Insufficient data to
> determine protocol [''] (connection aborted){code}
> We're trying to get a C++ connection to Azure Service Bus using AMQP with
> QPID proton, and trying out the examples under qpid-proton/cpp/examples it
> fails.
> Steps to reproduce:
> # Clone qpid-proton
> # Follow installation and make README
> # Create new Service Bus Namespace in azure
> # Create new Service Bus Queue in Azure with Sessions enabled
> # Create a policy with all permissions
> # `./service_bus -n .servicebus.windows.net -p -k
> -e
> Expected results:
> It should work according to the docs in the cpp/examples/service_bus.cpp docs
> Actual results:
> {code:java}
> amqp:connection:framing-error: SASL header mismatch: Insufficient data to
> determine protocol [''] (connection aborted){code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2006) Qpid Proton cannot connect to Azure Service Bus 'amqp:connection:framing-error'
[
https://issues.apache.org/jira/browse/PROTON-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16802153#comment-16802153
]
ASF subversion and git services commented on PROTON-2006:
-
Commit eab1fef19b4e58a8b79408f29e10fe36b07a3b83 in qpid-proton's branch
refs/heads/master from Andrew Stitcher
[ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=eab1fef ]
PROTON-2006: [C++] Fixed up service bus example to work
- Connection options needed fixing
-- You can't put user/password in the connection url anymore
-- Need to turn SSL on and ensure SASL mech is PLAIN
- Misuse of scheduling stopped the application exiting when finished
> Qpid Proton cannot connect to Azure Service Bus
> 'amqp:connection:framing-error'
> ---
>
> Key: PROTON-2006
> URL: https://issues.apache.org/jira/browse/PROTON-2006
> Project: Qpid Proton
> Issue Type: Bug
> Components: cpp-binding, examples
>Affects Versions: proton-c-0.28.0
>Reporter: Oskar Christensson
>Priority: Major
>
>
> {code:java}
> amqp:connection:framing-error: SASL header mismatch: Insufficient data to
> determine protocol [''] (connection aborted){code}
> We're trying to get a C++ connection to Azure Service Bus using AMQP with
> QPID proton, and trying out the examples under qpid-proton/cpp/examples it
> fails.
> Steps to reproduce:
> # Clone qpid-proton
> # Follow installation and make README
> # Create new Service Bus Namespace in azure
> # Create new Service Bus Queue in Azure with Sessions enabled
> # Create a policy with all permissions
> # `./service_bus -n .servicebus.windows.net -p -k
> -e
> Expected results:
> It should work according to the docs in the cpp/examples/service_bus.cpp docs
> Actual results:
> {code:java}
> amqp:connection:framing-error: SASL header mismatch: Insufficient data to
> determine protocol [''] (connection aborted){code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-1306) [tools] Scraper does not account for changes to log format
[ https://issues.apache.org/jira/browse/DISPATCH-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chuck Rolke resolved DISPATCH-1306. --- Resolution: Fixed Fixed at Commit 004fa473 > [tools] Scraper does not account for changes to log format > -- > > Key: DISPATCH-1306 > URL: https://issues.apache.org/jira/browse/DISPATCH-1306 > Project: Qpid Dispatch > Issue Type: Bug > Components: Tools >Affects Versions: 0.6.0 >Reporter: Chuck Rolke >Assignee: Chuck Rolke >Priority: Major > > DISPATCH-1289 changed the connection number in the log from, say, [5] to > [C5]. Scraper expects an integer and gets tripped up. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1306) [tools] Scraper does not account for changes to log format
[ https://issues.apache.org/jira/browse/DISPATCH-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16802097#comment-16802097 ] ASF subversion and git services commented on DISPATCH-1306: --- Commit 004fa473843d7f4366d8b62cab88aa0d5117b5c8 in qpid-dispatch's branch refs/heads/master from Charles E. Rolke [ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=004fa47 ] DISPATCH-1306: accomodate new logfile connection number format > [tools] Scraper does not account for changes to log format > -- > > Key: DISPATCH-1306 > URL: https://issues.apache.org/jira/browse/DISPATCH-1306 > Project: Qpid Dispatch > Issue Type: Bug > Components: Tools >Affects Versions: 0.6.0 >Reporter: Chuck Rolke >Assignee: Chuck Rolke >Priority: Major > > DISPATCH-1289 changed the connection number in the log from, say, [5] to > [C5]. Scraper expects an integer and gets tripped up. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-1306) [tools] Scraper does not account for changes to log format
Chuck Rolke created DISPATCH-1306: - Summary: [tools] Scraper does not account for changes to log format Key: DISPATCH-1306 URL: https://issues.apache.org/jira/browse/DISPATCH-1306 Project: Qpid Dispatch Issue Type: Bug Components: Tools Affects Versions: 0.6.0 Reporter: Chuck Rolke Assignee: Chuck Rolke DISPATCH-1289 changed the connection number in the log from, say, [5] to [C5]. Scraper expects an integer and gets tripped up. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Reopened] (DISPATCH-1265) Delivery_abort test causes inter-router session error
[ https://issues.apache.org/jira/browse/DISPATCH-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chuck Rolke reopened DISPATCH-1265: --- Dispatch can't fix this as the underlying problem is in Proton. This issue is reopened so we can track the progress again when proton gets fixed. > Delivery_abort test causes inter-router session error > - > > Key: DISPATCH-1265 > URL: https://issues.apache.org/jira/browse/DISPATCH-1265 > Project: Qpid Dispatch > Issue Type: Bug > Components: Router Node >Affects Versions: 1.5.0 > Environment: Fedora 29, Python 3. > branch DISPATCH-1264#a5aab9 > ctest -VV -R system_tests_delivery_abort >Reporter: Chuck Rolke >Assignee: Ganesh Murthy >Priority: Critical > Fix For: 1.6.0 > > Attachments: DISPATCH-1265_ctest-log.txt, > DISPATCH-1265_scraped-logs-timeout.html > > > Inter-router connection closes with: > error :"amqp:session:invalid-field" "sequencing error, expected delivery-id > 24, got 23" -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-1304) Authz self test fails with python 3
[ https://issues.apache.org/jira/browse/DISPATCH-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chuck Rolke resolved DISPATCH-1304. --- Resolution: Fixed Fix Version/s: 1.7.0 fixed at Commit ae97a4d > Authz self test fails with python 3 > --- > > Key: DISPATCH-1304 > URL: https://issues.apache.org/jira/browse/DISPATCH-1304 > Project: Qpid Dispatch > Issue Type: Bug > Components: Tests >Affects Versions: 1.5.0 >Reporter: Chuck Rolke >Assignee: Chuck Rolke >Priority: Major > Fix For: 1.7.0 > > Attachments: authz.txt > > > This issue is with program authservice.py written to support > system_tests_authz_service_plugin self test. The issue is not with the router > mission code. See attached selftest log file. > A workaround is simply ignore the error that bubbles up from Proton. The onus > is on Proton to figure out what is really wrong and how a caller like > AuthService can avoid the error. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (QPID-8289) [Broker-J] Broker startup can fail due to ConcurrentModificationException
Alex Rudyy created QPID-8289:
Summary: [Broker-J] Broker startup can fail due to
ConcurrentModificationException
Key: QPID-8289
URL: https://issues.apache.org/jira/browse/QPID-8289
Project: Qpid
Issue Type: Bug
Components: Broker-J
Affects Versions: qpid-java-broker-7.1.1
Reporter: Alex Rudyy
The startup can fail with the following exception
{noformat}
ERROR [VirtualHostNode-default-Config] (o.a.q.s.m.AbstractConfiguredObject) -
Failed to open object with name 'default'. Object will be put into ERROR state.
org.apache.qpid.server.configuration.IllegalConfigurationException: Cannot open
virtual host message store:null
at
org.apache.qpid.server.virtualhost.AbstractVirtualHost.validateMessageStoreCreation(AbstractVirtualHost.java:563)
at
org.apache.qpid.server.virtualhost.AbstractVirtualHost.onValidate(AbstractVirtualHost.java:398)
at
org.apache.qpid.server.model.AbstractConfiguredObject.doValidation(AbstractConfiguredObject.java:1205)
at
org.apache.qpid.server.model.AbstractConfiguredObject$1.execute(AbstractConfiguredObject.java:589)
at
org.apache.qpid.server.model.AbstractConfiguredObject$1.execute(AbstractConfiguredObject.java:578)
at
org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:639)
at
org.apache.qpid.server.model.AbstractConfiguredObject$2.execute(AbstractConfiguredObject.java:632)
at
org.apache.qpid.server.configuration.updater.TaskExecutorImpl$TaskLoggingWrapper.execute(TaskExecutorImpl.java:248)
at
org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper$1.run(TaskExecutorImpl.java:320)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:360)
at
org.apache.qpid.server.configuration.updater.TaskExecutorImpl$CallableWrapper.call(TaskExecutorImpl.java:313)
at
com.google.common.util.concurrent.TrustedListenableFutureTask$TrustedFutureInterruptibleTask.runInterruptibly(TrustedListenableFutureTask.java:125)
at
com.google.common.util.concurrent.InterruptibleTask.run(InterruptibleTask.java:57)
at
com.google.common.util.concurrent.TrustedListenableFutureTask.run(TrustedListenableFutureTask.java:78)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at
org.apache.qpid.server.bytebuffer.QpidByteBufferFactory.lambda$null$0(QpidByteBufferFactory.java:464)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.util.ConcurrentModificationException: null
at java.util.Hashtable$Enumerator.next(Hashtable.java:1383)
at java.util.HashMap.putMapEntries(HashMap.java:512)
at java.util.HashMap.putAll(HashMap.java:785)
at
org.apache.qpid.server.model.AbstractConfiguredObject.getContextKeys(AbstractConfiguredObject.java:3508)
at
org.apache.qpid.server.store.berkeleydb.BDBUtils.getContextSettingsWithNameMatchingRegExpPattern(BDBUtils.java:130)
at
org.apache.qpid.server.store.berkeleydb.BDBUtils.getEnvironmentConfigurationParameters(BDBUtils.java:119)
at
org.apache.qpid.server.store.berkeleydb.StandardEnvironmentFacadeFactory$1.getParameters(StandardEnvironmentFacadeFactory.java:73)
at
org.apache.qpid.server.store.berkeleydb.StandardEnvironmentFacade.(StandardEnvironmentFacade.java:116)
at
org.apache.qpid.server.store.berkeleydb.StandardEnvironmentFacadeFactory.createEnvironmentFacade(StandardEnvironmentFacadeFactory.java:89)
at
org.apache.qpid.server.store.berkeleydb.BDBMessageStore.doOpen(BDBMessageStore.java:57)
at
org.apache.qpid.server.store.berkeleydb.AbstractBDBMessageStore.openMessageStore(AbstractBDBMessageStore.java:131)
at
org.apache.qpid.server.virtualhost.AbstractVirtualHost.validateMessageStoreCreation(AbstractVirtualHost.java:559)
... 18 common frames omitted
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1304) Authz self test fails with python 3
[ https://issues.apache.org/jira/browse/DISPATCH-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16801942#comment-16801942 ] ASF subversion and git services commented on DISPATCH-1304: --- Commit ae97a4d608dfda080608c310dd607b4186c06047 in qpid-dispatch's branch refs/heads/master from Charles E. Rolke [ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=ae97a4d ] DISPATCH-1304: authservice.py program fails at shutdown in python 3 Container().run() throws an OSError. Catch and ignore the error. > Authz self test fails with python 3 > --- > > Key: DISPATCH-1304 > URL: https://issues.apache.org/jira/browse/DISPATCH-1304 > Project: Qpid Dispatch > Issue Type: Bug > Components: Tests >Affects Versions: 1.5.0 >Reporter: Chuck Rolke >Assignee: Chuck Rolke >Priority: Major > Attachments: authz.txt > > > This issue is with program authservice.py written to support > system_tests_authz_service_plugin self test. The issue is not with the router > mission code. See attached selftest log file. > A workaround is simply ignore the error that bubbles up from Proton. The onus > is on Proton to figure out what is really wrong and how a caller like > AuthService can avoid the error. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-1305) Fix flake8 warnings in system_tests_policy
[
https://issues.apache.org/jira/browse/DISPATCH-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy resolved DISPATCH-1305.
-
Resolution: Fixed
> Fix flake8 warnings in system_tests_policy
> --
>
> Key: DISPATCH-1305
> URL: https://issues.apache.org/jira/browse/DISPATCH-1305
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.5.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.7.0
>
>
> {noformat}
> 56: ERROR: InvocationError for command
> '/foo/qpid-dispatch/build/tests/.tox/py27/bin/flake8 --count
> /foo/qpid-dispatch/python /foo/qpid-dispatch/console /foo/qpid-dispatch/docs
> /foo/qpid-dispatch/tests /foo/qpid-dispatch/tools --show-source
> --ignore=E111,E114,E121,E122,E123,E124,E126,E127,E128,E129,E131,E201,E202,E203,E211,E221,E222,E225,E226,E228,E231,E241,E251,E261,E266,E265,E271,E272,E301,E302,E303,E401,E402,E501,E502,E701,E702,E703,E704,E711,E712,E713,E714,E731,F401,F403,F405,F811,F841,H101,H102,H104,H201,H202,H234,H237,H238,H301,H306,H401,H403,H404,H405,W291,W292,W293,W391,W503'
> (exited with code 1)
> 56: py35 create: /foo/qpid-dispatch/build/tests/.tox/py35
> 56: py35 installdeps: hacking>=1.1.0
> 56: py35 installed:
> flake8==2.6.2,hacking==1.1.0,mccabe==0.5.3,pbr==5.1.3,pycodestyle==2.0.0,pyflakes==1.2.3,six==1.12.0
> 56: py35 run-test-pre: PYTHONHASHSEED='1741025927'
> 56: py35 runtests: commands[0] | flake8 --count /foo/qpid-dispatch/python
> /foo/qpid-dispatch/console /foo/qpid-dispatch/docs /foo/qpid-dispatch/tests
> /foo/qpid-dispatch/tools --show-source
> --ignore=E111,E114,E121,E122,E123,E124,E126,E127,E128,E129,E131,E201,E202,E203,E211,E221,E222,E225,E226,E228,E231,E241,E251,E261,E266,E265,E271,E272,E301,E302,E303,E401,E402,E501,E502,E701,E702,E703,E704,E711,E712,E713,E714,E731,F401,F403,F405,F811,F841,H101,H102,H104,H201,H202,H234,H237,H238,H301,H306,H401,H403,H404,H405,W291,W292,W293,W391,W503
> 56: /foo/qpid-dispatch/tests/system_tests_policy.py:1317:13: E125
> continuation line with same indent as next logical line
> 56: and self.link_error == False and self._error is None:
> 56: ^
> 56: /foo/qpid-dispatch/tests/system_tests_policy.py:1326:13: E125
> continuation line with same indent as next logical line
> 56: and self.link_error == False and self._error is None:
> 56: ^
> 56: /foo/qpid-dispatch/tests/system_tests_policy.py:1345:13: E125
> continuation line with same indent as next logical line
> 56: and self.link_error == False and self._error is None:
> 56: ^
> 56: 3
> 56: ERROR: InvocationError for command
> '/foo/qpid-dispatch/build/tests/.tox/py35/bin/flake8 --count
> /foo/qpid-dispatch/python /foo/qpid-dispatch/console /foo/qpid-dispatch/docs
> /foo/qpid-dispatch/tests /foo/qpid-dispatch/tools --show-source
> --ignore=E111,E114,E121,E122,E123,E124,E126,E127,E128,E129,E131,E201,E202,E203,E211,E221,E222,E225,E226,E228,E231,E241,E251,E261,E266,E265,E271,E272,E301,E302,E303,E401,E402,E501,E502,E701,E702,E703,E704,E711,E712,E713,E714,E731,F401,F403,F405,F811,F841,H101,H102,H104,H201,H202,H234,H237,H238,H301,H306,H401,H403,H404,H405,W291,W292,W293,W391,W503'
> (exited with code 1)
> 56: py36 create: /foo/qpid-dispatch/build/tests/.tox/py36
> 56: SKIPPED: InterpreterNotFound: python3.6
> 56: py37 create: /foo/qpid-dispatch/build/tests/.tox/py37
> 56: SKIPPED: InterpreterNotFound: python3.7
> 56: ___ summary
>
> 56: ERROR: py27: commands failed
> 56: ERROR: py35: commands failed
> 56: SKIPPED: py36: InterpreterNotFound: python3.6
> 56: SKIPPED: py37: InterpreterNotFound: python3.7
> 56/56 Test #56: python-checker ***Failed
> Error regular expression found in output. Regex=[commands failed] 49.73 sec
> 96% tests passed, 2 tests failed out of 56
> Total Test time (real) = 683.94 sec{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1305) Fix flake8 warnings in system_tests_policy
[
https://issues.apache.org/jira/browse/DISPATCH-1305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16801877#comment-16801877
]
ASF subversion and git services commented on DISPATCH-1305:
---
Commit 9e10ba9dbc7328b02bad101c8563e0c51508a815 in qpid-dispatch's branch
refs/heads/master from Ganesh Murthy
[ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=9e10ba9 ]
DISPATCH-1305 - Fixed flake8 indent error
> Fix flake8 warnings in system_tests_policy
> --
>
> Key: DISPATCH-1305
> URL: https://issues.apache.org/jira/browse/DISPATCH-1305
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.5.0
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.7.0
>
>
> {noformat}
> 56: ERROR: InvocationError for command
> '/foo/qpid-dispatch/build/tests/.tox/py27/bin/flake8 --count
> /foo/qpid-dispatch/python /foo/qpid-dispatch/console /foo/qpid-dispatch/docs
> /foo/qpid-dispatch/tests /foo/qpid-dispatch/tools --show-source
> --ignore=E111,E114,E121,E122,E123,E124,E126,E127,E128,E129,E131,E201,E202,E203,E211,E221,E222,E225,E226,E228,E231,E241,E251,E261,E266,E265,E271,E272,E301,E302,E303,E401,E402,E501,E502,E701,E702,E703,E704,E711,E712,E713,E714,E731,F401,F403,F405,F811,F841,H101,H102,H104,H201,H202,H234,H237,H238,H301,H306,H401,H403,H404,H405,W291,W292,W293,W391,W503'
> (exited with code 1)
> 56: py35 create: /foo/qpid-dispatch/build/tests/.tox/py35
> 56: py35 installdeps: hacking>=1.1.0
> 56: py35 installed:
> flake8==2.6.2,hacking==1.1.0,mccabe==0.5.3,pbr==5.1.3,pycodestyle==2.0.0,pyflakes==1.2.3,six==1.12.0
> 56: py35 run-test-pre: PYTHONHASHSEED='1741025927'
> 56: py35 runtests: commands[0] | flake8 --count /foo/qpid-dispatch/python
> /foo/qpid-dispatch/console /foo/qpid-dispatch/docs /foo/qpid-dispatch/tests
> /foo/qpid-dispatch/tools --show-source
> --ignore=E111,E114,E121,E122,E123,E124,E126,E127,E128,E129,E131,E201,E202,E203,E211,E221,E222,E225,E226,E228,E231,E241,E251,E261,E266,E265,E271,E272,E301,E302,E303,E401,E402,E501,E502,E701,E702,E703,E704,E711,E712,E713,E714,E731,F401,F403,F405,F811,F841,H101,H102,H104,H201,H202,H234,H237,H238,H301,H306,H401,H403,H404,H405,W291,W292,W293,W391,W503
> 56: /foo/qpid-dispatch/tests/system_tests_policy.py:1317:13: E125
> continuation line with same indent as next logical line
> 56: and self.link_error == False and self._error is None:
> 56: ^
> 56: /foo/qpid-dispatch/tests/system_tests_policy.py:1326:13: E125
> continuation line with same indent as next logical line
> 56: and self.link_error == False and self._error is None:
> 56: ^
> 56: /foo/qpid-dispatch/tests/system_tests_policy.py:1345:13: E125
> continuation line with same indent as next logical line
> 56: and self.link_error == False and self._error is None:
> 56: ^
> 56: 3
> 56: ERROR: InvocationError for command
> '/foo/qpid-dispatch/build/tests/.tox/py35/bin/flake8 --count
> /foo/qpid-dispatch/python /foo/qpid-dispatch/console /foo/qpid-dispatch/docs
> /foo/qpid-dispatch/tests /foo/qpid-dispatch/tools --show-source
> --ignore=E111,E114,E121,E122,E123,E124,E126,E127,E128,E129,E131,E201,E202,E203,E211,E221,E222,E225,E226,E228,E231,E241,E251,E261,E266,E265,E271,E272,E301,E302,E303,E401,E402,E501,E502,E701,E702,E703,E704,E711,E712,E713,E714,E731,F401,F403,F405,F811,F841,H101,H102,H104,H201,H202,H234,H237,H238,H301,H306,H401,H403,H404,H405,W291,W292,W293,W391,W503'
> (exited with code 1)
> 56: py36 create: /foo/qpid-dispatch/build/tests/.tox/py36
> 56: SKIPPED: InterpreterNotFound: python3.6
> 56: py37 create: /foo/qpid-dispatch/build/tests/.tox/py37
> 56: SKIPPED: InterpreterNotFound: python3.7
> 56: ___ summary
>
> 56: ERROR: py27: commands failed
> 56: ERROR: py35: commands failed
> 56: SKIPPED: py36: InterpreterNotFound: python3.6
> 56: SKIPPED: py37: InterpreterNotFound: python3.7
> 56/56 Test #56: python-checker ***Failed
> Error regular expression found in output. Regex=[commands failed] 49.73 sec
> 96% tests passed, 2 tests failed out of 56
> Total Test time (real) = 683.94 sec{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-1305) Fix flake8 warnings in system_tests_policy
Ganesh Murthy created DISPATCH-1305:
---
Summary: Fix flake8 warnings in system_tests_policy
Key: DISPATCH-1305
URL: https://issues.apache.org/jira/browse/DISPATCH-1305
Project: Qpid Dispatch
Issue Type: Bug
Components: Tests
Affects Versions: 1.5.0
Reporter: Ganesh Murthy
Assignee: Ganesh Murthy
Fix For: 1.7.0
{noformat}
56: ERROR: InvocationError for command
'/foo/qpid-dispatch/build/tests/.tox/py27/bin/flake8 --count
/foo/qpid-dispatch/python /foo/qpid-dispatch/console /foo/qpid-dispatch/docs
/foo/qpid-dispatch/tests /foo/qpid-dispatch/tools --show-source
--ignore=E111,E114,E121,E122,E123,E124,E126,E127,E128,E129,E131,E201,E202,E203,E211,E221,E222,E225,E226,E228,E231,E241,E251,E261,E266,E265,E271,E272,E301,E302,E303,E401,E402,E501,E502,E701,E702,E703,E704,E711,E712,E713,E714,E731,F401,F403,F405,F811,F841,H101,H102,H104,H201,H202,H234,H237,H238,H301,H306,H401,H403,H404,H405,W291,W292,W293,W391,W503'
(exited with code 1)
56: py35 create: /foo/qpid-dispatch/build/tests/.tox/py35
56: py35 installdeps: hacking>=1.1.0
56: py35 installed:
flake8==2.6.2,hacking==1.1.0,mccabe==0.5.3,pbr==5.1.3,pycodestyle==2.0.0,pyflakes==1.2.3,six==1.12.0
56: py35 run-test-pre: PYTHONHASHSEED='1741025927'
56: py35 runtests: commands[0] | flake8 --count /foo/qpid-dispatch/python
/foo/qpid-dispatch/console /foo/qpid-dispatch/docs /foo/qpid-dispatch/tests
/foo/qpid-dispatch/tools --show-source
--ignore=E111,E114,E121,E122,E123,E124,E126,E127,E128,E129,E131,E201,E202,E203,E211,E221,E222,E225,E226,E228,E231,E241,E251,E261,E266,E265,E271,E272,E301,E302,E303,E401,E402,E501,E502,E701,E702,E703,E704,E711,E712,E713,E714,E731,F401,F403,F405,F811,F841,H101,H102,H104,H201,H202,H234,H237,H238,H301,H306,H401,H403,H404,H405,W291,W292,W293,W391,W503
56: /foo/qpid-dispatch/tests/system_tests_policy.py:1317:13: E125 continuation
line with same indent as next logical line
56: and self.link_error == False and self._error is None:
56: ^
56: /foo/qpid-dispatch/tests/system_tests_policy.py:1326:13: E125 continuation
line with same indent as next logical line
56: and self.link_error == False and self._error is None:
56: ^
56: /foo/qpid-dispatch/tests/system_tests_policy.py:1345:13: E125 continuation
line with same indent as next logical line
56: and self.link_error == False and self._error is None:
56: ^
56: 3
56: ERROR: InvocationError for command
'/foo/qpid-dispatch/build/tests/.tox/py35/bin/flake8 --count
/foo/qpid-dispatch/python /foo/qpid-dispatch/console /foo/qpid-dispatch/docs
/foo/qpid-dispatch/tests /foo/qpid-dispatch/tools --show-source
--ignore=E111,E114,E121,E122,E123,E124,E126,E127,E128,E129,E131,E201,E202,E203,E211,E221,E222,E225,E226,E228,E231,E241,E251,E261,E266,E265,E271,E272,E301,E302,E303,E401,E402,E501,E502,E701,E702,E703,E704,E711,E712,E713,E714,E731,F401,F403,F405,F811,F841,H101,H102,H104,H201,H202,H234,H237,H238,H301,H306,H401,H403,H404,H405,W291,W292,W293,W391,W503'
(exited with code 1)
56: py36 create: /foo/qpid-dispatch/build/tests/.tox/py36
56: SKIPPED: InterpreterNotFound: python3.6
56: py37 create: /foo/qpid-dispatch/build/tests/.tox/py37
56: SKIPPED: InterpreterNotFound: python3.7
56: ___ summary
56: ERROR: py27: commands failed
56: ERROR: py35: commands failed
56: SKIPPED: py36: InterpreterNotFound: python3.6
56: SKIPPED: py37: InterpreterNotFound: python3.7
56/56 Test #56: python-checker ***Failed
Error regular expression found in output. Regex=[commands failed] 49.73 sec
96% tests passed, 2 tests failed out of 56
Total Test time (real) = 683.94 sec{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2022) Python3 reactor listener client fails with 'Bad file descriptor' exception
Chuck Rolke created PROTON-2022: --- Summary: Python3 reactor listener client fails with 'Bad file descriptor' exception Key: PROTON-2022 URL: https://issues.apache.org/jira/browse/PROTON-2022 Project: Qpid Proton Issue Type: Bug Components: python-binding Affects Versions: proton-c-0.27.0 Environment: Fedora 29 or 28. Python 3. qpid-dispatch master @f359aea 1.6.0-rc2 Reporter: Chuck Rolke Attachments: authz.txt Qpid-dispatch self tests run a helper program qpid-dispatch/tests/authservice.py.in With Python 2 this test program works normally. With Python 3 the test fails with an 'OSError Errno 9, Bad file descriptor' exception. Control is passed from the application to a MessagingHandler with Container(handler).run() The stack trace is posted as an attached file. To reproduce: from the build directory ctest -VV -R authz -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2020) _io.py error path syntax error in python3
[ https://issues.apache.org/jira/browse/PROTON-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chuck Rolke resolved PROTON-2020. - Resolution: Fixed Fix Version/s: proton-c-0.28.0 Fixed at Commit 68b384f > _io.py error path syntax error in python3 > - > > Key: PROTON-2020 > URL: https://issues.apache.org/jira/browse/PROTON-2020 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: proton-c-0.27.0 > Environment: python 3 > Fedora 29 > Proton master > qpid-dispatch master @88e25 > self test system_tests_authz_service_plugin >Reporter: Chuck Rolke >Priority: Major > Fix For: proton-c-0.28.0 > > > * > 39: File "/opt/local/lib64/proton/bindings/python/proton/_io.py", line 138, > in select > * > 39: if e[0] != errno.EINTR: > * > 39: TypeError: 'OSError' object is not subscriptable > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Updated] (DISPATCH-1304) Authz self test fails with python 3
[ https://issues.apache.org/jira/browse/DISPATCH-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chuck Rolke updated DISPATCH-1304: -- Attachment: authz.txt > Authz self test fails with python 3 > --- > > Key: DISPATCH-1304 > URL: https://issues.apache.org/jira/browse/DISPATCH-1304 > Project: Qpid Dispatch > Issue Type: Bug > Components: Tests >Affects Versions: 1.5.0 >Reporter: Chuck Rolke >Assignee: Chuck Rolke >Priority: Major > Attachments: authz.txt > > > This issue is with program authservice.py written to support > system_tests_authz_service_plugin self test. The issue is not with the router > mission code. See attached selftest log file. > A workaround is simply ignore the error that bubbles up from Proton. The onus > is on Proton to figure out what is really wrong and how a caller like > AuthService can avoid the error. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (DISPATCH-1304) Authz self test fails with python 3
Chuck Rolke created DISPATCH-1304: - Summary: Authz self test fails with python 3 Key: DISPATCH-1304 URL: https://issues.apache.org/jira/browse/DISPATCH-1304 Project: Qpid Dispatch Issue Type: Bug Components: Tests Affects Versions: 1.5.0 Reporter: Chuck Rolke Assignee: Chuck Rolke This issue is with program authservice.py written to support system_tests_authz_service_plugin self test. The issue is not with the router mission code. See attached selftest log file. A workaround is simply ignore the error that bubbles up from Proton. The onus is on Proton to figure out what is really wrong and how a caller like AuthService can avoid the error. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2020) _io.py error path syntax error in python3
[ https://issues.apache.org/jira/browse/PROTON-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16801627#comment-16801627 ] ASF subversion and git services commented on PROTON-2020: - Commit 68b384fb187a341e68a396e7d451a5bfacaee16a in qpid-proton's branch refs/heads/master from Charles E. Rolke [ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=68b384f ] PROTON-2020: handle OSError in python 3 > _io.py error path syntax error in python3 > - > > Key: PROTON-2020 > URL: https://issues.apache.org/jira/browse/PROTON-2020 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: proton-c-0.27.0 > Environment: python 3 > Fedora 29 > Proton master > qpid-dispatch master @88e25 > self test system_tests_authz_service_plugin >Reporter: Chuck Rolke >Priority: Major > > * > 39: File "/opt/local/lib64/proton/bindings/python/proton/_io.py", line 138, > in select > * > 39: if e[0] != errno.EINTR: > * > 39: TypeError: 'OSError' object is not subscriptable > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
