[jira] [Commented] (DISPATCH-1110) Intermittent router hang while running QIT's AMQP large content test
[ https://issues.apache.org/jira/browse/DISPATCH-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16642461#comment-16642461 ] Chuck Rolke commented on DISPATCH-1110: --- The title for this issue, "Intermittent router hang while running QIT's AMQP large content test", is a little misleading. The router never hangs. The hang is in the test Receiver which is waiting for 8 messages and only 7 messages arrive before the test times out. As designed, the test Sender sends 8 unacknowledged messages into the router network and then disconnects the AMQP connection after 2, 3, 4, or 5 messages are confirmed through the on_tracker_accept callback. What is the expectation for the remainder of the unconfirmed messages? I added instrumentation to the QIT Sender and Receiver to get timestamps and more internal information about test progress. In particular I added an 'on_tracker_release' callback. When this callback is invoked it means that for some reason the router could not send a message to its destination. During one of the Receiver hang events the Sender is being notified of a message being released: {{stderr= 1539028405.939654 on_sendable: sent 8 messages 1539028405.969454 on_sendable: doing nothing. Already sent 8 messages 1539028405.982049 on_sendable: doing nothing. Already sent 8 messages 1539028405.982106 on_tracker_release: msgsConfirmed 0 amqp_large_content_test::Sender::on_connection_error: amqp:session:invalid-field: sequencing error, expected delivery-id 5, got 4 1539028405.982304 on_container_stop: msgsConfirmed 0 amqp_large_content_test: Sender error: on_connection_error }} When the Sender is notified of a tracker release then the Receiver is guaranteed not to receive all the messages. > Intermittent router hang while running QIT's AMQP large content test > > > Key: DISPATCH-1110 > URL: https://issues.apache.org/jira/browse/DISPATCH-1110 > Project: Qpid Dispatch > Issue Type: Bug > Environment: Standard QIT environment. > Once QIT is built and installed, the environment is set using the config.sh > file. See QUICKSTART for details. >Reporter: Kim van der Riet >Assignee: Ganesh Murthy >Priority: Major > Attachments: qdrouterd.conf > > > When running the Qpid Interop Test's AMQP large content test, a stand-alone > router will intermittently hang and cause the test to time out. > The failure appears to be limited to either the AMQP list or map types, and > usually with the C++ client as the message sender. The C++, Python2 and > Python3 as receiver clients have all seen this failure, but the Python2 > receiver client seems to reproduce more readily on my hardware. > In all cases, the test fails when the router sends what I suppose is the > final transfer of a large message (I have not added up/counted the bytes of > the many preceding transfers) to the consumer. The consumer then sends a > disposition, but the router does not respond again until the test times out. > The consumer can be seen to send heartbeats to the router, but the router > does not send any of its own. > {noformat} > ... (plenty of 65550-sized frames R->C) > R->C 5976 3.454766::1 ::1 AMQP65550 > R->C 5977 3.454775::1 ::1 AMQP65550 > R->C 5978 3.454783::1 ::1 AMQP48171 > C->R 5982 3.529881::1 ::1 AMQP115 disposition > C->R 5984 7.530704::1 ::1 AMQP94 (empty) > C->R 5986 11.532306 ::1 ::1 AMQP94 (empty) > ...{noformat} > There are no errors to be seen in the router logs other than when the > consuming client is killed owing to the test timeout. > {noformat} > ... > 2018-08-29 12:50:23.191754 -0400 SERVER (info) [14]: Accepted connection to > ::1:amqp from ::1:37262 > 2018-08-29 12:51:19.562695 -0400 SERVER (info) [14]: Connection from > ::1:37262 (to ::1:amqp) failed: amqp:connection:framing-error connection > aborted > {noformat} > The reproducer is not very tight on this, and the error occurs about 50% of > the time on my hardware. -- 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-8247) [Broker-J] Upgrade mockito to 2.x
Alex Rudyy created QPID-8247: Summary: [Broker-J] Upgrade mockito to 2.x Key: QPID-8247 URL: https://issues.apache.org/jira/browse/QPID-8247 Project: Qpid Issue Type: Improvement Components: Broker-J Reporter: Alex Rudyy Fix For: qpid-java-broker-7.1.0 The Qpid Broker tests depends on mockito version 1.9.5. In order to be able to build broker with java9 and above we need to upgrade mockito at least to version 2.20.0 where compatibility with java 11 was added. Mockito version 2.22.0 is considered to upgrade to. -- 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-8132) Refresh Apache BCEL dependency to 6.2
[ https://issues.apache.org/jira/browse/QPID-8132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16642101#comment-16642101 ] Alex Rudyy commented on QPID-8132: -- The corresponding change is committed in revision [9dd20fba64c1edc0d68b804f3b02e5792c0f5ffd|https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=9dd20fba64c1edc0d68b804f3b02e5792c0f5ffd] > Refresh Apache BCEL dependency to 6.2 > - > > Key: QPID-8132 > URL: https://issues.apache.org/jira/browse/QPID-8132 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Keith Wall >Assignee: Alex Rudyy >Priority: Minor > Fix For: qpid-java-broker-7.1.0 > > > The Apache BCEL dependency used by Broker-J is getting stale (5.2). 6.2 is > the latest release. -- 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] (QPID-8132) Refresh Apache BCEL dependency to 6.2
[ https://issues.apache.org/jira/browse/QPID-8132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8132: - Status: Reviewable (was: In Progress) > Refresh Apache BCEL dependency to 6.2 > - > > Key: QPID-8132 > URL: https://issues.apache.org/jira/browse/QPID-8132 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Keith Wall >Assignee: Alex Rudyy >Priority: Minor > Fix For: qpid-java-broker-7.1.0 > > > The Apache BCEL dependency used by Broker-J is getting stale (5.2). 6.2 is > the latest release. -- 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] [Assigned] (QPID-8132) Refresh Apache BCEL dependency to 6.2
[ https://issues.apache.org/jira/browse/QPID-8132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy reassigned QPID-8132: Assignee: Alex Rudyy > Refresh Apache BCEL dependency to 6.2 > - > > Key: QPID-8132 > URL: https://issues.apache.org/jira/browse/QPID-8132 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Keith Wall >Assignee: Alex Rudyy >Priority: Minor > Fix For: qpid-java-broker-7.1.0 > > > The Apache BCEL dependency used by Broker-J is getting stale (5.2). 6.2 is > the latest release. -- 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-1131) validate link route prefix field
[ https://issues.apache.org/jira/browse/DISPATCH-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16641861#comment-16641861 ] ASF GitHub Bot commented on DISPATCH-1131: -- Github user codecov-io commented on the issue: https://github.com/apache/qpid-dispatch/pull/388 # [Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/388?src=pr=h1) Report > Merging [#388](https://codecov.io/gh/apache/qpid-dispatch/pull/388?src=pr=desc) into [master](https://codecov.io/gh/apache/qpid-dispatch/commit/3f92be9015615d119cd4707e0ff63a2cf1a73a7c?src=pr=desc) will **increase** coverage by `0.11%`. > The diff coverage is `92.98%`. [![Impacted file tree graph](https://codecov.io/gh/apache/qpid-dispatch/pull/388/graphs/tree.svg?width=650=rk2Cgd27pP=150=pr)](https://codecov.io/gh/apache/qpid-dispatch/pull/388?src=pr=tree) ```diff @@Coverage Diff @@ ## master #388 +/- ## == + Coverage 84.93% 85.05% +0.11% == Files 73 73 Lines 1649916523 +24 == + Hits1401414054 +40 + Misses 2485 2469 -16 ``` | [Impacted Files](https://codecov.io/gh/apache/qpid-dispatch/pull/388?src=pr=tree) | Coverage Δ | | |---|---|---| | [src/router\_core/agent\_config\_link\_route.c](https://codecov.io/gh/apache/qpid-dispatch/pull/388/diff?src=pr=tree#diff-c3JjL3JvdXRlcl9jb3JlL2FnZW50X2NvbmZpZ19saW5rX3JvdXRlLmM=) | `86.74% <100%> (+7.49%)` | :arrow_up: | | [src/router\_core/route\_control.c](https://codecov.io/gh/apache/qpid-dispatch/pull/388/diff?src=pr=tree#diff-c3JjL3JvdXRlcl9jb3JlL3JvdXRlX2NvbnRyb2wuYw==) | `96.03% <100%> (-0.14%)` | :arrow_down: | | [src/router\_core/agent\_config\_address.c](https://codecov.io/gh/apache/qpid-dispatch/pull/388/diff?src=pr=tree#diff-c3JjL3JvdXRlcl9jb3JlL2FnZW50X2NvbmZpZ19hZGRyZXNzLmM=) | `78.82% <91.48%> (+2.5%)` | :arrow_up: | | [src/router\_core/router\_core.c](https://codecov.io/gh/apache/qpid-dispatch/pull/388/diff?src=pr=tree#diff-c3JjL3JvdXRlcl9jb3JlL3JvdXRlcl9jb3JlLmM=) | `92.05% <0%> (-0.34%)` | :arrow_down: | | [src/router\_core/transfer.c](https://codecov.io/gh/apache/qpid-dispatch/pull/388/diff?src=pr=tree#diff-c3JjL3JvdXRlcl9jb3JlL3RyYW5zZmVyLmM=) | `90.52% <0%> (-0.16%)` | :arrow_down: | | [src/parse.c](https://codecov.io/gh/apache/qpid-dispatch/pull/388/diff?src=pr=tree#diff-c3JjL3BhcnNlLmM=) | `86.1% <0%> (+0.27%)` | :arrow_up: | -- [Continue to review full report at Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/388?src=pr=continue). > **Legend** - [Click here to learn more](https://docs.codecov.io/docs/codecov-delta) > `Δ = absolute (impact)`, `ø = not affected`, `? = missing data` > Powered by [Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/388?src=pr=footer). Last update [3f92be9...31bb414](https://codecov.io/gh/apache/qpid-dispatch/pull/388?src=pr=lastupdated). Read the [comment docs](https://docs.codecov.io/docs/pull-request-comments). > validate link route prefix field > > > Key: DISPATCH-1131 > URL: https://issues.apache.org/jira/browse/DISPATCH-1131 > Project: Qpid Dispatch > Issue Type: Bug > Components: Management Agent >Affects Versions: 1.3.0 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Major > Fix For: 1.4.0 > > > Verify the link route prefix field contains a valid prefix -- 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-dispatch issue #388: DISPATCH-1131: add better validation of address pa...
Github user codecov-io commented on the issue: https://github.com/apache/qpid-dispatch/pull/388 # [Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/388?src=pr=h1) Report > Merging [#388](https://codecov.io/gh/apache/qpid-dispatch/pull/388?src=pr=desc) into [master](https://codecov.io/gh/apache/qpid-dispatch/commit/3f92be9015615d119cd4707e0ff63a2cf1a73a7c?src=pr=desc) will **increase** coverage by `0.11%`. > The diff coverage is `92.98%`. [![Impacted file tree graph](https://codecov.io/gh/apache/qpid-dispatch/pull/388/graphs/tree.svg?width=650=rk2Cgd27pP=150=pr)](https://codecov.io/gh/apache/qpid-dispatch/pull/388?src=pr=tree) ```diff @@Coverage Diff @@ ## master #388 +/- ## == + Coverage 84.93% 85.05% +0.11% == Files 73 73 Lines 1649916523 +24 == + Hits1401414054 +40 + Misses 2485 2469 -16 ``` | [Impacted Files](https://codecov.io/gh/apache/qpid-dispatch/pull/388?src=pr=tree) | Coverage Π| | |---|---|---| | [src/router\_core/agent\_config\_link\_route.c](https://codecov.io/gh/apache/qpid-dispatch/pull/388/diff?src=pr=tree#diff-c3JjL3JvdXRlcl9jb3JlL2FnZW50X2NvbmZpZ19saW5rX3JvdXRlLmM=) | `86.74% <100%> (+7.49%)` | :arrow_up: | | [src/router\_core/route\_control.c](https://codecov.io/gh/apache/qpid-dispatch/pull/388/diff?src=pr=tree#diff-c3JjL3JvdXRlcl9jb3JlL3JvdXRlX2NvbnRyb2wuYw==) | `96.03% <100%> (-0.14%)` | :arrow_down: | | [src/router\_core/agent\_config\_address.c](https://codecov.io/gh/apache/qpid-dispatch/pull/388/diff?src=pr=tree#diff-c3JjL3JvdXRlcl9jb3JlL2FnZW50X2NvbmZpZ19hZGRyZXNzLmM=) | `78.82% <91.48%> (+2.5%)` | :arrow_up: | | [src/router\_core/router\_core.c](https://codecov.io/gh/apache/qpid-dispatch/pull/388/diff?src=pr=tree#diff-c3JjL3JvdXRlcl9jb3JlL3JvdXRlcl9jb3JlLmM=) | `92.05% <0%> (-0.34%)` | :arrow_down: | | [src/router\_core/transfer.c](https://codecov.io/gh/apache/qpid-dispatch/pull/388/diff?src=pr=tree#diff-c3JjL3JvdXRlcl9jb3JlL3RyYW5zZmVyLmM=) | `90.52% <0%> (-0.16%)` | :arrow_down: | | [src/parse.c](https://codecov.io/gh/apache/qpid-dispatch/pull/388/diff?src=pr=tree#diff-c3JjL3BhcnNlLmM=) | `86.1% <0%> (+0.27%)` | :arrow_up: | -- [Continue to review full report at Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/388?src=pr=continue). > **Legend** - [Click here to learn more](https://docs.codecov.io/docs/codecov-delta) > `Π= absolute (impact)`, `ø = not affected`, `? = missing data` > Powered by [Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/388?src=pr=footer). Last update [3f92be9...31bb414](https://codecov.io/gh/apache/qpid-dispatch/pull/388?src=pr=lastupdated). Read the [comment docs](https://docs.codecov.io/docs/pull-request-comments). --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1131) validate link route prefix field
[ https://issues.apache.org/jira/browse/DISPATCH-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16641826#comment-16641826 ] ASF GitHub Bot commented on DISPATCH-1131: -- GitHub user kgiusti opened a pull request: https://github.com/apache/qpid-dispatch/pull/388 DISPATCH-1131: add better validation of address patterns and prefixes This moves the address pattern/prefix validation to a common function that can be share by both link routes add configured addresses. This closes #385 You can merge this pull request into a Git repository by running: $ git pull https://github.com/kgiusti/dispatch DISPATCH-1131 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-dispatch/pull/388.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #388 commit c38dde95d5f32a743f41a8a8c728a8c554bf17ff Author: Kenneth Giusti Date: 2018-09-27T17:22:51Z DISPATCH-1131: add better validation of address patterns and prefixes This moves the address pattern/prefix validation to a common function that can be share by both link routes add configured addresses. This closes #385 > validate link route prefix field > > > Key: DISPATCH-1131 > URL: https://issues.apache.org/jira/browse/DISPATCH-1131 > Project: Qpid Dispatch > Issue Type: Bug > Components: Management Agent >Affects Versions: 1.3.0 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Major > Fix For: 1.4.0 > > > Verify the link route prefix field contains a valid prefix -- 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-dispatch pull request #388: DISPATCH-1131: add better validation of add...
GitHub user kgiusti opened a pull request: https://github.com/apache/qpid-dispatch/pull/388 DISPATCH-1131: add better validation of address patterns and prefixes This moves the address pattern/prefix validation to a common function that can be share by both link routes add configured addresses. This closes #385 You can merge this pull request into a Git repository by running: $ git pull https://github.com/kgiusti/dispatch DISPATCH-1131 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/qpid-dispatch/pull/388.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #388 commit c38dde95d5f32a743f41a8a8c728a8c554bf17ff Author: Kenneth Giusti Date: 2018-09-27T17:22:51Z DISPATCH-1131: add better validation of address patterns and prefixes This moves the address pattern/prefix validation to a common function that can be share by both link routes add configured addresses. This closes #385 --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1131) validate link route prefix field
[ https://issues.apache.org/jira/browse/DISPATCH-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16641823#comment-16641823 ] ASF GitHub Bot commented on DISPATCH-1131: -- Github user kgiusti closed the pull request at: https://github.com/apache/qpid-dispatch/pull/387 > validate link route prefix field > > > Key: DISPATCH-1131 > URL: https://issues.apache.org/jira/browse/DISPATCH-1131 > Project: Qpid Dispatch > Issue Type: Bug > Components: Management Agent >Affects Versions: 1.3.0 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Major > Fix For: 1.4.0 > > > Verify the link route prefix field contains a valid prefix -- 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-dispatch pull request #387: DISPATCH-1131: add better validation of add...
Github user kgiusti closed the pull request at: https://github.com/apache/qpid-dispatch/pull/387 --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-1137) Connection info contains stale pointer to container id
[ https://issues.apache.org/jira/browse/DISPATCH-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved DISPATCH-1137. -- Resolution: Fixed > Connection info contains stale pointer to container id > -- > > Key: DISPATCH-1137 > URL: https://issues.apache.org/jira/browse/DISPATCH-1137 > Project: Qpid Dispatch > Issue Type: Bug > Components: Router Node >Affects Versions: 1.3.0 >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Major > Fix For: 1.4.0, 2.0.0 > > > On connection close the memory pointed to by the container name pointer in > the connection info structure has been freed (as found by valgrind). Need to > keep a copy of the name. -- 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] (QPID-8241) [Broker-J] Remove use of javax.xml.bind.DatatypeConverter
[ https://issues.apache.org/jira/browse/QPID-8241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy resolved QPID-8241. -- Resolution: Fixed Assignee: (was: Rob Godfrey) I reviewed the committed changes. They look good to me. Thus, resolving the JIRA. > [Broker-J] Remove use of javax.xml.bind.DatatypeConverter > - > > Key: QPID-8241 > URL: https://issues.apache.org/jira/browse/QPID-8241 > Project: Qpid > Issue Type: Improvement > Components: Broker-J >Reporter: Rob Godfrey >Priority: Major > Fix For: qpid-java-broker-7.1.0 > > > As per [this > comment|https://issues.apache.org/jira/browse/QPID-7885?focusedCommentId=16613383=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16613383] > on QPID-7885, javax.xml.bind.DatatypeConverter is no longer contained in the > default classpath in Java 9. As such we should reimplement all places in the > broker code using this. -- 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] [Assigned] (PROTON-1888) [python] Allow configuration of connection details via a simple config file
[ https://issues.apache.org/jira/browse/PROTON-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell reassigned PROTON-1888: -- Assignee: Gordon Sim > [python] Allow configuration of connection details via a simple config file > --- > > Key: PROTON-1888 > URL: https://issues.apache.org/jira/browse/PROTON-1888 > Project: Qpid Proton > Issue Type: Improvement > Components: python-binding >Reporter: Gordon Sim >Assignee: Gordon Sim >Priority: Major > Fix For: proton-c-0.26.0 > > > It can be convenient to keep details of the connection to be established out > of application code, making it easier to switch between environments. Support > for a simple config file that can be used to point the application at the > right AMQP service would be useful. Ideally this would be common across a > range of clients. -- 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] (PROTON-1888) [python] Allow configuration of connection details via a simple config file
[ https://issues.apache.org/jira/browse/PROTON-1888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1888: --- Summary: [python] Allow configuration of connection details via a simple config file (was: Allow configuration of connection details via a simple config file) > [python] Allow configuration of connection details via a simple config file > --- > > Key: PROTON-1888 > URL: https://issues.apache.org/jira/browse/PROTON-1888 > Project: Qpid Proton > Issue Type: Improvement > Components: python-binding >Reporter: Gordon Sim >Priority: Major > Fix For: proton-c-0.26.0 > > > It can be convenient to keep details of the connection to be established out > of application code, making it easier to switch between environments. Support > for a simple config file that can be used to point the application at the > right AMQP service would be useful. Ideally this would be common across a > range of clients. -- 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] [Closed] (PROTON-1926) 0.26.0 release tasks
[ https://issues.apache.org/jira/browse/PROTON-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell closed PROTON-1926. -- > 0.26.0 release tasks > > > Key: PROTON-1926 > URL: https://issues.apache.org/jira/browse/PROTON-1926 > Project: Qpid Proton > Issue Type: Task > Components: proton-c, release >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: proton-c-0.26.0 > > -- 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-1926) 0.26.0 release tasks
[ https://issues.apache.org/jira/browse/PROTON-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell resolved PROTON-1926. Resolution: Done > 0.26.0 release tasks > > > Key: PROTON-1926 > URL: https://issues.apache.org/jira/browse/PROTON-1926 > Project: Qpid Proton > Issue Type: Task > Components: proton-c, release >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: proton-c-0.26.0 > > -- 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