[jira] [Commented] (PROTON-1781) [c-proactor] fix mis-named netaddr functions

[ https://issues.apache.org/jira/browse/PROTON-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16388061#comment-16388061 ] Alan Conway commented on PROTON-1781: - commit 06c3d6e2f46811038853b95401cd017cb21e2713

[jira] [Resolved] (PROTON-1781) [c-proactor] fix mis-named netaddr functions

[ https://issues.apache.org/jira/browse/PROTON-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1781. - Resolution: Fixed > [c-proactor] fix mis-named netaddr functions >

[jira] [Created] (PROTON-1784) [ruby] Connection#each_sender each_receiver should take a block

Alan Conway created PROTON-1784: --- Summary: [ruby] Connection#each_sender each_receiver should take a block Key: PROTON-1784 URL: https://issues.apache.org/jira/browse/PROTON-1784 Project: Qpid Proton

[jira] [Updated] (PROTON-1782) [ruby] implement for scheduled tasks and heartbeats

[ https://issues.apache.org/jira/browse/PROTON-1782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated PROTON-1782: Affects Version/s: proton-c-0.21.0 > [ruby] implement for scheduled tasks and heartbeats >

[jira] [Updated] (PROTON-1782) [ruby] implement for scheduled tasks and heartbeats

[ https://issues.apache.org/jira/browse/PROTON-1782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated PROTON-1782: Component/s: ruby-binding > [ruby] implement for scheduled tasks and heartbeats >

[jira] [Created] (PROTON-1781) [c-proactor] fix mis-named netaddr functions

Alan Conway created PROTON-1781: --- Summary: [c-proactor] fix mis-named netaddr functions Key: PROTON-1781 URL: https://issues.apache.org/jira/browse/PROTON-1781 Project: Qpid Proton Issue

[jira] [Resolved] (PROTON-1696) Go test of anonymous SASL fails if it can't find saslpasswd2

[ https://issues.apache.org/jira/browse/PROTON-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1696. - Resolution: Fixed Fix Version/s: proton-c-0.22.0 > Go test of anonymous SASL fails if it

[jira] [Created] (PROTON-1778) [ruby] support for user threads communicating with proton threads

Alan Conway created PROTON-1778: --- Summary: [ruby] support for user threads communicating with proton threads Key: PROTON-1778 URL: https://issues.apache.org/jira/browse/PROTON-1778 Project: Qpid Proton

[jira] [Updated] (PROTON-1615) c++: container leaks if exception thrown by handler.

[ https://issues.apache.org/jira/browse/PROTON-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated PROTON-1615: Fix Version/s: proton-c-0.22.0 > c++: container leaks if exception thrown by handler. >

[jira] [Updated] (PROTON-1592) [proton-python] accessing properties of event.receiver in on_link_opened throws exception

[ https://issues.apache.org/jira/browse/PROTON-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated PROTON-1592: Fix Version/s: (was: proton-c-future) proton-c-0.22.0 > [proton-python]

[jira] [Commented] (PROTON-1760) [ruby-binding] the package name on rubygems.org does not follow conventions

[ https://issues.apache.org/jira/browse/PROTON-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16380824#comment-16380824 ] Alan Conway commented on PROTON-1760: - [~iboverma] you should keep an eye on this for downstream

[jira] [Commented] (PROTON-1760) [ruby-binding] the package name on rubygems.org does not follow conventions

[ https://issues.apache.org/jira/browse/PROTON-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16380823#comment-16380823 ] Alan Conway commented on PROTON-1760: - According to http://guides.rubygems.org/name-your-gem/ the gem

[jira] [Updated] (PROTON-1775) rubygem doc is not multilib-clean for x86_64 vs i686

[ https://issues.apache.org/jira/browse/PROTON-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated PROTON-1775: Fix Version/s: proton-c-0.22.0 > rubygem doc is not multilib-clean for x86_64 vs i686 >

[jira] [Updated] (PROTON-1760) [ruby-binding] the package name on rubygems.org does not follow conventions

[ https://issues.apache.org/jira/browse/PROTON-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated PROTON-1760: Fix Version/s: proton-c-0.22.0 > [ruby-binding] the package name on rubygems.org does not follow

[jira] [Commented] (PROTON-1764) Slow performance seen when running Go client

[ https://issues.apache.org/jira/browse/PROTON-1764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16379414#comment-16379414 ] Alan Conway commented on PROTON-1764: - It is expected that the go client spend a lot of time in the C

[jira] [Resolved] (PROTON-1773) Access after free possibly created by recent fix

[ https://issues.apache.org/jira/browse/PROTON-1773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1773. - Resolution: Fixed > Access after free possibly created by recent fix >

[jira] [Commented] (PROTON-1775) rubygem doc is not multilib-clean for x86_64 vs i686

[ https://issues.apache.org/jira/browse/PROTON-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16377553#comment-16377553 ] Alan Conway commented on PROTON-1775: - Gotcha, I'll find a way around it. > rubygem doc is not

[jira] [Updated] (PROTON-1770) CLONE - [cpp] win_iocp fix for seg fault in reconnect test

[ https://issues.apache.org/jira/browse/PROTON-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated PROTON-1770: Fix Version/s: (was: proton-c-0.21.0) proton-c-0.22.0 > CLONE - [cpp]

[jira] [Commented] (PROTON-1775) rubygem doc is not multilib-clean for x86_64 vs i686

[ https://issues.apache.org/jira/browse/PROTON-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16377532#comment-16377532 ] Alan Conway commented on PROTON-1775: - I don't understand the error - how can .html files have

[jira] [Resolved] (PROTON-1776) [ruby] on_sender/receiver_open/close events are not generated

[ https://issues.apache.org/jira/browse/PROTON-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1776. - Resolution: Fixed > [ruby] on_sender/receiver_open/close events are not generated >

[jira] [Created] (PROTON-1776) [ruby] on_sender/receiver_open/close events are not generated

Alan Conway created PROTON-1776: --- Summary: [ruby] on_sender/receiver_open/close events are not generated Key: PROTON-1776 URL: https://issues.apache.org/jira/browse/PROTON-1776 Project: Qpid Proton

[jira] [Created] (PROTON-1771) [c-proactor] multi-thread race test for proactor

Alan Conway created PROTON-1771: --- Summary: [c-proactor] multi-thread race test for proactor Key: PROTON-1771 URL: https://issues.apache.org/jira/browse/PROTON-1771 Project: Qpid Proton Issue

[jira] [Assigned] (PROTON-1643) [FreeBSD] ruby-old-example-test hangs

[ https://issues.apache.org/jira/browse/PROTON-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway reassigned PROTON-1643: --- Assignee: Alan Conway (was: Andrew Stitcher) > [FreeBSD] ruby-old-example-test hangs >

[jira] [Commented] (PROTON-1766) [cpp] seg fault in reconnect test

[ https://issues.apache.org/jira/browse/PROTON-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373134#comment-16373134 ] Alan Conway commented on PROTON-1766: - Fixed on epoll and libuv. NOT fixed for windows IOCP. New

[jira] [Resolved] (PROTON-1766) [cpp] seg fault in reconnect test

[ https://issues.apache.org/jira/browse/PROTON-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1766. - Resolution: Fixed > [cpp] seg fault in reconnect test > - > >

[jira] [Reopened] (PROTON-1770) CLONE - [cpp] win_iocp fix for seg fault in reconnect test

[ https://issues.apache.org/jira/browse/PROTON-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway reopened PROTON-1770: - Closed by mistake > CLONE - [cpp] win_iocp fix for seg fault in reconnect test >

[jira] [Commented] (PROTON-1770) CLONE - [cpp] win_iocp fix for seg fault in reconnect test

[ https://issues.apache.org/jira/browse/PROTON-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373111#comment-16373111 ] Alan Conway commented on PROTON-1770: - Fixed for epoll and libuv, see commits for PROTON-1766.

[jira] [Assigned] (PROTON-1770) CLONE - [cpp] win_iocp fix for seg fault in reconnect test

[ https://issues.apache.org/jira/browse/PROTON-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway reassigned PROTON-1770: --- Assignee: Cliff Jansen (was: Alan Conway) > CLONE - [cpp] win_iocp fix for seg fault in

[jira] [Resolved] (PROTON-1770) CLONE - [cpp] win_iocp fix for seg fault in reconnect test

[ https://issues.apache.org/jira/browse/PROTON-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1770. - Resolution: Fixed > CLONE - [cpp] win_iocp fix for seg fault in reconnect test >

[jira] [Created] (PROTON-1770) CLONE - [cpp] win_iocp fix for seg fault in reconnect test

Alan Conway created PROTON-1770: --- Summary: CLONE - [cpp] win_iocp fix for seg fault in reconnect test Key: PROTON-1770 URL: https://issues.apache.org/jira/browse/PROTON-1770 Project: Qpid Proton

[jira] [Created] (QPID-8107) [ruby] cproton.i not building on RHEL 6

Alan Conway created QPID-8107: - Summary: [ruby] cproton.i not building on RHEL 6 Key: QPID-8107 URL: https://issues.apache.org/jira/browse/QPID-8107 Project: Qpid Issue Type: Bug

[jira] [Commented] (PROTON-447) Ruby types returned from Data should carry their AMQP type

[ https://issues.apache.org/jira/browse/PROTON-447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16371583#comment-16371583 ] Alan Conway commented on PROTON-447: It is not possible to add information to immediate type

[jira] [Updated] (PROTON-447) Ruby types returned from Data should carry their AMQP type

[ https://issues.apache.org/jira/browse/PROTON-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated PROTON-447: --- Priority: Minor (was: Major) > Ruby types returned from Data should carry their AMQP type >

[jira] [Comment Edited] (PROTON-1734) [cpp] container.stop() doesn't work when called from non-proactor thread.

[ https://issues.apache.org/jira/browse/PROTON-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16370416#comment-16370416 ] Alan Conway edited comment on PROTON-1734 at 2/20/18 6:30 PM: -- I think this

[jira] [Commented] (PROTON-1734) [cpp] container.stop() doesn't work when called from non-proactor thread.

[ https://issues.apache.org/jira/browse/PROTON-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16370416#comment-16370416 ] Alan Conway commented on PROTON-1734: - I think this is a proactor behavior problem. In stop(), C++

[jira] [Comment Edited] (PROTON-1734) [cpp] container.stop() doesn't work when called from non-proactor thread.

[ https://issues.apache.org/jira/browse/PROTON-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16370416#comment-16370416 ] Alan Conway edited comment on PROTON-1734 at 2/20/18 6:29 PM: -- I think this

[jira] [Commented] (PROTON-1766) [cpp] seg fault in reconnect test

[ https://issues.apache.org/jira/browse/PROTON-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16370354#comment-16370354 ] Alan Conway commented on PROTON-1766: - NOTE: the issue can be reproduced using

[jira] [Created] (PROTON-1766) [cpp] seg fault in reconnect test

Alan Conway created PROTON-1766: --- Summary: [cpp] seg fault in reconnect test Key: PROTON-1766 URL: https://issues.apache.org/jira/browse/PROTON-1766 Project: Qpid Proton Issue Type:

[jira] [Updated] (PROTON-1765) [ruby] auto-test of installed gem

[ https://issues.apache.org/jira/browse/PROTON-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated PROTON-1765: Description: Restore the following tests to the ruby/CMakeLists.txt section that builds a gem:

[jira] [Created] (PROTON-1765) [ruby] auto-test of installed gem

Alan Conway created PROTON-1765: --- Summary: [ruby] auto-test of installed gem Key: PROTON-1765 URL: https://issues.apache.org/jira/browse/PROTON-1765 Project: Qpid Proton Issue Type:

[jira] [Resolved] (PROTON-1762) [ruby] gem does not contain examples or tests

[ https://issues.apache.org/jira/browse/PROTON-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1762. - Resolution: Fixed > [ruby] gem does not contain examples or tests >

[jira] [Commented] (PROTON-1762) [ruby] gem does not contain examples or tests

[ https://issues.apache.org/jira/browse/PROTON-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16364770#comment-16364770 ] Alan Conway commented on PROTON-1762: - Also should allow building the gem *without* the C library.

[jira] [Closed] (PROTON-1761) [ruby-binding] proton-c/bindings/ruby/cprotonRUBY_wrap.c:2166:26: warning: implicit declaration of function ‘rb_thread_call_without_gvl’ [-Wimplicit-function-declaration]

[ https://issues.apache.org/jira/browse/PROTON-1761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway closed PROTON-1761. --- Resolution: Duplicate Fixed by commit 9a8f9f59 PROTON-1738: [ruby] Fix compile warnings in SWIG

[jira] [Resolved] (PROTON-1738) [ruby-binding] incompatible with ruby 2.0.0

[ https://issues.apache.org/jira/browse/PROTON-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1738. - Resolution: Fixed Fixed and tested on 1.9.3, 2.0.0, 2.4.3. If we need compatibility further back

[jira] [Commented] (PROTON-1762) [ruby] gem does not contain examples or tests

[ https://issues.apache.org/jira/browse/PROTON-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16364384#comment-16364384 ] Alan Conway commented on PROTON-1762: - We also should have a cmake auto-test that installs the gem

[jira] [Updated] (PROTON-1762) [ruby] gem does not contain examples or tests

[ https://issues.apache.org/jira/browse/PROTON-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated PROTON-1762: Description: The ruby gem created by cmake does not include example files or tests.  The example

[jira] [Updated] (PROTON-1762) [ruby] gem does not contain examples

[ https://issues.apache.org/jira/browse/PROTON-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated PROTON-1762: Description: The ruby gem created by cmake does not include example files or tests.  The example

[jira] [Updated] (PROTON-1762) [ruby] gem does not contain examples or tests

[ https://issues.apache.org/jira/browse/PROTON-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated PROTON-1762: Summary: [ruby] gem does not contain examples or tests (was: [ruby] gem does not contain

[jira] [Created] (PROTON-1762) [ruby] gem does not contain examples

Alan Conway created PROTON-1762: --- Summary: [ruby] gem does not contain examples Key: PROTON-1762 URL: https://issues.apache.org/jira/browse/PROTON-1762 Project: Qpid Proton Issue Type:

[jira] [Commented] (PROTON-1738) [ruby-binding] incompatible with ruby 2.0.0

[ https://issues.apache.org/jira/browse/PROTON-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16319072#comment-16319072 ] Alan Conway commented on PROTON-1738: - Attached patch partially fixes the 2.0.0 issues, but there are

[jira] [Updated] (PROTON-1738) [ruby-binding] incompatible with ruby 2.0.0

[ https://issues.apache.org/jira/browse/PROTON-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated PROTON-1738: Attachment: 0001-WIP-Fix-for-issues-on-ruby-2.0.0.patch > [ruby-binding] incompatible with ruby

[jira] [Resolved] (PROTON-1733) [cpp] Provide access to actual listening port for listen(":0")

[ https://issues.apache.org/jira/browse/PROTON-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1733. - Resolution: Fixed > [cpp] Provide access to actual listening port for listen(":0") >

[jira] [Created] (PROTON-1734) [cpp] container.stop() doesn't work when called from non-proactor thread.

Alan Conway created PROTON-1734: --- Summary: [cpp] container.stop() doesn't work when called from non-proactor thread. Key: PROTON-1734 URL: https://issues.apache.org/jira/browse/PROTON-1734 Project:

[jira] [Commented] (DISPATCH-878) qdrouterd should log real port if port 0 was specified for the listener port property in qdrouterd.conf

[ https://issues.apache.org/jira/browse/DISPATCH-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16312049#comment-16312049 ] Alan Conway commented on DISPATCH-878: -- Fixed PROTON-1706. You can now get the list of real

[jira] [Updated] (PROTON-1705) [go] binding puts build artifacts in the source tree

[ https://issues.apache.org/jira/browse/PROTON-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated PROTON-1705: Fix Version/s: proton-c-0.20.0 > [go] binding puts build artifacts in the source tree >

[jira] [Updated] (DISPATCH-227) Independent filtering of logging to consoles and log files.

[ https://issues.apache.org/jira/browse/DISPATCH-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated DISPATCH-227: - Priority: Minor (was: Major) > Independent filtering of logging to consoles and log files. >

[jira] [Resolved] (PROTON-1705) [go] binding puts build artifacts in the source tree

[ https://issues.apache.org/jira/browse/PROTON-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1705. - Resolution: Fixed > [go] binding puts build artifacts in the source tree >

[jira] [Resolved] (PROTON-1644) [FreeBSD] Scheme for reusing ports in testing does not work for FreeBSD

[ https://issues.apache.org/jira/browse/PROTON-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1644. - Resolution: Fixed > [FreeBSD] Scheme for reusing ports in testing does not work for FreeBSD >

[jira] [Commented] (PROTON-1644) [FreeBSD] Scheme for reusing ports in testing does not work for FreeBSD

[ https://issues.apache.org/jira/browse/PROTON-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16312036#comment-16312036 ] Alan Conway commented on PROTON-1644: - C++ fixed by PROTON-1733 PROTON-1646 is still valid, although

[jira] [Resolved] (PROTON-1733) [cpp] Provide access to actual listening port for listen(":0")

[ https://issues.apache.org/jira/browse/PROTON-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1733. - Resolution: Fixed > [cpp] Provide access to actual listening port for listen(":0") >

[jira] [Created] (PROTON-1733) [cpp] Provide access to actual listening port for listen(":0")

Alan Conway created PROTON-1733: --- Summary: [cpp] Provide access to actual listening port for listen(":0") Key: PROTON-1733 URL: https://issues.apache.org/jira/browse/PROTON-1733 Project: Qpid Proton

[jira] [Commented] (PROTON-1644) [FreeBSD] Scheme for reusing ports in testing does not work for FreeBSD

[ https://issues.apache.org/jira/browse/PROTON-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16311774#comment-16311774 ] Alan Conway commented on PROTON-1644: - C tests and examples fixed by PROTON-1706, using listen ":0"

[jira] [Resolved] (PROTON-1706) pn_listener_t provide access to actual listening port

[ https://issues.apache.org/jira/browse/PROTON-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1706. - Resolution: Fixed > pn_listener_t provide access to actual listening port >

[jira] [Resolved] (DISPATCH-893) Compile fails using libwebsockets 7

[ https://issues.apache.org/jira/browse/DISPATCH-893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved DISPATCH-893. -- Resolution: Fixed > Compile fails using libwebsockets 7 > ---

[jira] [Updated] (PROTON-1703) [cpp] Remove auto_settle from receiver options

[ https://issues.apache.org/jira/browse/PROTON-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated PROTON-1703: Priority: Minor (was: Major) > [cpp] Remove auto_settle from receiver options >

[jira] [Commented] (PROTON-1706) pn_listener_t provide access to actual listening port

[ https://issues.apache.org/jira/browse/PROTON-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16308672#comment-16308672 ] Alan Conway commented on PROTON-1706: - Simplified proposed API, since the proactor must create all

[jira] [Commented] (DISPATCH-739) Enable valgrind leak-check=full and fix any memory errors found

[ https://issues.apache.org/jira/browse/DISPATCH-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16308334#comment-16308334 ] Alan Conway commented on DISPATCH-739: -- I still see a lot of memory errors on master. I fixed a

[jira] [Commented] (DISPATCH-902) Intermittent crash with link to broker when broker closed

[ https://issues.apache.org/jira/browse/DISPATCH-902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16301679#comment-16301679 ] Alan Conway commented on DISPATCH-902: -- Fixed PROTON-1727 which I believe is the root cause of this

[jira] [Assigned] (DISPATCH-902) Intermittent crash with link to broker when broker closed

[ https://issues.apache.org/jira/browse/DISPATCH-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway reassigned DISPATCH-902: Assignee: Ganesh Murthy (was: Alan Conway) > Intermittent crash with link to broker

[jira] [Resolved] (PROTON-1727) [epoll proactor] segfaults, hangs and leaked FDs around failed connect

[ https://issues.apache.org/jira/browse/PROTON-1727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1727. - Resolution: Fixed > [epoll proactor] segfaults, hangs and leaked FDs around failed connect >

[jira] [Updated] (PROTON-1727) [epoll proactor] segfaults, hangs and leaked FDs around failed connect

[ https://issues.apache.org/jira/browse/PROTON-1727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated PROTON-1727: Priority: Blocker (was: Major) > [epoll proactor] segfaults, hangs and leaked FDs around failed

[jira] [Updated] (PROTON-1727) [epoll proactor] segfaults, hangs and leaked FDs around failed connect

[ https://issues.apache.org/jira/browse/PROTON-1727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated PROTON-1727: Fix Version/s: (was: proton-c-0.19.0) proton-c-0.20.0 > [epoll proactor]

[jira] [Updated] (PROTON-1727) [epoll proactor] segfaults, hangs and leaked FDs around failed connect

[ https://issues.apache.org/jira/browse/PROTON-1727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated PROTON-1727: Fix Version/s: proton-c-0.19.0 > [epoll proactor] segfaults, hangs and leaked FDs around failed

[jira] [Created] (PROTON-1727) [epoll proactor] segfaults, hangs and leaked FDs around failed connect

Alan Conway created PROTON-1727: --- Summary: [epoll proactor] segfaults, hangs and leaked FDs around failed connect Key: PROTON-1727 URL: https://issues.apache.org/jira/browse/PROTON-1727 Project: Qpid

[jira] [Updated] (DISPATCH-902) Intermittent crash with link to broker when broker closed

[ https://issues.apache.org/jira/browse/DISPATCH-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway updated DISPATCH-902: - Attachment: testme.tgz Proton-only reproducer. See Makefile for how to build/run. Notes: - you

[jira] [Resolved] (PROTON-1725) [ruby] broker example does not work if run outside home directory

[ https://issues.apache.org/jira/browse/PROTON-1725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1725. - Resolution: Fixed > [ruby] broker example does not work if run outside home directory >

[jira] [Resolved] (PROTON-1724) [ruby] early error in Container#listen is not handled correctly

[ https://issues.apache.org/jira/browse/PROTON-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1724. - Resolution: Fixed > [ruby] early error in Container#listen is not handled correctly >

[jira] [Created] (PROTON-1725) [ruby] broker example does not work if run outside home directory

Alan Conway created PROTON-1725: --- Summary: [ruby] broker example does not work if run outside home directory Key: PROTON-1725 URL: https://issues.apache.org/jira/browse/PROTON-1725 Project: Qpid Proton

[jira] [Created] (PROTON-1724) [ruby] early error in Container#listen is not handled correctly

Alan Conway created PROTON-1724: --- Summary: [ruby] early error in Container#listen is not handled correctly Key: PROTON-1724 URL: https://issues.apache.org/jira/browse/PROTON-1724 Project: Qpid Proton

[jira] [Assigned] (DISPATCH-902) Intermittent crash with link to broker when broker closed

[ https://issues.apache.org/jira/browse/DISPATCH-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway reassigned DISPATCH-902: Assignee: Alan Conway (was: Ted Ross) > Intermittent crash with link to broker when

[jira] [Comment Edited] (PROTON-1079) Ruby Reactor interface fails with SSL.new ArgumentError

[ https://issues.apache.org/jira/browse/PROTON-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16296955#comment-16296955 ] Alan Conway edited comment on PROTON-1079 at 12/19/17 3:27 PM: ---

[jira] [Commented] (PROTON-1079) Ruby Reactor interface fails with SSL.new ArgumentError

[ https://issues.apache.org/jira/browse/PROTON-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16296955#comment-16296955 ] Alan Conway commented on PROTON-1079: - [~jr...@redhat.com] it should. That reactor code is gone,

[jira] [Resolved] (PROTON-1720) [ruby] support for SSL configuration via connection options

[ https://issues.apache.org/jira/browse/PROTON-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1720. - Resolution: Fixed > [ruby] support for SSL configuration via connection options >

[jira] [Resolved] (PROTON-1721) [ruby] resovler errors are not handled correctly

[ https://issues.apache.org/jira/browse/PROTON-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1721. - Resolution: Fixed Fix Version/s: proton-c-0.19.0 > [ruby] resovler errors are not handled

[jira] [Created] (PROTON-1721) [ruby] resovler errors are not handled correctly

Alan Conway created PROTON-1721: --- Summary: [ruby] resovler errors are not handled correctly Key: PROTON-1721 URL: https://issues.apache.org/jira/browse/PROTON-1721 Project: Qpid Proton Issue

[jira] [Created] (PROTON-1720) [ruby] support for SSL configuration via connection options

Alan Conway created PROTON-1720: --- Summary: [ruby] support for SSL configuration via connection options Key: PROTON-1720 URL: https://issues.apache.org/jira/browse/PROTON-1720 Project: Qpid Proton

[jira] [Resolved] (PROTON-1717) [C proactor] Allow initialization of transport and connection before binding

[ https://issues.apache.org/jira/browse/PROTON-1717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1717. - Resolution: Fixed > [C proactor] Allow initialization of transport and connection before binding

[jira] [Resolved] (PROTON-1537) ruby: update API in line with new C++ API changes

[ https://issues.apache.org/jira/browse/PROTON-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1537. - Resolution: Fixed > ruby: update API in line with new C++ API changes >

[jira] [Created] (PROTON-1717) [C proactor] Allow initialization of transport and connection before binding

Alan Conway created PROTON-1717: --- Summary: [C proactor] Allow initialization of transport and connection before binding Key: PROTON-1717 URL: https://issues.apache.org/jira/browse/PROTON-1717 Project:

[jira] [Assigned] (DISPATCH-893) Compile fails using libwebsockets 7

[ https://issues.apache.org/jira/browse/DISPATCH-893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway reassigned DISPATCH-893: Assignee: Alan Conway > Compile fails using libwebsockets 7 >

[jira] [Resolved] (PROTON-1693) [ruby] Replace C-reactor based code with new Container

[ https://issues.apache.org/jira/browse/PROTON-1693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1693. - Resolution: Fixed Fix Version/s: proton-c-0.19.0 The later against 1064 should really be

[jira] [Resolved] (DISPATCH-874) unable to load .json or .woff2 files from local file system from http port

[ https://issues.apache.org/jira/browse/DISPATCH-874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved DISPATCH-874. -- Resolution: Fixed > unable to load .json or .woff2 files from local file system from http

[jira] [Assigned] (DISPATCH-874) unable to load .json or .woff2 files from local file system from http port

[ https://issues.apache.org/jira/browse/DISPATCH-874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway reassigned DISPATCH-874: Assignee: Alan Conway > unable to load .json or .woff2 files from local file system from

[jira] [Commented] (DISPATCH-878) qdrouterd should log real port if port 0 was specified for the listener port property in qdrouterd.conf

[ https://issues.apache.org/jira/browse/DISPATCH-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16274560#comment-16274560 ] Alan Conway commented on DISPATCH-878: -- I think we can support greppable real ports easily enough,

[jira] [Created] (PROTON-1706) pn_listener_t provide access to actual listening port

Alan Conway created PROTON-1706: --- Summary: pn_listener_t provide access to actual listening port Key: PROTON-1706 URL: https://issues.apache.org/jira/browse/PROTON-1706 Project: Qpid Proton

[jira] [Created] (PROTON-1705) [go] binding puts build artifacts in the source tree

Alan Conway created PROTON-1705: --- Summary: [go] binding puts build artifacts in the source tree Key: PROTON-1705 URL: https://issues.apache.org/jira/browse/PROTON-1705 Project: Qpid Proton

[jira] [Resolved] (PROTON-1704) [c proactor] test_ipv4_ipv6 intermittent failure on FreeBSD

[ https://issues.apache.org/jira/browse/PROTON-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1704. - Resolution: Fixed > [c proactor] test_ipv4_ipv6 intermittent failure on FreeBSD >

[jira] [Created] (PROTON-1704) [c proactor] test_ipv4_ipv6 intermittent failure on FreeBSD

Alan Conway created PROTON-1704: --- Summary: [c proactor] test_ipv4_ipv6 intermittent failure on FreeBSD Key: PROTON-1704 URL: https://issues.apache.org/jira/browse/PROTON-1704 Project: Qpid Proton

[jira] [Commented] (DISPATCH-878) qdrouterd should log real port if port 0 was specified for the listener port property in qdrouterd.conf

[ https://issues.apache.org/jira/browse/DISPATCH-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16273395#comment-16273395 ] Alan Conway commented on DISPATCH-878: -- FYI, on Unix platforms you can find the port using standard

[jira] [Resolved] (PROTON-1703) [cpp] Remove auto_settle from receiver options

[ https://issues.apache.org/jira/browse/PROTON-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1703. - Resolution: Fixed > [cpp] Remove auto_settle from receiver options >

<    1   2   3   4   5   6   7   8   9   10   >