InputStream in SSLUtil.java line 449
Hello, I noticed that there may be an unclosed resource around line 449 of org.apache.qpid.server.transport.network.security.ssl.SSLUtil.java Let me know what you think or if you need more details. Thanks, Jesse - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[GitHub] qpid-dispatch issue #296: Introduce a new structure under docs for multiple ...
Github user ssorj commented on the issue: https://github.com/apache/qpid-dispatch/pull/296 Squashed and merged at https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=f77f92c . --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (DISPATCH-851) Update CMakeLists.txt to build new Dispatch Router Book
[
https://issues.apache.org/jira/browse/DISPATCH-851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Ross resolved DISPATCH-851.
--
Resolution: Done
> Update CMakeLists.txt to build new Dispatch Router Book
> ---
>
> Key: DISPATCH-851
> URL: https://issues.apache.org/jira/browse/DISPATCH-851
> Project: Qpid Dispatch
> Issue Type: Sub-task
> Components: Documentation
>Reporter: Ben Hardesty
>Assignee: Justin Ross
>Priority: Major
> Fix For: 1.2.0
>
>
> 1. CMakeLists.txt should build the new Dispatch Router book, currently
> located in /doc/new-book/.
> 2. The doc/ directory should support multiple books. For example:
> {code}
> /doc/books/ref-guide
>
> /doc/books/user-guide
> {code}
> The ref-guide would be for automatically-generated reference material such as
> management schema and possibly man pages. The user-guide would be for
> manually-created content (i.e. the Dispatch Router Book).
> 3. The new book should be built using AsciiDoctor instead of AsciiDoc Python
> (additional info here:
> http://asciidoctor.org/docs/user-manual/#migrating-from-asciidoc-python).
> Note: For copying the book dir images, note that the images are now located
> in /doc/new-book/images/. Before, they were located in /doc/book/.
--
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-851) Update CMakeLists.txt to build new Dispatch Router Book
[
https://issues.apache.org/jira/browse/DISPATCH-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524232#comment-16524232
]
ASF subversion and git services commented on DISPATCH-851:
--
Commit f77f92cbeb5cf88c9ddcd577ab4b2deadb3dedf5 in qpid-dispatch's branch
refs/heads/master from [~jr...@redhat.com]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=f77f92c ]
DISPATCH-851: Move the new book into primary position and reorg the docs
> Update CMakeLists.txt to build new Dispatch Router Book
> ---
>
> Key: DISPATCH-851
> URL: https://issues.apache.org/jira/browse/DISPATCH-851
> Project: Qpid Dispatch
> Issue Type: Sub-task
> Components: Documentation
>Reporter: Ben Hardesty
>Assignee: Justin Ross
>Priority: Major
> Fix For: 1.2.0
>
>
> 1. CMakeLists.txt should build the new Dispatch Router book, currently
> located in /doc/new-book/.
> 2. The doc/ directory should support multiple books. For example:
> {code}
> /doc/books/ref-guide
>
> /doc/books/user-guide
> {code}
> The ref-guide would be for automatically-generated reference material such as
> management schema and possibly man pages. The user-guide would be for
> manually-created content (i.e. the Dispatch Router Book).
> 3. The new book should be built using AsciiDoctor instead of AsciiDoc Python
> (additional info here:
> http://asciidoctor.org/docs/user-manual/#migrating-from-asciidoc-python).
> Note: For copying the book dir images, note that the images are now located
> in /doc/new-book/images/. Before, they were located in /doc/book/.
--
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-1875) [Ruby] Error running ruby-test-container on Raspbian Jesse
[
https://issues.apache.org/jira/browse/PROTON-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524202#comment-16524202
]
Andrew Stitcher commented on PROTON-1875:
-
It seems that Thread.report_on_exception is enabled in ruby 2.5 so is just not
available in 2.3.3
> [Ruby] Error running ruby-test-container on Raspbian Jesse
> --
>
> Key: PROTON-1875
> URL: https://issues.apache.org/jira/browse/PROTON-1875
> Project: Qpid Proton
> Issue Type: Bug
> Components: ruby-binding
>Affects Versions: proton-c-0.24.0
> Environment: ruby 2.3.3p222 (2016-11-21) [arm-linux-gnueabihf]
>Reporter: Andrew Stitcher
>Assignee: Alan Conway
>Priority: Major
>
> Get this error when running the tests:
> {noformat}
> test 36
> Start 36: ruby-test-container
> 36: Test command: /usr/bin/python
> "/home/andrew/Source/qpid-proton/src/scripts/env.py" "--"
> "PATH=/home/andrew/Source/qpid-proton/bld/ruby:/home/andrew/Source/qpid-proton/bld/c:/home/andrew/.cargo/bin:/home/andrew/.cargo/bin:/home/andrew/.local/bin:/home/andrew/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games"
>
> "RUBYLIB=/home/andrew/Source/qpid-proton/src/ruby/lib:/home/andrew/Source/qpid-proton/src/ruby/tests:/home/andrew/Source/qpid-proton/src/ruby/spec:/home/andrew/Source/qpid-proton/bld/ruby:/home/andrew/Source/qpid-proton/bld/c:"
> "SASLPASSWD=/usr/sbin/saslpasswd2" "/usr/bin/ruby"
> "/home/andrew/Source/qpid-proton/src/ruby/tests/test_container.rb" "-v"
> 36: Test timeout computed to be: 1500
> 36: /home/andrew/Source/qpid-proton/src/ruby/tests/test_container.rb:25:in
> `': undefined method `report_on_exception=' for Thread:Class
> (NoMethodError)
> 1/2 Test #36: ruby-test-container ..***Failed0.96 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-1875) [Ruby] Error running ruby-test-container on Raspbian Jesse
Andrew Stitcher created PROTON-1875:
---
Summary: [Ruby] Error running ruby-test-container on Raspbian Jesse
Key: PROTON-1875
URL: https://issues.apache.org/jira/browse/PROTON-1875
Project: Qpid Proton
Issue Type: Bug
Components: ruby-binding
Affects Versions: proton-c-0.24.0
Environment: ruby 2.3.3p222 (2016-11-21) [arm-linux-gnueabihf]
Reporter: Andrew Stitcher
Assignee: Alan Conway
Get this error when running the tests:
{noformat}
test 36
Start 36: ruby-test-container
36: Test command: /usr/bin/python
"/home/andrew/Source/qpid-proton/src/scripts/env.py" "--"
"PATH=/home/andrew/Source/qpid-proton/bld/ruby:/home/andrew/Source/qpid-proton/bld/c:/home/andrew/.cargo/bin:/home/andrew/.cargo/bin:/home/andrew/.local/bin:/home/andrew/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games"
"RUBYLIB=/home/andrew/Source/qpid-proton/src/ruby/lib:/home/andrew/Source/qpid-proton/src/ruby/tests:/home/andrew/Source/qpid-proton/src/ruby/spec:/home/andrew/Source/qpid-proton/bld/ruby:/home/andrew/Source/qpid-proton/bld/c:"
"SASLPASSWD=/usr/sbin/saslpasswd2" "/usr/bin/ruby"
"/home/andrew/Source/qpid-proton/src/ruby/tests/test_container.rb" "-v"
36: Test timeout computed to be: 1500
36: /home/andrew/Source/qpid-proton/src/ruby/tests/test_container.rb:25:in
`': undefined method `report_on_exception=' for Thread:Class
(NoMethodError)
1/2 Test #36: ruby-test-container ..***Failed0.96 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
[GitHub] qpid-dispatch issue #296: Introduce a new structure under docs for multiple ...
Github user codecov-io commented on the issue: https://github.com/apache/qpid-dispatch/pull/296 # [Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/296?src=pr=h1) Report > :exclamation: No coverage uploaded for pull request base (`master@7c8f311`). [Click here to learn what that means](https://docs.codecov.io/docs/error-reference#section-missing-base-commit). > The diff coverage is `n/a`. [](https://codecov.io/gh/apache/qpid-dispatch/pull/296?src=pr=tree) ```diff @@Coverage Diff@@ ## master #296 +/- ## = Coverage ? 86.56% = Files ? 69 Lines ?15476 Branches ?0 = Hits ?13397 Misses? 2079 Partials ?0 ``` -- [Continue to review full report at Codecov](https://codecov.io/gh/apache/qpid-dispatch/pull/296?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/296?src=pr=footer). Last update [7c8f311...643bd60](https://codecov.io/gh/apache/qpid-dispatch/pull/296?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] [Resolved] (PROTON-1858) [Python] Rewrite wrapped C handlers in python
[ https://issues.apache.org/jira/browse/PROTON-1858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-1858. - Resolution: Fixed Fix Version/s: proton-c-0.24.0 The Handshaker and FlowController handlers have been rewritten. The IOHandler has not at this point, but may not need to be rewritten seperately from the dispatch loop itself. > [Python] Rewrite wrapped C handlers in python > - > > Key: PROTON-1858 > URL: https://issues.apache.org/jira/browse/PROTON-1858 > Project: Qpid Proton > Issue Type: Improvement > Components: python-binding >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.24.0 > > > This is necessary to move the python bindings off the reactor implementations > and only depend on qpid-proton-core -- 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-1874) Valgrind complains about epoll_ctl accessing uninitialised data
[ https://issues.apache.org/jira/browse/PROTON-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-1874. - Resolution: Fixed Fix Version/s: proton-c-0.25.0 > Valgrind complains about epoll_ctl accessing uninitialised data > --- > > Key: PROTON-1874 > URL: https://issues.apache.org/jira/browse/PROTON-1874 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c > Environment: Raspberry Pi 3, Raspbian Jesse >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Minor > Fix For: proton-c-0.25.0 > > > The valgrind complaint is true, but probably harmless - it will only be seen > on 32 bit machines where the final 4 bytes of the ev.data union (which is 8 > bytes) are not initialised as they are not in ev.data.ptr which is only 4 > bytes. -- 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-1874) Valgrind complains about epoll_ctl accessing uninitialised data
[ https://issues.apache.org/jira/browse/PROTON-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524196#comment-16524196 ] ASF subversion and git services commented on PROTON-1874: - Commit 37cd347de669a99137cc45e4d886c47e70b9e3e8 in qpid-proton's branch refs/heads/master from [~astitcher] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=37cd347 ] PROTON-1874: Silence valgrind complaint on 32 bit machines with epoll proactor > Valgrind complains about epoll_ctl accessing uninitialised data > --- > > Key: PROTON-1874 > URL: https://issues.apache.org/jira/browse/PROTON-1874 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c > Environment: Raspberry Pi 3, Raspbian Jesse >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Minor > > The valgrind complaint is true, but probably harmless - it will only be seen > on 32 bit machines where the final 4 bytes of the ev.data union (which is 8 > bytes) are not initialised as they are not in ev.data.ptr which is only 4 > bytes. -- 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-1874) Valgrind complains about epoll_ctl accessing uninitialised data
Andrew Stitcher created PROTON-1874: --- Summary: Valgrind complains about epoll_ctl accessing uninitialised data Key: PROTON-1874 URL: https://issues.apache.org/jira/browse/PROTON-1874 Project: Qpid Proton Issue Type: Bug Components: proton-c Environment: Raspberry Pi 3, Raspbian Jesse Reporter: Andrew Stitcher Assignee: Andrew Stitcher The valgrind complaint is true, but probably harmless - it will only be seen on 32 bit machines where the final 4 bytes of the ev.data union (which is 8 bytes) are not initialised as they are not in ev.data.ptr which is only 4 bytes. -- 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] (QPIDJMS-398) Update testing dependencies and bundle plugin to latest
[ https://issues.apache.org/jira/browse/QPIDJMS-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved QPIDJMS-398. -- Resolution: Fixed > Update testing dependencies and bundle plugin to latest > --- > > Key: QPIDJMS-398 > URL: https://issues.apache.org/jira/browse/QPIDJMS-398 > Project: Qpid JMS > Issue Type: Task > Components: qpid-jms-client >Affects Versions: 0.34.0 >Reporter: Timothy Bish >Assignee: Timothy Bish >Priority: Major > Fix For: 0.35.0 > > > Update the test dependencies for Mockito and Jetty to latest and switch to > latest bundle plugin. -- 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] (QPIDJMS-398) Update testing dependencies and bundle plugin to latest
Timothy Bish created QPIDJMS-398: Summary: Update testing dependencies and bundle plugin to latest Key: QPIDJMS-398 URL: https://issues.apache.org/jira/browse/QPIDJMS-398 Project: Qpid JMS Issue Type: Task Components: qpid-jms-client Affects Versions: 0.34.0 Reporter: Timothy Bish Assignee: Timothy Bish Fix For: 0.35.0 Update the test dependencies for Mockito and Jetty to latest and switch to latest bundle plugin. -- 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] (QPIDJMS-397) Update to the current v19 apache parent pom
[ https://issues.apache.org/jira/browse/QPIDJMS-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524146#comment-16524146 ] ASF subversion and git services commented on QPIDJMS-397: - Commit 7c5debd0009fe5c49761fd5f646e7b3a2f64c6e6 in qpid-jms's branch refs/heads/master from [~tabish121] [ https://git-wip-us.apache.org/repos/asf?p=qpid-jms.git;h=7c5debd ] QPIDJMS-397 Update to the current v19 Apache parent pom Update to latest pom to capture latest plugins and align with other apache Java components. > Update to the current v19 apache parent pom > --- > > Key: QPIDJMS-397 > URL: https://issues.apache.org/jira/browse/QPIDJMS-397 > Project: Qpid JMS > Issue Type: Task > Components: qpid-jms-client >Affects Versions: 0.34.0 >Reporter: Timothy Bish >Assignee: Timothy Bish >Priority: Major > Fix For: 0.35.0 > > > The build should be updated to a current apache parent pom version to use > more current plugins etc and better align with the other java components. -- 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] (QPIDJMS-397) Update to the current v19 apache parent pom
[ https://issues.apache.org/jira/browse/QPIDJMS-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved QPIDJMS-397. -- Resolution: Fixed > Update to the current v19 apache parent pom > --- > > Key: QPIDJMS-397 > URL: https://issues.apache.org/jira/browse/QPIDJMS-397 > Project: Qpid JMS > Issue Type: Task > Components: qpid-jms-client >Affects Versions: 0.34.0 >Reporter: Timothy Bish >Assignee: Timothy Bish >Priority: Major > Fix For: 0.35.0 > > > The build should be updated to a current apache parent pom version to use > more current plugins etc and better align with the other java components. -- 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-1008) Router should preserve original connection information when attempting to make failover connections
[
https://issues.apache.org/jira/browse/DISPATCH-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-1008:
Fix Version/s: 1.2.0
> Router should preserve original connection information when attempting to
> make failover connections
> ---
>
> Key: DISPATCH-1008
> URL: https://issues.apache.org/jira/browse/DISPATCH-1008
> Project: Qpid Dispatch
> Issue Type: Bug
>Reporter: Ganesh Murthy
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: 1.2.0
>
> Attachments: broker-slave.xml, broker.xml, qdrouterd-failover.conf
>
>
> # Start artemis master and slave brokers and the router with the attached
> config files.
> # Notice that the router receives an open frame from the master broker with
> the following failover information
> #
> {noformat}
> 2018-05-22 22:11:11.830106 -0230 SERVER (trace) [1]:0 <- @open(16)
> [container-id="localhost", max-frame-size=4294967295, channel-max=65535,
> idle-time-out=3,
> offered-capabilities=@PN_SYMBOL[:"sole-connection-for-container",
> :"DELAYED_DELIVERY", :"SHARED-SUBS", :"ANONYMOUS-RELAY"],
> properties={:product="apache-activemq-artemis",
> :"failover-server-list"=[{:hostname="0.0.0.8", :scheme="amqp", :port=61617,
> :"network-host"="0.0.0.0"}]"}]{noformat}
>
> # Now, kill the master broker and notice that the router correctly fails
> over to the slave broker. But the slave broker does not provide any failover
> information in its open frame and hence the router erases its original master
> broker connection information
> # When the master broker is now restarted and the slave broker is killed,
> the router attempts to repeatedly connect only to the slave broker but never
> attempts a connection to the master broker.
> # If the router did not erase its failover list but preserved the original
> master connection information, it would have connected the master broker.
--
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-1045) Sometimes close connetion after releasing partial multi-frame messsage
[ https://issues.apache.org/jira/browse/DISPATCH-1045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1045: Fix Version/s: 1.2.0 > Sometimes close connetion after releasing partial multi-frame messsage > -- > > Key: DISPATCH-1045 > URL: https://issues.apache.org/jira/browse/DISPATCH-1045 > Project: Qpid Dispatch > Issue Type: Bug > Components: Router Node >Affects Versions: 1.1.0 >Reporter: Alan Conway >Assignee: Ganesh Murthy >Priority: Major > Fix For: 1.2.0 > > > Since DISPATCH-1012 the router releases undeliverable deliveries. > In the case of a multi-frame delivery, it is possible for dispatch to release > it before the entire delivery has been received. Presently dispatch settles > such deliveries and advances its link. That means that if another transfer > for the same delivery arrives, dispatch regards it as a new message with an > invalid delivery-id and closes the connection. Since the release is > asynchronous, there's no way for the client to avoid this possibility. > Worth checking the spec but I suspect we should be dropping the extra data > rather than closing the connection. Need to investigate how this would work > in proton - I think we'd update the delivery without settling it and then > wait for the remote to settle before finally throwing it away. > -- 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] (DISPATCH-934) Add a way to annotate configuration as experimental
[ https://issues.apache.org/jira/browse/DISPATCH-934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross reassigned DISPATCH-934: - Assignee: (was: Alan Conway) > Add a way to annotate configuration as experimental > --- > > Key: DISPATCH-934 > URL: https://issues.apache.org/jira/browse/DISPATCH-934 > Project: Qpid Dispatch > Issue Type: New Feature > Components: Management Agent >Reporter: Ted Ross >Priority: Minor > Fix For: Backlog > > > Add a management-schema annotation for entities and attributes that labels > them as "experimental". Any time an experimental item is used in > configuration (or via the management protocol) the router shall issue a log > warning stating that the configuration is experimental and may not be > supported in the future. > -- 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-934) Add a way to annotate configuration as experimental
[ https://issues.apache.org/jira/browse/DISPATCH-934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-934: -- Fix Version/s: (was: 1.2.0) Backlog > Add a way to annotate configuration as experimental > --- > > Key: DISPATCH-934 > URL: https://issues.apache.org/jira/browse/DISPATCH-934 > Project: Qpid Dispatch > Issue Type: New Feature > Components: Management Agent >Reporter: Ted Ross >Priority: Minor > Fix For: Backlog > > > Add a management-schema annotation for entities and attributes that labels > them as "experimental". Any time an experimental item is used in > configuration (or via the management protocol) the router shall issue a log > warning stating that the configuration is experimental and may not be > supported in the future. > -- 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-939) Router aborts transfer, closes connection with error on QIT amqp_large_content_test
[
https://issues.apache.org/jira/browse/DISPATCH-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross updated DISPATCH-939:
--
Summary: Router aborts transfer, closes connection with error on QIT
amqp_large_content_test (was: Router aborts transfer, closes connection with
error on QIT amqp_large_contnet_test)
> Router aborts transfer, closes connection with error on QIT
> amqp_large_content_test
> ---
>
> Key: DISPATCH-939
> URL: https://issues.apache.org/jira/browse/DISPATCH-939
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Reporter: Kim van der Riet
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: Backlog
>
> Attachments: dispatch.multiframe.06.pcapng, qdrouterd.conf
>
>
> The Qpid Interop Test large content test repeatedly fails when run against a
> single-node dispatch router (dispatch config file attached).
> The test that reproduces this most readily but without too much length is the
> following:
> {noformat}
> python -m qpid_interop_test.amqp_large_content_test --include-shim ProtonCpp
> --include-type list
> WARNING: Rhea Javascript shims not found
> Test Broker: qpid-dispatch-router v.1.0.0 on
> test_list_ProtonCpp->ProtonCpp (__main__.ListTestCase) ... ERROR
> ==
> ERROR: test_list_ProtonCpp->ProtonCpp (__main__.ListTestCase)
> --
> Traceback (most recent call last):
> File
> "/home/kvdr/RedHat/install/lib/python2.7/site-packages/qpid_interop_test/amqp_large_content_test.py",
> line 196, in inner_test_method
> timeout)
> File
> "/home/kvdr/RedHat/install/lib/python2.7/site-packages/qpid_interop_test/amqp_large_content_test.py",
> line 121, in run_test
> raise InteropTestError('Receive shim \'%s\':\n%s' % (receive_shim.NAME,
> receive_obj))
> InteropTestError: Receive shim 'ProtonCpp':
> amqp_large_content_test receiver error: receiver read failure
> --
> Ran 1 test in 0.801s
> FAILED (errors=1)
> {noformat}
> The router left the following message:
> {noformat}
> SERVER (info) Connection from ::1:57020 (to ::1:amqp) failed:
> amqp:connection:framing-error connection aborted{noformat}
> The attached capture file shows a typical observable sequence of events on
> the wire that lead up to the failure. The test that created this error
> consists of 4 messages:
> # A 1MB message consisting of a list containing a single 1MB string
> (delivery-id 0);
> # A 1MB message consisting of a list containing 16 64kB strings (delivery-id
> 1);
> # A 10MB message consisting of a list containing a single 10MB string
> (delivery-id 2);
> # A 10MB message consisting of a list containing 16 655MB strings
> (delivery-id 3).
> The following is a summary of what transpires:
> * *Frame 1527:* The sender completes sending the last message (delivery-id
> 3) to the router, and closes the connection (without waiting for
> dispositions). At this point, the receiver is in the process of being sent
> message-id 2.
> * *Frame 1539:* Last transfer for message-id 2 from dispatch to receiver.
> * *Frame 1545 - 1598:* Message-id 3 starts being sent to receiver.
> * *Frame 1600:* Dispatch router returns close to sender (initiated in *frame
> 1527*). No errors or arguments.
> * *Frame 1605:* Receiver sends flow, disposition for delivery-id 2
> (completed in *frame 1539*).
> * *Frame 1607 - 1618:* Continue to send message with delivery-id 3 to
> receiver.
> * *Frame 1619:* Transfer aborted. A transfer performative with more=False,
> Settled=True, Aborted=True.
> * *Frame 1622:* Close sent from Dispatch to Receiver with Condition:
> {{amqp:connection:framing-error}}, Description: {{connection aborted}}.
> All instances of this error have occurred between dispatch router and the
> receiver once the sender has closed its connection.
>
--
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] (DISPATCH-939) Router aborts transfer, closes connection with error on QIT amqp_large_content_test
[
https://issues.apache.org/jira/browse/DISPATCH-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross reassigned DISPATCH-939:
-
Assignee: (was: Ganesh Murthy)
> Router aborts transfer, closes connection with error on QIT
> amqp_large_content_test
> ---
>
> Key: DISPATCH-939
> URL: https://issues.apache.org/jira/browse/DISPATCH-939
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Reporter: Kim van der Riet
>Priority: Major
> Fix For: Backlog
>
> Attachments: dispatch.multiframe.06.pcapng, qdrouterd.conf
>
>
> The Qpid Interop Test large content test repeatedly fails when run against a
> single-node dispatch router (dispatch config file attached).
> The test that reproduces this most readily but without too much length is the
> following:
> {noformat}
> python -m qpid_interop_test.amqp_large_content_test --include-shim ProtonCpp
> --include-type list
> WARNING: Rhea Javascript shims not found
> Test Broker: qpid-dispatch-router v.1.0.0 on
> test_list_ProtonCpp->ProtonCpp (__main__.ListTestCase) ... ERROR
> ==
> ERROR: test_list_ProtonCpp->ProtonCpp (__main__.ListTestCase)
> --
> Traceback (most recent call last):
> File
> "/home/kvdr/RedHat/install/lib/python2.7/site-packages/qpid_interop_test/amqp_large_content_test.py",
> line 196, in inner_test_method
> timeout)
> File
> "/home/kvdr/RedHat/install/lib/python2.7/site-packages/qpid_interop_test/amqp_large_content_test.py",
> line 121, in run_test
> raise InteropTestError('Receive shim \'%s\':\n%s' % (receive_shim.NAME,
> receive_obj))
> InteropTestError: Receive shim 'ProtonCpp':
> amqp_large_content_test receiver error: receiver read failure
> --
> Ran 1 test in 0.801s
> FAILED (errors=1)
> {noformat}
> The router left the following message:
> {noformat}
> SERVER (info) Connection from ::1:57020 (to ::1:amqp) failed:
> amqp:connection:framing-error connection aborted{noformat}
> The attached capture file shows a typical observable sequence of events on
> the wire that lead up to the failure. The test that created this error
> consists of 4 messages:
> # A 1MB message consisting of a list containing a single 1MB string
> (delivery-id 0);
> # A 1MB message consisting of a list containing 16 64kB strings (delivery-id
> 1);
> # A 10MB message consisting of a list containing a single 10MB string
> (delivery-id 2);
> # A 10MB message consisting of a list containing 16 655MB strings
> (delivery-id 3).
> The following is a summary of what transpires:
> * *Frame 1527:* The sender completes sending the last message (delivery-id
> 3) to the router, and closes the connection (without waiting for
> dispositions). At this point, the receiver is in the process of being sent
> message-id 2.
> * *Frame 1539:* Last transfer for message-id 2 from dispatch to receiver.
> * *Frame 1545 - 1598:* Message-id 3 starts being sent to receiver.
> * *Frame 1600:* Dispatch router returns close to sender (initiated in *frame
> 1527*). No errors or arguments.
> * *Frame 1605:* Receiver sends flow, disposition for delivery-id 2
> (completed in *frame 1539*).
> * *Frame 1607 - 1618:* Continue to send message with delivery-id 3 to
> receiver.
> * *Frame 1619:* Transfer aborted. A transfer performative with more=False,
> Settled=True, Aborted=True.
> * *Frame 1622:* Close sent from Dispatch to Receiver with Condition:
> {{amqp:connection:framing-error}}, Description: {{connection aborted}}.
> All instances of this error have occurred between dispatch router and the
> receiver once the sender has closed its connection.
>
--
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] (QPIDJMS-397) Update to the current v19 apache parent pom
Timothy Bish created QPIDJMS-397: Summary: Update to the current v19 apache parent pom Key: QPIDJMS-397 URL: https://issues.apache.org/jira/browse/QPIDJMS-397 Project: Qpid JMS Issue Type: Task Components: qpid-jms-client Affects Versions: 0.34.0 Reporter: Timothy Bish Assignee: Timothy Bish Fix For: 0.35.0 The build should be updated to a current apache parent pom version to use more current plugins etc and better align with the other java components. -- 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-939) Router aborts transfer, closes connection with error on QIT amqp_large_contnet_test
[
https://issues.apache.org/jira/browse/DISPATCH-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross updated DISPATCH-939:
--
Fix Version/s: (was: 1.2.0)
Backlog
> Router aborts transfer, closes connection with error on QIT
> amqp_large_contnet_test
> ---
>
> Key: DISPATCH-939
> URL: https://issues.apache.org/jira/browse/DISPATCH-939
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Container
>Reporter: Kim van der Riet
>Assignee: Ganesh Murthy
>Priority: Major
> Fix For: Backlog
>
> Attachments: dispatch.multiframe.06.pcapng, qdrouterd.conf
>
>
> The Qpid Interop Test large content test repeatedly fails when run against a
> single-node dispatch router (dispatch config file attached).
> The test that reproduces this most readily but without too much length is the
> following:
> {noformat}
> python -m qpid_interop_test.amqp_large_content_test --include-shim ProtonCpp
> --include-type list
> WARNING: Rhea Javascript shims not found
> Test Broker: qpid-dispatch-router v.1.0.0 on
> test_list_ProtonCpp->ProtonCpp (__main__.ListTestCase) ... ERROR
> ==
> ERROR: test_list_ProtonCpp->ProtonCpp (__main__.ListTestCase)
> --
> Traceback (most recent call last):
> File
> "/home/kvdr/RedHat/install/lib/python2.7/site-packages/qpid_interop_test/amqp_large_content_test.py",
> line 196, in inner_test_method
> timeout)
> File
> "/home/kvdr/RedHat/install/lib/python2.7/site-packages/qpid_interop_test/amqp_large_content_test.py",
> line 121, in run_test
> raise InteropTestError('Receive shim \'%s\':\n%s' % (receive_shim.NAME,
> receive_obj))
> InteropTestError: Receive shim 'ProtonCpp':
> amqp_large_content_test receiver error: receiver read failure
> --
> Ran 1 test in 0.801s
> FAILED (errors=1)
> {noformat}
> The router left the following message:
> {noformat}
> SERVER (info) Connection from ::1:57020 (to ::1:amqp) failed:
> amqp:connection:framing-error connection aborted{noformat}
> The attached capture file shows a typical observable sequence of events on
> the wire that lead up to the failure. The test that created this error
> consists of 4 messages:
> # A 1MB message consisting of a list containing a single 1MB string
> (delivery-id 0);
> # A 1MB message consisting of a list containing 16 64kB strings (delivery-id
> 1);
> # A 10MB message consisting of a list containing a single 10MB string
> (delivery-id 2);
> # A 10MB message consisting of a list containing 16 655MB strings
> (delivery-id 3).
> The following is a summary of what transpires:
> * *Frame 1527:* The sender completes sending the last message (delivery-id
> 3) to the router, and closes the connection (without waiting for
> dispositions). At this point, the receiver is in the process of being sent
> message-id 2.
> * *Frame 1539:* Last transfer for message-id 2 from dispatch to receiver.
> * *Frame 1545 - 1598:* Message-id 3 starts being sent to receiver.
> * *Frame 1600:* Dispatch router returns close to sender (initiated in *frame
> 1527*). No errors or arguments.
> * *Frame 1605:* Receiver sends flow, disposition for delivery-id 2
> (completed in *frame 1539*).
> * *Frame 1607 - 1618:* Continue to send message with delivery-id 3 to
> receiver.
> * *Frame 1619:* Transfer aborted. A transfer performative with more=False,
> Settled=True, Aborted=True.
> * *Frame 1622:* Close sent from Dispatch to Receiver with Condition:
> {{amqp:connection:framing-error}}, Description: {{connection aborted}}.
> All instances of this error have occurred between dispatch router and the
> receiver once the sender has closed its connection.
>
--
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] (DISPATCH-1046) system_tests_policy fail in python3 environment
[
https://issues.apache.org/jira/browse/DISPATCH-1046?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti reassigned DISPATCH-1046:
Assignee: Ken Giusti
> system_tests_policy fail in python3 environment
> ---
>
> Key: DISPATCH-1046
> URL: https://issues.apache.org/jira/browse/DISPATCH-1046
> Project: Qpid Dispatch
> Issue Type: Bug
>Reporter: Ken Giusti
>Assignee: Ken Giusti
>Priority: Major
> Attachments: Dockerfile-ctest
>
>
> Can be reproduced by building and running the attached dockerfile
> -
> Start 21: system_tests_policy
> 21: Test command: /usr/bin/python
> "/main/qpid-dispatch-master/BUILD/tests/run.py" "-x" "unit2" "-v"
> "system_tests_policy"
> 21: Test timeout computed to be: 1500
> 21: test_verify_maximum_connections
> (system_tests_policy.AbsoluteConnectionCountLimit) ... ok
> 21: test_01_router_links_allowed
> (system_tests_policy.InterrouterLinksAllowed) ... ok
> 21: test_repeated_create_delete (system_tests_policy.LoadPolicyFromFolder)
> ... ok
> 21: test_verify_policies_are_loaded
> (system_tests_policy.LoadPolicyFromFolder) ... ok
> 21: test_verify_policy_add_update_delete
> (system_tests_policy.LoadPolicyFromFolder) ... ok
> 21: ERROR
> 21: test_link_name_parse_tree_patterns
> (system_tests_policy.PolicyLinkNamePatternTest) ... ERROR
> 21: test_03_policy_warnings (system_tests_policy.PolicyWarnings) ... ok
> 21: test_verify_n_receivers (system_tests_policy.SenderReceiverLimits) ... ok
> 21: test_verify_n_senders (system_tests_policy.SenderReceiverLimits) ... ok
> 21: test_verify_vhost_maximum_connections
> (system_tests_policy.VhostPolicyFromRouterConfig) ... ok
> 21: test_vhost_allowed_addresses
> (system_tests_policy.VhostPolicyFromRouterConfig) ... ok
> 21: test_vhost_denied_addresses
> (system_tests_policy.VhostPolicyFromRouterConfig) ... ok
> 21: test_01_id_vs_hostname (system_tests_policy.VhostPolicyNameField) ... ok
> 21:
> 21: ==
> 21: ERROR: setUpClass (system_tests_policy.PolicyHostamePatternTest)
> 21: --
> 21: Traceback (most recent call last):
> 21: File "/main/qpid-dispatch-master/tests/system_test.py", line 175, in
> wait_port
> 21: **retry_kwargs)
> 21: File "/main/qpid-dispatch-master/tests/system_test.py", line 134, in
> retry_exception
> 21: return function()
> 21: File "/main/qpid-dispatch-master/tests/system_test.py", line 174, in
>
> 21: retry_exception(lambda: s.connect((host, port)), exception_test=check,
> 21: ConnectionRefusedError: [Errno 111] Connection refused
> 21:
> 21: During handling of the above exception, another exception occurred:
> 21:
> 21: Traceback (most recent call last):
> 21: File "/main/qpid-dispatch-master/tests/system_tests_policy.py", line
> 852, in setUpClass
> 21: cls.router = cls.tester.qdrouterd('PolicyVhostNamePatternTest',
> config, wait=True)
> 21: File "/main/qpid-dispatch-master/tests/system_test.py", line 562, in
> qdrouterd
> 21: return self.cleanup(Qdrouterd(*args, **kwargs))
> 21: File "/main/qpid-dispatch-master/tests/system_test.py", line 352, in
> __init__
> 21: self.wait_ready()
> 21: File "/main/qpid-dispatch-master/tests/system_test.py", line 483, in
> wait_ready
> 21: self.wait_ports(**retry_kwargs)
> 21: File "/main/qpid-dispatch-master/tests/system_test.py", line 468, in
> wait_ports
> 21: wait_ports(self.ports_family, **retry_kwargs)
> 21: File "/main/qpid-dispatch-master/tests/system_test.py", line 185, in
> wait_ports
> 21: wait_port(port=port, protocol_family=protocol_family, **retry_kwargs)
> 21: File "/main/qpid-dispatch-master/tests/system_test.py", line 177, in
> wait_port
> 21: raise Exception("wait_port timeout on host %s port %s: %s"%(host,
> port, e))
> 21: Exception: wait_port timeout on host 127.0.0.1 port 21435: [Errno 111]
> Connection refused
> 21:
> 21: ==
> 21: ERROR: test_link_name_parse_tree_patterns
> (system_tests_policy.PolicyLinkNamePatternTest)
> 21: --
> 21: Traceback (most recent call last):
> 21: File "/main/qpid-dispatch-master/tests/system_tests_policy.py", line
> 642, in run_qdmanage
> 21: p.teardown()
> 21: File "/main/qpid-dispatch-master/tests/system_test.py", line 264, in
> teardown
> 21: error("exit code %s, expected %s" % (status, self.expect))
> 21: File "/main/qpid-dispatch-master/tests/system_test.py", line 254, in
> error
> 21: self.outfile + '.cmd', f.read()));
> 21: RuntimeError: Process 352 error: exit code 1, expected 0
> 21: qdmanage create
[jira] [Resolved] (DISPATCH-1051) Python memory leak via PyLong_FromLong
[ https://issues.apache.org/jira/browse/DISPATCH-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved DISPATCH-1051. -- Resolution: Fixed > Python memory leak via PyLong_FromLong > -- > > Key: DISPATCH-1051 > URL: https://issues.apache.org/jira/browse/DISPATCH-1051 > Project: Qpid Dispatch > Issue Type: Bug >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Major > Fix For: 1.2.0 > > > ==7883== 24 bytes in 1 blocks are definitely lost in loss record 50 of 3,471 > ==7883==at 0x4C2CB6B: malloc (vg_replace_malloc.c:299) > ==7883==by 0x5BF0091: PyObject_Malloc (obmalloc.c:982) > ==7883==by 0x5BDC8E8: _PyLong_New (longobject.c:76) > ==7883==by 0x5BDC886: PyLong_FromLong (longobject.c:129) > ==7883==by 0x4E70E02: qd_register_constant (python_embedded.c:706) > ==7883==by 0x4E71D88: qd_python_setup (python_embedded.c:757) > ==7883==by 0x4E71D88: qd_python_initialize (python_embedded.c:62) > ==7883==by 0x4E62C20: qd_dispatch (dispatch.c:88) > ==7883==by 0x4017D2: main_process (main.c:89) > ==7883==by 0x40163E: main (main.c:360) -- 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-1051) Python memory leak via PyLong_FromLong
[ https://issues.apache.org/jira/browse/DISPATCH-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523956#comment-16523956 ] ASF subversion and git services commented on DISPATCH-1051: --- Commit 7c8f3119918ffebc2e444e0b66d0505f4d83dcc8 in qpid-dispatch's branch refs/heads/master from Kenneth Giusti [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=7c8f311 ] DISPATCH-1051: remove extra incref of python long object > Python memory leak via PyLong_FromLong > -- > > Key: DISPATCH-1051 > URL: https://issues.apache.org/jira/browse/DISPATCH-1051 > Project: Qpid Dispatch > Issue Type: Bug >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Major > Fix For: 1.2.0 > > > ==7883== 24 bytes in 1 blocks are definitely lost in loss record 50 of 3,471 > ==7883==at 0x4C2CB6B: malloc (vg_replace_malloc.c:299) > ==7883==by 0x5BF0091: PyObject_Malloc (obmalloc.c:982) > ==7883==by 0x5BDC8E8: _PyLong_New (longobject.c:76) > ==7883==by 0x5BDC886: PyLong_FromLong (longobject.c:129) > ==7883==by 0x4E70E02: qd_register_constant (python_embedded.c:706) > ==7883==by 0x4E71D88: qd_python_setup (python_embedded.c:757) > ==7883==by 0x4E71D88: qd_python_initialize (python_embedded.c:62) > ==7883==by 0x4E62C20: qd_dispatch (dispatch.c:88) > ==7883==by 0x4017D2: main_process (main.c:89) > ==7883==by 0x40163E: main (main.c:360) -- 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-845) Allow connecting containers to declare their availability for link routes
[ https://issues.apache.org/jira/browse/DISPATCH-845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-845: -- Fix Version/s: (was: 1.2.0) Backlog > Allow connecting containers to declare their availability for link routes > - > > Key: DISPATCH-845 > URL: https://issues.apache.org/jira/browse/DISPATCH-845 > Project: Qpid Dispatch > Issue Type: New Feature > Components: Router Node >Reporter: Ted Ross >Assignee: Ted Ross >Priority: Major > Fix For: Backlog > > > In the case where a container wishes to connect to a router network and > accept incoming routed link attaches (i.e. become a destination for link > routes), it is now quite complicated to do so. First, the connected router > must be configured with a listener in the route-container role. Second, > there must be linkRoute objects configured for each prefix or pattern for the > connected container. > A more efficient mechanism for dynamic/ephemeral link routes can be supported > as follows: > * A container opening a connection to the router may provide a connection > property that contains a list of prefixes and/or patterns for link routes. > * During the lifecycle of that connection, the router maintains active > link-route addresses targeting that container. > This feature allows for lightweight establishment of link-route destinations > without the need for connection roles and configured link-routes with > independently managed lifecycles (active, inactive, etc.). -- 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-930) Edge Router mode for improved scale and efficiency
[ https://issues.apache.org/jira/browse/DISPATCH-930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Ross updated DISPATCH-930: -- Fix Version/s: (was: 1.2.0) Backlog > Edge Router mode for improved scale and efficiency > -- > > Key: DISPATCH-930 > URL: https://issues.apache.org/jira/browse/DISPATCH-930 > Project: Qpid Dispatch > Issue Type: New Feature > Components: Router Node >Reporter: Ted Ross >Assignee: Ted Ross >Priority: Major > Fix For: Backlog > > Attachments: EdgeRouter.pdf > > > Introduce a new router operating mode called "edge" that allows a router to > join a network with a single uplink to an "interior" router. Such routers > can be proliferated without limit and allow for greatly increased network > size. > -- 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-1051) Python memory leak via PyLong_FromLong
Ken Giusti created DISPATCH-1051: Summary: Python memory leak via PyLong_FromLong Key: DISPATCH-1051 URL: https://issues.apache.org/jira/browse/DISPATCH-1051 Project: Qpid Dispatch Issue Type: Bug Reporter: Ken Giusti Assignee: Ken Giusti Fix For: 1.2.0 ==7883== 24 bytes in 1 blocks are definitely lost in loss record 50 of 3,471 ==7883==at 0x4C2CB6B: malloc (vg_replace_malloc.c:299) ==7883==by 0x5BF0091: PyObject_Malloc (obmalloc.c:982) ==7883==by 0x5BDC8E8: _PyLong_New (longobject.c:76) ==7883==by 0x5BDC886: PyLong_FromLong (longobject.c:129) ==7883==by 0x4E70E02: qd_register_constant (python_embedded.c:706) ==7883==by 0x4E71D88: qd_python_setup (python_embedded.c:757) ==7883==by 0x4E71D88: qd_python_initialize (python_embedded.c:62) ==7883==by 0x4E62C20: qd_dispatch (dispatch.c:88) ==7883==by 0x4017D2: main_process (main.c:89) ==7883==by 0x40163E: main (main.c:360) -- 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-1871) Ruby leaks memory sending messages
[ https://issues.apache.org/jira/browse/PROTON-1871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523869#comment-16523869 ] Alan Conway commented on PROTON-1871: - FYI - some time ago I wrote a fluentd plugin based on proton: [https://github.com/ViaQ/docker-fluentd/tree/master/amqp_qpid] Just in case it is of interest, it has nothing to do with the bug you've reported. I'll investigate the memory leak, thanks for reporting it. > Ruby leaks memory sending messages > -- > > Key: PROTON-1871 > URL: https://issues.apache.org/jira/browse/PROTON-1871 > Project: Qpid Proton > Issue Type: Bug > Components: ruby-binding >Affects Versions: proton-c-0.23.0 >Reporter: roi costas >Assignee: Alan Conway >Priority: Major > Attachments: out_amq.rb, valgrind.txt > > > We have developed a simple fluentd output plugin which only sends messages to > AMQ. Sending messages with sender.send, memory increases continuously and it > is never released, not even when message processing is stopped. > The qpid-proton code is really simple and we have checked that it is > sender.send the one that leaks memory. > I have run memory_profiler, and the leak does not seem to by in ruby but in > C++ code because both the number of objects and bytes remain between constant > values. I have tried to debug it with valgrind but I cannot find the source > class of the leak. > I have attached the ruby code, ruby version 2.3.4. -- 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-1047) system_tests_ssl fail when running under python3 environment
[
https://issues.apache.org/jira/browse/DISPATCH-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti resolved DISPATCH-1047.
--
Resolution: Fixed
Fix Version/s: 1.2.0
> system_tests_ssl fail when running under python3 environment
>
>
> Key: DISPATCH-1047
> URL: https://issues.apache.org/jira/browse/DISPATCH-1047
> Project: Qpid Dispatch
> Issue Type: Bug
>Reporter: Ken Giusti
>Assignee: Ken Giusti
>Priority: Major
> Fix For: 1.2.0
>
> Attachments: Dockerfile-ctest
>
>
> Can be reproduced in attached dockerfile
> --
> Start 45: system_tests_ssl
> 45: Test command: /usr/bin/python
> "/main/qpid-dispatch-master/BUILD/tests/run.py" "-x" "unit2" "-v"
> "system_tests_ssl"
> 45: Test timeout computed to be: 1500
> 45: ERROR
> 45: ERROR
> 45:
> 45: ==
> 45: ERROR: setUpClass (system_tests_ssl.RouterTestSslClient)
> 45: --
> 45: Traceback (most recent call last):
> 45: File "/main/qpid-dispatch-master/tests/system_tests_ssl.py", line 105,
> in setUpClass
> 45: super(RouterTestSslClient, cls).create_sasl_files()
> 45: File "/main/qpid-dispatch-master/tests/system_tests_ssl.py", line 57,
> in create_sasl_files
> 45: result = pipe.communicate('password')
> 45: File "/usr/lib64/python3.6/subprocess.py", line 843, in communicate
> 45: stdout, stderr = self._communicate(input, endtime, timeout)
> 45: File "/usr/lib64/python3.6/subprocess.py", line 1499, in _communicate
> 45: input_view = memoryview(self._input)
> 45: TypeError: memoryview: a bytes-like object is required, not 'str'
> 45:
> 45: ==
> 45: ERROR: setUpClass (system_tests_ssl.RouterTestSslInterRouter)
> 45: --
> 45: Traceback (most recent call last):
> 45: File "/main/qpid-dispatch-master/tests/system_tests_ssl.py", line 410,
> in setUpClass
> 45: super(RouterTestSslInterRouter, cls).create_sasl_files()
> 45: File "/main/qpid-dispatch-master/tests/system_tests_ssl.py", line 57,
> in create_sasl_files
> 45: result = pipe.communicate('password')
> 45: File "/usr/lib64/python3.6/subprocess.py", line 843, in communicate
> 45: stdout, stderr = self._communicate(input, endtime, timeout)
> 45: File "/usr/lib64/python3.6/subprocess.py", line 1499, in _communicate
> 45: input_view = memoryview(self._input)
> 45: TypeError: memoryview: a bytes-like object is required, not 'str'
> 45:
> 45: --
> 45: Ran 0 tests in 0.005s
> 45:
> 45: FAILED (errors=2)
> 45/47 Test #45: system_tests_ssl ..***Failed
> 0.22
--
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-1048) system_tests_http fail when run under python3 environment
[ https://issues.apache.org/jira/browse/DISPATCH-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti resolved DISPATCH-1048. -- Resolution: Fixed Fix Version/s: 1.2.0 > system_tests_http fail when run under python3 environment > - > > Key: DISPATCH-1048 > URL: https://issues.apache.org/jira/browse/DISPATCH-1048 > Project: Qpid Dispatch > Issue Type: Bug >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Major > Fix For: 1.2.0 > > Attachments: Dockerfile-ctest > > > Can reproduce with attached docker file > - > Start 46: system_tests_http > 46: Test command: /usr/bin/python > "/main/qpid-dispatch-master/BUILD/tests/run.py" "-x" "unit2" "-v" > "system_tests_http" > 46: Test timeout computed to be: 1500 > 46: system_tests_http (unittest2.loader._FailedTest) ... ERROR > 46: > 46: == > 46: ERROR: system_tests_http (unittest2.loader._FailedTest) > 46: -- > 46: Traceback (most recent call last): > 46: ImportError: Failed to import test module: system_tests_http > 46: Traceback (most recent call last): > 46: File "/usr/lib/python3.6/site-packages/unittest2/loader.py", line 172, > in loadTestsFromName > 46: module = __import__(module_name) > 46: File "/main/qpid-dispatch-master/tests/system_tests_http.py", line 25, > in > 46: import os, threading, sys, urllib2 > 46: ModuleNotFoundError: No module named 'urllib2' > 46: > 46: > 46: -- > 46: Ran 1 test in 0.000s > 46: > 46: FAILED (errors=1) > 46/47 Test #46: system_tests_http .***Failed > 0.21 sec -- 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-1048) system_tests_http fail when run under python3 environment
[ https://issues.apache.org/jira/browse/DISPATCH-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523862#comment-16523862 ] ASF subversion and git services commented on DISPATCH-1048: --- Commit 7a6fa82335ba4d4d3024522e6736566224eaae5b in qpid-dispatch's branch refs/heads/master from Kenneth Giusti [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=7a6fa82 ] DISPATCH-1048: correct import for urllib in python3, use unicode. This closes #330 > system_tests_http fail when run under python3 environment > - > > Key: DISPATCH-1048 > URL: https://issues.apache.org/jira/browse/DISPATCH-1048 > Project: Qpid Dispatch > Issue Type: Bug >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Major > Attachments: Dockerfile-ctest > > > Can reproduce with attached docker file > - > Start 46: system_tests_http > 46: Test command: /usr/bin/python > "/main/qpid-dispatch-master/BUILD/tests/run.py" "-x" "unit2" "-v" > "system_tests_http" > 46: Test timeout computed to be: 1500 > 46: system_tests_http (unittest2.loader._FailedTest) ... ERROR > 46: > 46: == > 46: ERROR: system_tests_http (unittest2.loader._FailedTest) > 46: -- > 46: Traceback (most recent call last): > 46: ImportError: Failed to import test module: system_tests_http > 46: Traceback (most recent call last): > 46: File "/usr/lib/python3.6/site-packages/unittest2/loader.py", line 172, > in loadTestsFromName > 46: module = __import__(module_name) > 46: File "/main/qpid-dispatch-master/tests/system_tests_http.py", line 25, > in > 46: import os, threading, sys, urllib2 > 46: ModuleNotFoundError: No module named 'urllib2' > 46: > 46: > 46: -- > 46: Ran 1 test in 0.000s > 46: > 46: FAILED (errors=1) > 46/47 Test #46: system_tests_http .***Failed > 0.21 sec -- 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-1048) system_tests_http fail when run under python3 environment
[ https://issues.apache.org/jira/browse/DISPATCH-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523863#comment-16523863 ] ASF GitHub Bot commented on DISPATCH-1048: -- Github user asfgit closed the pull request at: https://github.com/apache/qpid-dispatch/pull/330 > system_tests_http fail when run under python3 environment > - > > Key: DISPATCH-1048 > URL: https://issues.apache.org/jira/browse/DISPATCH-1048 > Project: Qpid Dispatch > Issue Type: Bug >Reporter: Ken Giusti >Assignee: Ken Giusti >Priority: Major > Attachments: Dockerfile-ctest > > > Can reproduce with attached docker file > - > Start 46: system_tests_http > 46: Test command: /usr/bin/python > "/main/qpid-dispatch-master/BUILD/tests/run.py" "-x" "unit2" "-v" > "system_tests_http" > 46: Test timeout computed to be: 1500 > 46: system_tests_http (unittest2.loader._FailedTest) ... ERROR > 46: > 46: == > 46: ERROR: system_tests_http (unittest2.loader._FailedTest) > 46: -- > 46: Traceback (most recent call last): > 46: ImportError: Failed to import test module: system_tests_http > 46: Traceback (most recent call last): > 46: File "/usr/lib/python3.6/site-packages/unittest2/loader.py", line 172, > in loadTestsFromName > 46: module = __import__(module_name) > 46: File "/main/qpid-dispatch-master/tests/system_tests_http.py", line 25, > in > 46: import os, threading, sys, urllib2 > 46: ModuleNotFoundError: No module named 'urllib2' > 46: > 46: > 46: -- > 46: Ran 1 test in 0.000s > 46: > 46: FAILED (errors=1) > 46/47 Test #46: system_tests_http .***Failed > 0.21 sec -- 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 #330: DISPATCH-1048: correct import for urllib in...
Github user asfgit closed the pull request at: https://github.com/apache/qpid-dispatch/pull/330 --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (DISPATCH-1047) system_tests_ssl fail when running under python3 environment
[
https://issues.apache.org/jira/browse/DISPATCH-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523856#comment-16523856
]
ASF GitHub Bot commented on DISPATCH-1047:
--
Github user asfgit closed the pull request at:
https://github.com/apache/qpid-dispatch/pull/329
> system_tests_ssl fail when running under python3 environment
>
>
> Key: DISPATCH-1047
> URL: https://issues.apache.org/jira/browse/DISPATCH-1047
> Project: Qpid Dispatch
> Issue Type: Bug
>Reporter: Ken Giusti
>Assignee: Ken Giusti
>Priority: Major
> Attachments: Dockerfile-ctest
>
>
> Can be reproduced in attached dockerfile
> --
> Start 45: system_tests_ssl
> 45: Test command: /usr/bin/python
> "/main/qpid-dispatch-master/BUILD/tests/run.py" "-x" "unit2" "-v"
> "system_tests_ssl"
> 45: Test timeout computed to be: 1500
> 45: ERROR
> 45: ERROR
> 45:
> 45: ==
> 45: ERROR: setUpClass (system_tests_ssl.RouterTestSslClient)
> 45: --
> 45: Traceback (most recent call last):
> 45: File "/main/qpid-dispatch-master/tests/system_tests_ssl.py", line 105,
> in setUpClass
> 45: super(RouterTestSslClient, cls).create_sasl_files()
> 45: File "/main/qpid-dispatch-master/tests/system_tests_ssl.py", line 57,
> in create_sasl_files
> 45: result = pipe.communicate('password')
> 45: File "/usr/lib64/python3.6/subprocess.py", line 843, in communicate
> 45: stdout, stderr = self._communicate(input, endtime, timeout)
> 45: File "/usr/lib64/python3.6/subprocess.py", line 1499, in _communicate
> 45: input_view = memoryview(self._input)
> 45: TypeError: memoryview: a bytes-like object is required, not 'str'
> 45:
> 45: ==
> 45: ERROR: setUpClass (system_tests_ssl.RouterTestSslInterRouter)
> 45: --
> 45: Traceback (most recent call last):
> 45: File "/main/qpid-dispatch-master/tests/system_tests_ssl.py", line 410,
> in setUpClass
> 45: super(RouterTestSslInterRouter, cls).create_sasl_files()
> 45: File "/main/qpid-dispatch-master/tests/system_tests_ssl.py", line 57,
> in create_sasl_files
> 45: result = pipe.communicate('password')
> 45: File "/usr/lib64/python3.6/subprocess.py", line 843, in communicate
> 45: stdout, stderr = self._communicate(input, endtime, timeout)
> 45: File "/usr/lib64/python3.6/subprocess.py", line 1499, in _communicate
> 45: input_view = memoryview(self._input)
> 45: TypeError: memoryview: a bytes-like object is required, not 'str'
> 45:
> 45: --
> 45: Ran 0 tests in 0.005s
> 45:
> 45: FAILED (errors=2)
> 45/47 Test #45: system_tests_ssl ..***Failed
> 0.22
--
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-1047) system_tests_ssl fail when running under python3 environment
[
https://issues.apache.org/jira/browse/DISPATCH-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523855#comment-16523855
]
ASF subversion and git services commented on DISPATCH-1047:
---
Commit 13652ac4e4bd724ce9a9278611a9e219071f5896 in qpid-dispatch's branch
refs/heads/master from Kenneth Giusti
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=13652ac ]
DISPATCH-1047: open the pipe to saslpasswd2 in text mode. This closes #329
> system_tests_ssl fail when running under python3 environment
>
>
> Key: DISPATCH-1047
> URL: https://issues.apache.org/jira/browse/DISPATCH-1047
> Project: Qpid Dispatch
> Issue Type: Bug
>Reporter: Ken Giusti
>Assignee: Ken Giusti
>Priority: Major
> Attachments: Dockerfile-ctest
>
>
> Can be reproduced in attached dockerfile
> --
> Start 45: system_tests_ssl
> 45: Test command: /usr/bin/python
> "/main/qpid-dispatch-master/BUILD/tests/run.py" "-x" "unit2" "-v"
> "system_tests_ssl"
> 45: Test timeout computed to be: 1500
> 45: ERROR
> 45: ERROR
> 45:
> 45: ==
> 45: ERROR: setUpClass (system_tests_ssl.RouterTestSslClient)
> 45: --
> 45: Traceback (most recent call last):
> 45: File "/main/qpid-dispatch-master/tests/system_tests_ssl.py", line 105,
> in setUpClass
> 45: super(RouterTestSslClient, cls).create_sasl_files()
> 45: File "/main/qpid-dispatch-master/tests/system_tests_ssl.py", line 57,
> in create_sasl_files
> 45: result = pipe.communicate('password')
> 45: File "/usr/lib64/python3.6/subprocess.py", line 843, in communicate
> 45: stdout, stderr = self._communicate(input, endtime, timeout)
> 45: File "/usr/lib64/python3.6/subprocess.py", line 1499, in _communicate
> 45: input_view = memoryview(self._input)
> 45: TypeError: memoryview: a bytes-like object is required, not 'str'
> 45:
> 45: ==
> 45: ERROR: setUpClass (system_tests_ssl.RouterTestSslInterRouter)
> 45: --
> 45: Traceback (most recent call last):
> 45: File "/main/qpid-dispatch-master/tests/system_tests_ssl.py", line 410,
> in setUpClass
> 45: super(RouterTestSslInterRouter, cls).create_sasl_files()
> 45: File "/main/qpid-dispatch-master/tests/system_tests_ssl.py", line 57,
> in create_sasl_files
> 45: result = pipe.communicate('password')
> 45: File "/usr/lib64/python3.6/subprocess.py", line 843, in communicate
> 45: stdout, stderr = self._communicate(input, endtime, timeout)
> 45: File "/usr/lib64/python3.6/subprocess.py", line 1499, in _communicate
> 45: input_view = memoryview(self._input)
> 45: TypeError: memoryview: a bytes-like object is required, not 'str'
> 45:
> 45: --
> 45: Ran 0 tests in 0.005s
> 45:
> 45: FAILED (errors=2)
> 45/47 Test #45: system_tests_ssl ..***Failed
> 0.22
--
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 #329: DISPATCH-1047: open the pipe to saslpasswd2...
Github user asfgit closed the pull request at: https://github.com/apache/qpid-dispatch/pull/329 --- - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Closed] (PROTON-1849) [c] server behaves incorrectly on duplicate link attach
[
https://issues.apache.org/jira/browse/PROTON-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell closed PROTON-1849.
--
Resolution: Duplicate
Removed fix-version since it was closed as a duplicate of something that is
still open, and without any changes.
> [c] server behaves incorrectly on duplicate link attach
> ---
>
> Key: PROTON-1849
> URL: https://issues.apache.org/jira/browse/PROTON-1849
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Affects Versions: proton-c-0.22.0
>Reporter: Alan Conway
>Assignee: Alan Conway
>Priority: Minor
>
> --The fix for
> PROTON-1832: [c] reject duplicate link attach with connection error.
> Is incorrect. It raises a transport eror on duplicate link names. That is
> better than crashing but the AMQP spec says:
>
> {quote}2.6.1 Naming A Link
> [snip]
> A link's name uniquely identifies the link from the container of the source
> to the container of the target node, i.e., if the container of the source
> node is A, and the container of the target node is B, the link can be
> globally identified by the (ordered) tuple _(A,B,)_. Consequently, a
> link can only be active in one connection at a time. If an attempt is made to
> attach the link subsequently when it is not suspended, then the link can be
> 'stolen', i.e., the second attach succeeds and the first attach MUST then be
> closed with a link error of
> [stolen|http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-transport-v1.0-os.html#choice-link-error-stolen].
> This behavior ensures that in the event of a connection failure occurring
> and being noticed by one party, that re-establishment has the desired effect.
> {quote}
> The spec is anticipating duplicate names being used on *different*
> connections during reconnect but we should treat duplicates on the same
> connection the same way. In particular proton should dispatch the events to
> close the stolen link *before* the events that open the new link.
> On the client side, a duplicate link attach will cause the original link to
> be closed with a STOLEN error, then open the new link. The events and
> protocol frames will show the close/STOLEN first, then the open.
> This is more consistent with the spec, and more forgiving than closing the
> connection with an error. It means intermediaries that just forward link
> traffic will do the right thing automatically on an upstream reconnect (close
> and re-open the downstream link) even if they don't locally check for link
> name duplication.
--
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] (PROTON-1849) [c] server behaves incorrectly on duplicate link attach
[
https://issues.apache.org/jira/browse/PROTON-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell reopened PROTON-1849:
> [c] server behaves incorrectly on duplicate link attach
> ---
>
> Key: PROTON-1849
> URL: https://issues.apache.org/jira/browse/PROTON-1849
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Affects Versions: proton-c-0.22.0
>Reporter: Alan Conway
>Assignee: Alan Conway
>Priority: Minor
>
> --The fix for
> PROTON-1832: [c] reject duplicate link attach with connection error.
> Is incorrect. It raises a transport eror on duplicate link names. That is
> better than crashing but the AMQP spec says:
>
> {quote}2.6.1 Naming A Link
> [snip]
> A link's name uniquely identifies the link from the container of the source
> to the container of the target node, i.e., if the container of the source
> node is A, and the container of the target node is B, the link can be
> globally identified by the (ordered) tuple _(A,B,)_. Consequently, a
> link can only be active in one connection at a time. If an attempt is made to
> attach the link subsequently when it is not suspended, then the link can be
> 'stolen', i.e., the second attach succeeds and the first attach MUST then be
> closed with a link error of
> [stolen|http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-transport-v1.0-os.html#choice-link-error-stolen].
> This behavior ensures that in the event of a connection failure occurring
> and being noticed by one party, that re-establishment has the desired effect.
> {quote}
> The spec is anticipating duplicate names being used on *different*
> connections during reconnect but we should treat duplicates on the same
> connection the same way. In particular proton should dispatch the events to
> close the stolen link *before* the events that open the new link.
> On the client side, a duplicate link attach will cause the original link to
> be closed with a STOLEN error, then open the new link. The events and
> protocol frames will show the close/STOLEN first, then the open.
> This is more consistent with the spec, and more forgiving than closing the
> connection with an error. It means intermediaries that just forward link
> traffic will do the right thing automatically on an upstream reconnect (close
> and re-open the downstream link) even if they don't locally check for link
> name duplication.
--
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-1849) [c] server behaves incorrectly on duplicate link attach
[
https://issues.apache.org/jira/browse/PROTON-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated PROTON-1849:
---
Fix Version/s: (was: proton-c-0.24.0)
> [c] server behaves incorrectly on duplicate link attach
> ---
>
> Key: PROTON-1849
> URL: https://issues.apache.org/jira/browse/PROTON-1849
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Affects Versions: proton-c-0.22.0
>Reporter: Alan Conway
>Assignee: Alan Conway
>Priority: Minor
>
> --The fix for
> PROTON-1832: [c] reject duplicate link attach with connection error.
> Is incorrect. It raises a transport eror on duplicate link names. That is
> better than crashing but the AMQP spec says:
>
> {quote}2.6.1 Naming A Link
> [snip]
> A link's name uniquely identifies the link from the container of the source
> to the container of the target node, i.e., if the container of the source
> node is A, and the container of the target node is B, the link can be
> globally identified by the (ordered) tuple _(A,B,)_. Consequently, a
> link can only be active in one connection at a time. If an attempt is made to
> attach the link subsequently when it is not suspended, then the link can be
> 'stolen', i.e., the second attach succeeds and the first attach MUST then be
> closed with a link error of
> [stolen|http://docs.oasis-open.org/amqp/core/v1.0/os/amqp-core-transport-v1.0-os.html#choice-link-error-stolen].
> This behavior ensures that in the event of a connection failure occurring
> and being noticed by one party, that re-establishment has the desired effect.
> {quote}
> The spec is anticipating duplicate names being used on *different*
> connections during reconnect but we should treat duplicates on the same
> connection the same way. In particular proton should dispatch the events to
> close the stolen link *before* the events that open the new link.
> On the client side, a duplicate link attach will cause the original link to
> be closed with a STOLEN error, then open the new link. The events and
> protocol frames will show the close/STOLEN first, then the open.
> This is more consistent with the spec, and more forgiving than closing the
> connection with an error. It means intermediaries that just forward link
> traffic will do the right thing automatically on an upstream reconnect (close
> and re-open the downstream link) even if they don't locally check for link
> name duplication.
--
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] (QPIDIT-39) Make qpid-jms-client version a parameter of Maven build
[
https://issues.apache.org/jira/browse/QPIDIT-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated QPIDIT-39:
-
Fix Version/s: 0.1.0
> Make qpid-jms-client version a parameter of Maven build
> ---
>
> Key: QPIDIT-39
> URL: https://issues.apache.org/jira/browse/QPIDIT-39
> Project: Apache QPID Interoperability Test Suite
> Issue Type: Improvement
> Components: Qpid Jms Shim
>Affects Versions: 0.1.0
>Reporter: Jiri Daněk
>Assignee: Kim van der Riet
>Priority: Critical
> Fix For: 0.1.0
>
>
> I wish to be able to change the version of qpid-jms-client library used in
> the jms shim. This would allow running the test with older versions of the
> library and also with various proprietary builds of the library.
> One possible way to implement this would be to make the library version a
> maven attribute and to switch between geronimo-jms_1.1_spec and the 2.0
> version using maven profile, e.g.:
> {noformat}
> mvn -Pjms11 -Dqpid-jms-client.version=0.11.0.mycompany-1 package
> mvn -Pjms20 -Dqpid-jms-client.version=0.20.0 package
> {noformat}
> On a related task, it might be helpful to use Maven to produce an uberjar, a
> jar that bundles all runtime dependencies in itself. It would simplify
> running the shim from the test program, because then there would be no
> classpath to deal with.
--
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-1049) Add console tests
[ https://issues.apache.org/jira/browse/DISPATCH-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Allen resolved DISPATCH-1049. Resolution: Fixed Fix Version/s: 1.2.0 > Add console tests > - > > Key: DISPATCH-1049 > URL: https://issues.apache.org/jira/browse/DISPATCH-1049 > Project: Qpid Dispatch > Issue Type: Improvement > Components: Console >Affects Versions: 1.1.0 >Reporter: Ernest Allen >Assignee: Ernest Allen >Priority: Major > Fix For: 1.2.0 > > > Add tests for the console's javascript code to the test system. -- 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] (QPIDIT-39) Make qpid-jms-client version a parameter of Maven build
[
https://issues.apache.org/jira/browse/QPIDIT-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell closed QPIDIT-39.
Resolution: Fixed
> Make qpid-jms-client version a parameter of Maven build
> ---
>
> Key: QPIDIT-39
> URL: https://issues.apache.org/jira/browse/QPIDIT-39
> Project: Apache QPID Interoperability Test Suite
> Issue Type: Improvement
> Components: Qpid Jms Shim
>Affects Versions: 0.1.0
>Reporter: Jiri Daněk
>Assignee: Kim van der Riet
>Priority: Critical
> Fix For: 0.1.0
>
>
> I wish to be able to change the version of qpid-jms-client library used in
> the jms shim. This would allow running the test with older versions of the
> library and also with various proprietary builds of the library.
> One possible way to implement this would be to make the library version a
> maven attribute and to switch between geronimo-jms_1.1_spec and the 2.0
> version using maven profile, e.g.:
> {noformat}
> mvn -Pjms11 -Dqpid-jms-client.version=0.11.0.mycompany-1 package
> mvn -Pjms20 -Dqpid-jms-client.version=0.20.0 package
> {noformat}
> On a related task, it might be helpful to use Maven to produce an uberjar, a
> jar that bundles all runtime dependencies in itself. It would simplify
> running the shim from the test program, because then there would be no
> classpath to deal with.
--
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] (QPIDIT-125) Release QIT 0.2.0
[ https://issues.apache.org/jira/browse/QPIDIT-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523821#comment-16523821 ] ASF subversion and git services commented on QPIDIT-125: Commit 3e97487cb0f1417dd9eef1614b593b7963db7ba5 in qpid-interop-test's branch refs/heads/0.2.0 from [~kpvdr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-interop-test.git;h=3e97487 ] QPIDIT-125: Removed further AMQP nulls from test as PROTON-1815 has not yet made it into the current releases of Proton. > Release QIT 0.2.0 > - > > Key: QPIDIT-125 > URL: https://issues.apache.org/jira/browse/QPIDIT-125 > Project: Apache QPID Interoperability Test Suite > Issue Type: Task >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.2.0 > > > Update docs, create branches, tags, etc. for the release of Qpid Interop Test > v. 0.2.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] [Updated] (PROTON-1873) 0.25.0 release tasks
[ https://issues.apache.org/jira/browse/PROTON-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-1873: --- Fix Version/s: (was: proton-c-0.24.0) proton-c-0.25.0 > 0.25.0 release tasks > > > Key: PROTON-1873 > URL: https://issues.apache.org/jira/browse/PROTON-1873 > Project: Qpid Proton > Issue Type: Task > Components: proton-c, release >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: proton-c-0.25.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] [Commented] (PROTON-1852) 0.24.0 release tasks
[ https://issues.apache.org/jira/browse/PROTON-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523806#comment-16523806 ] ASF subversion and git services commented on PROTON-1852: - Commit a7243b2e7928db2dce55c8db9f1ee67d931ca187 in qpid-proton's branch refs/heads/master from [~gemmellr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=a7243b2 ] PROTON-1852: update versions for 0.24.0-rc1 > 0.24.0 release tasks > > > Key: PROTON-1852 > URL: https://issues.apache.org/jira/browse/PROTON-1852 > Project: Qpid Proton > Issue Type: Task > Components: proton-c, release >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: proton-c-0.24.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] [Commented] (PROTON-1852) 0.24.0 release tasks
[ https://issues.apache.org/jira/browse/PROTON-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523807#comment-16523807 ] ASF subversion and git services commented on PROTON-1852: - Commit 138cadfebea781b6732038c427f44860f70c68d7 in qpid-proton's branch refs/heads/master from [~gemmellr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=138cadf ] PROTON-1852, PROTON-1873: update versions for 0.25.0-SNAPSHOT > 0.24.0 release tasks > > > Key: PROTON-1852 > URL: https://issues.apache.org/jira/browse/PROTON-1852 > Project: Qpid Proton > Issue Type: Task > Components: proton-c, release >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: proton-c-0.24.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] [Commented] (PROTON-1873) 0.25.0 release tasks
[ https://issues.apache.org/jira/browse/PROTON-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523808#comment-16523808 ] ASF subversion and git services commented on PROTON-1873: - Commit 138cadfebea781b6732038c427f44860f70c68d7 in qpid-proton's branch refs/heads/master from [~gemmellr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=138cadf ] PROTON-1852, PROTON-1873: update versions for 0.25.0-SNAPSHOT > 0.25.0 release tasks > > > Key: PROTON-1873 > URL: https://issues.apache.org/jira/browse/PROTON-1873 > Project: Qpid Proton > Issue Type: Task > Components: proton-c, release >Reporter: Robbie Gemmell >Assignee: Robbie Gemmell >Priority: Major > Fix For: proton-c-0.24.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] [Commented] (QPIDIT-125) Release QIT 0.2.0
[ https://issues.apache.org/jira/browse/QPIDIT-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523804#comment-16523804 ] ASF subversion and git services commented on QPIDIT-125: Commit ce135112c19e70c8980fee21c6c84101eb9f6b22 in qpid-interop-test's branch refs/heads/0.2.0 from [~kpvdr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-interop-test.git;h=ce13511 ] QPIDIT-125: Removed further AMQP nulls from test as PROTON-1815 has not yet made it into the current releases of Proton. > Release QIT 0.2.0 > - > > Key: QPIDIT-125 > URL: https://issues.apache.org/jira/browse/QPIDIT-125 > Project: Apache QPID Interoperability Test Suite > Issue Type: Task >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.2.0 > > > Update docs, create branches, tags, etc. for the release of Qpid Interop Test > v. 0.2.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] [Commented] (PROTON-1852) 0.24.0 release tasks
[
https://issues.apache.org/jira/browse/PROTON-1852?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523797#comment-16523797
]
Robbie Gemmell commented on PROTON-1852:
[http://git-wip-us.apache.org/repos/asf/qpid-proton/commit/b1b8322b]
{noformat}
PROTON-1852: Update SO versions after ABI change review
Commit: b1b8322b2f8f29653c8970aad5d37b3b22c56923
Committer: Justin Ross
Committed: Thu Jun 21 16:36:31 2018 -0700
{noformat}
> 0.24.0 release tasks
>
>
> Key: PROTON-1852
> URL: https://issues.apache.org/jira/browse/PROTON-1852
> Project: Qpid Proton
> Issue Type: Task
> Components: proton-c, release
>Reporter: Robbie Gemmell
>Assignee: Robbie Gemmell
>Priority: Major
> Fix For: proton-c-0.24.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-1869) [Python] Compiler conversion warnings with Win64 builds
[ https://issues.apache.org/jira/browse/PROTON-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-1869. - Resolution: Fixed > [Python] Compiler conversion warnings with Win64 builds > --- > > Key: PROTON-1869 > URL: https://issues.apache.org/jira/browse/PROTON-1869 > Project: Qpid Proton > Issue Type: Improvement > Components: python-binding >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.24.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-1868) [Python] pn_handle_t binding does not reliably work with Win64
[ https://issues.apache.org/jira/browse/PROTON-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-1868. - Resolution: Fixed > [Python] pn_handle_t binding does not reliably work with Win64 > -- > > Key: PROTON-1868 > URL: https://issues.apache.org/jira/browse/PROTON-1868 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding, ruby-binding >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.24.0 > > > pn_handle_t is treated by swig as identical to uintptr_t which is defined as > unsigned long. However under Win64 this is a 32 bit int which is not long > enough to fit all 64 bit addresses. > The swig code should be changed to either define uintptr_t as unsigned long > long for 64 bit builds which is always 64 bits (on all platforms). > Or we should use a custom typemap for pn_handle_t which uses PyLong_AsVoidPtr > & PyLong_FromVoidPtr. -- 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] (QPIDIT-125) Release QIT 0.2.0
[ https://issues.apache.org/jira/browse/QPIDIT-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523778#comment-16523778 ] Robbie Gemmell commented on QPIDIT-125: --- In what sense has "PROTON-1815 has not yet made it into the current releases of Proton."? As far as I see it was released in Proton 0.23.0 a month ago? > Release QIT 0.2.0 > - > > Key: QPIDIT-125 > URL: https://issues.apache.org/jira/browse/QPIDIT-125 > Project: Apache QPID Interoperability Test Suite > Issue Type: Task >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.2.0 > > > Update docs, create branches, tags, etc. for the release of Qpid Interop Test > v. 0.2.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] [Deleted] (PROTON-1872) Release QIT 0.2.0
[ https://issues.apache.org/jira/browse/PROTON-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell deleted PROTON-1872: --- > Release QIT 0.2.0 > - > > Key: PROTON-1872 > URL: https://issues.apache.org/jira/browse/PROTON-1872 > Project: Qpid Proton > Issue Type: Task >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > > Update docs, create branches, tags, etc for the release of 0.2.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] [Commented] (QPIDIT-125) Release QIT 0.2.0
[ https://issues.apache.org/jira/browse/QPIDIT-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523759#comment-16523759 ] ASF subversion and git services commented on QPIDIT-125: Commit 5eb9374c9416a9ce7054004674af3354af07db87 in qpid-interop-test's branch refs/heads/0.2.0 from [~kpvdr] [ https://git-wip-us.apache.org/repos/asf?p=qpid-interop-test.git;h=5eb9374 ] QPIDIT-125: Created 0.2.0 branch, removed AMQP nulls from test as PROTON-1815 has not yet made it into the current releases of Proton. > Release QIT 0.2.0 > - > > Key: QPIDIT-125 > URL: https://issues.apache.org/jira/browse/QPIDIT-125 > Project: Apache QPID Interoperability Test Suite > Issue Type: Task >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.2.0 > > > Update docs, create branches, tags, etc. for the release of Qpid Interop Test > v. 0.2.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] [Updated] (QPIDIT-125) Release QIT 0.2.0
[ https://issues.apache.org/jira/browse/QPIDIT-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet updated QPIDIT-125: Fix Version/s: 0.2.0 > Release QIT 0.2.0 > - > > Key: QPIDIT-125 > URL: https://issues.apache.org/jira/browse/QPIDIT-125 > Project: Apache QPID Interoperability Test Suite > Issue Type: Task >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > Fix For: 0.2.0 > > > Update docs, create branches, tags, etc. for the release of Qpid Interop Test > v. 0.2.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] [Created] (QPIDIT-125) Release QIT 0.2.0
Kim van der Riet created QPIDIT-125: --- Summary: Release QIT 0.2.0 Key: QPIDIT-125 URL: https://issues.apache.org/jira/browse/QPIDIT-125 Project: Apache QPID Interoperability Test Suite Issue Type: Task Reporter: Kim van der Riet Assignee: Kim van der Riet Update docs, create branches, tags, etc. for the release of Qpid Interop Test v. 0.2.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] [Created] (PROTON-1872) Release QIT 0.2.0
Kim van der Riet created PROTON-1872: Summary: Release QIT 0.2.0 Key: PROTON-1872 URL: https://issues.apache.org/jira/browse/PROTON-1872 Project: Qpid Proton Issue Type: Task Reporter: Kim van der Riet Assignee: Kim van der Riet Update docs, create branches, tags, etc for the release of 0.2.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] [Closed] (PROTON-1872) Release QIT 0.2.0
[ https://issues.apache.org/jira/browse/PROTON-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet closed PROTON-1872. Resolution: Invalid Opened under incorrect project > Release QIT 0.2.0 > - > > Key: PROTON-1872 > URL: https://issues.apache.org/jira/browse/PROTON-1872 > Project: Qpid Proton > Issue Type: Task >Reporter: Kim van der Riet >Assignee: Kim van der Riet >Priority: Major > > Update docs, create branches, tags, etc for the release of 0.2.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] [Updated] (PROTON-1871) Ruby leaks memory sending messages
[ https://issues.apache.org/jira/browse/PROTON-1871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] roi costas updated PROTON-1871: --- Attachment: valgrind.txt > Ruby leaks memory sending messages > -- > > Key: PROTON-1871 > URL: https://issues.apache.org/jira/browse/PROTON-1871 > Project: Qpid Proton > Issue Type: Bug > Components: ruby-binding >Affects Versions: proton-c-0.23.0 >Reporter: roi costas >Assignee: Alan Conway >Priority: Major > Attachments: out_amq.rb, valgrind.txt > > > We have developed a simple fluentd output plugin which only sends messages to > AMQ. Sending messages with sender.send, memory increases continuously and it > is never released, not even when message processing is stopped. > The qpid-proton code is really simple and we have checked that it is > sender.send the one that leaks memory. > I have run memory_profiler, and the leak does not seem to by in ruby but in > C++ code because both the number of objects and bytes remain between constant > values. I have tried to debug it with valgrind but I cannot find the source > class of the leak. > I have attached the ruby code, ruby version 2.3.4. -- 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-1871) Ruby leaks memory sending messages
[ https://issues.apache.org/jira/browse/PROTON-1871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] roi costas updated PROTON-1871: --- Description: We have developed a simple fluentd output plugin which only sends messages to AMQ. Sending messages with sender.send, memory increases continuously and it is never released, not even when message processing is stopped. The qpid-proton code is really simple and we have checked that it is sender.send the one that leaks memory. I have run memory_profiler, and the leak does not seem to by in ruby but in C++ code because both the number of objects and bytes remain between constant values. I have tried to debug it with valgrind but I cannot find the source class of the leak. I have attached the ruby code, ruby version 2.3.4. was: We have developed a simple fluentd output plugin which only sends messages to AMQ. Sending messages with sender.send, memory increases continuously and it is never released, not even when message processing is stopped. The qpid-proton code is really simple and we have checked that it is sender.send the one that leaks memory. I have attached the code. > Ruby leaks memory sending messages > -- > > Key: PROTON-1871 > URL: https://issues.apache.org/jira/browse/PROTON-1871 > Project: Qpid Proton > Issue Type: Bug > Components: ruby-binding >Affects Versions: proton-c-0.23.0 >Reporter: roi costas >Assignee: Alan Conway >Priority: Major > Attachments: out_amq.rb > > > We have developed a simple fluentd output plugin which only sends messages to > AMQ. Sending messages with sender.send, memory increases continuously and it > is never released, not even when message processing is stopped. > The qpid-proton code is really simple and we have checked that it is > sender.send the one that leaks memory. > I have run memory_profiler, and the leak does not seem to by in ruby but in > C++ code because both the number of objects and bytes remain between constant > values. I have tried to debug it with valgrind but I cannot find the source > class of the leak. > I have attached the ruby code, ruby version 2.3.4. -- 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-1871) Ruby leaks memory sending messages
roi costas created PROTON-1871: -- Summary: Ruby leaks memory sending messages Key: PROTON-1871 URL: https://issues.apache.org/jira/browse/PROTON-1871 Project: Qpid Proton Issue Type: Bug Components: ruby-binding Affects Versions: proton-c-0.23.0 Reporter: roi costas Assignee: Alan Conway Attachments: out_amq.rb We have developed a simple fluentd output plugin which only sends messages to AMQ. Sending messages with sender.send, memory increases continuously and it is never released, not even when message processing is stopped. The qpid-proton code is really simple and we have checked that it is sender.send the one that leaks memory. I have attached the 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-1050) sasl delegation plugin should set SNI to match auth address
[ https://issues.apache.org/jira/browse/DISPATCH-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved DISPATCH-1050. -- Resolution: Fixed > sasl delegation plugin should set SNI to match auth address > --- > > Key: DISPATCH-1050 > URL: https://issues.apache.org/jira/browse/DISPATCH-1050 > Project: Qpid Dispatch > Issue Type: Bug >Reporter: Gordon Sim >Assignee: Gordon Sim >Priority: Major > Fix For: 1.2.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] [Commented] (DISPATCH-1050) sasl delegation plugin should set SNI to match auth address
[ https://issues.apache.org/jira/browse/DISPATCH-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523552#comment-16523552 ] ASF subversion and git services commented on DISPATCH-1050: --- Commit b07d9461a4d4e8187966b336e1a155bdae3b3bb1 in qpid-dispatch's branch refs/heads/master from Gordon Sim [ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=b07d946 ] DISPATCH-1050: set SNI correctly for authservice > sasl delegation plugin should set SNI to match auth address > --- > > Key: DISPATCH-1050 > URL: https://issues.apache.org/jira/browse/DISPATCH-1050 > Project: Qpid Dispatch > Issue Type: Bug >Reporter: Gordon Sim >Assignee: Gordon Sim >Priority: Major > Fix For: 1.2.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] [Updated] (PROTON-1870) better logging for ssl
[ https://issues.apache.org/jira/browse/PROTON-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Ross updated PROTON-1870: Labels: logging (was: ) > better logging for ssl > -- > > Key: PROTON-1870 > URL: https://issues.apache.org/jira/browse/PROTON-1870 > Project: Qpid Proton > Issue Type: Improvement >Reporter: Gordon Sim >Priority: Major > Labels: logging > > Would be nice to have better logging for ssl connections, particularly where > they fail, e.g. the sni used, the ca the peer cert is signed with etc -- 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-1870) better logging for ssl
Gordon Sim created PROTON-1870: -- Summary: better logging for ssl Key: PROTON-1870 URL: https://issues.apache.org/jira/browse/PROTON-1870 Project: Qpid Proton Issue Type: Improvement Reporter: Gordon Sim Would be nice to have better logging for ssl connections, particularly where they fail, e.g. the sni used, the ca the peer cert is signed with etc -- 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-1050) sasl delegation plugin should set SNI to match auth address
Gordon Sim created DISPATCH-1050: Summary: sasl delegation plugin should set SNI to match auth address Key: DISPATCH-1050 URL: https://issues.apache.org/jira/browse/DISPATCH-1050 Project: Qpid Dispatch Issue Type: Bug Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 1.2.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] [Commented] (QPID-8212) [JMS AMQP 0-x][AMQP 0-8..0-91] Consumer close can block for 60 seconds and endup in time-out exception
[
https://issues.apache.org/jira/browse/QPID-8212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16523529#comment-16523529
]
ASF subversion and git services commented on QPID-8212:
---
Commit 22a4c4fc28f32e715d3852e303a2ed00e6770c44 in qpid-jms-amqp-0-x's branch
refs/heads/master from [~alex.rufous]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-jms-amqp-0-x.git;h=22a4c4f ]
QPID-8212: [JMS AMQP 0-x][AMQP 0-8..0-91] Make sure that consumer close does
not delay concurrent connection close
> [JMS AMQP 0-x][AMQP 0-8..0-91] Consumer close can block for 60 seconds and
> endup in time-out exception
> --
>
> Key: QPID-8212
> URL: https://issues.apache.org/jira/browse/QPID-8212
> Project: Qpid
> Issue Type: Bug
> Components: JMS AMQP 0-x
>Affects Versions: qpid-java-client-0-x-6.3.1
>Reporter: Alex Rudyy
>Priority: Blocker
> Fix For: qpid-java-client-0-x-6.3.2
>
>
> When method {{MessageConsumer#close()}} is invoked in one thread and method
> {{Connection#close()}} is invoked in another thread, the incoming
> {{BasicCancelOk}} frame can be ignored due to {{Connection#_closed}} flag
> being set. As result, the call to {{MessageConsumer#close()}} can block for
> 60 seconds and end up in exception due to not being able to receive
> {{BasicCancelOk}}. Invocation of {{Connection#close()}} also gets blocked
> due to message delivery lock being hold on consumer close.
> The defect was introduced as part of changes made against QPID-8185 in commit
> [f89f6c2f45d11fc63551d0d61c17eceedd6bd247|https://git-wip-us.apache.org/repos/asf?p=qpid-jms-amqp-0-x.git;h=f89f6c2]
> Method {{AMQProtocolSession#isClosedForInput}} checks whether session is
> closed for input by calling {{AMQSession#isClosed()}}. The latter returns
> true when either {{AMQSession#_closed}} or {{AMQConnection#_closed}} holds
> {{true}}. Only {{AMQSession#_closed}} should be checked in
> {{AMQProtocolSession#isClosedForInput}}.
--
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-7720) Java client hangs when publishing to C++ broker queue with flow control activated
[ https://issues.apache.org/jira/browse/QPID-7720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-7720: - Component/s: (was: Java Common) JMS AMQP 0-x > Java client hangs when publishing to C++ broker queue with flow control > activated > - > > Key: QPID-7720 > URL: https://issues.apache.org/jira/browse/QPID-7720 > Project: Qpid > Issue Type: Bug > Components: JMS AMQP 0-x >Affects Versions: qpid-java-6.1.1 >Reporter: Flavio Baronti >Priority: Major > Attachments: QPID-7720.patch > > > This is probably the same as QPID-4073. > When a C++ flow controlled queue is overfull, the broker stops sending > acknowledgements to client commands. This causes the internal command queue > of the client to become full. > In this situation, the client sends a flush request, then waits for the > internal queue to free some space. Unfortunately, the broker will answer to > the flush request with an empty response, and will not send anything else > when the queue becomes underfull again. Thus the client dies with a timeout. > I suggest a patch which sends again the flush command every 500ms, up to the > configured timeout. If the queue becomes underfull within the timeout, the > broker will answer with a non-empty response, and the client will restart > processing. -- 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
