[jira] [Commented] (PROTON-1703) [cpp] Remove auto_settle from receiver options
[ https://issues.apache.org/jira/browse/PROTON-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532921#comment-16532921 ] Alan Conway commented on PROTON-1703: - [~jr...@redhat.com] do we have a strategy to track bugs like this that are waiting for a binary-incompat release? It's unlikely to get attention at the right moment if it's just sitting at the low-priority end of my to-do list. > [cpp] Remove auto_settle from receiver options > -- > > Key: PROTON-1703 > URL: https://issues.apache.org/jira/browse/PROTON-1703 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Affects Versions: proton-c-0.19.0 >Reporter: Alan Conway >Assignee: Alan Conway >Priority: Minor > > auto_settle is a sender-only option, the receiver equivalent is auto_accept. > auto_settle is only used at messaging_adapter.cpp#L172, which applies only to > senders, it was included in the option list by mistake. -- 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=16532909#comment-16532909 ] ASF subversion and git services commented on PROTON-1852: - Commit a7243b2e7928db2dce55c8db9f1ee67d931ca187 in qpid-proton's branch refs/heads/go1 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-1866) cannot tell whether peer specified expiry-policy on terminus
[ https://issues.apache.org/jira/browse/PROTON-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532906#comment-16532906 ] ASF subversion and git services commented on PROTON-1866: - Commit ccb9e5a388022e529502dcc547b7862b2185d6bc in qpid-proton's branch refs/heads/go1 from Gordon Sim [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=ccb9e5a ] PROTON-1866: provide method to determine whether expiry policy was set explicitly or not > cannot tell whether peer specified expiry-policy on terminus > > > Key: PROTON-1866 > URL: https://issues.apache.org/jira/browse/PROTON-1866 > Project: Qpid Proton > Issue Type: Bug >Affects Versions: proton-c-0.23.0 >Reporter: Gordon Sim >Assignee: Gordon Sim >Priority: Major > Fix For: proton-c-0.24.0 > > > This prevents anything using proton-c to behave differently if an explicit > policy is set. -- 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-1869) [Python] Compiler conversion warnings with Win64 builds
[ https://issues.apache.org/jira/browse/PROTON-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532908#comment-16532908 ] ASF subversion and git services commented on PROTON-1869: - Commit 7c0a3387a5096d86541dbddfeb55f36eb0b85dd8 in qpid-proton's branch refs/heads/go1 from [~astitcher] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=7c0a338 ] PROTON-1869: Fix some SWIG Python Win64 type/pointer conversion problems > [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] [Commented] (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:comment-tabpanel=16532907#comment-16532907 ] ASF subversion and git services commented on PROTON-1868: - Commit 798894f63dba6a0d4eaa6e015d6f5ac64274be2f in qpid-proton's branch refs/heads/go1 from [~astitcher] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=798894f ] PROTON-1868: Fix pn_handle_t python binding on Visual Studio 64 bit compiles > [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] (PROTON-1865) Improve split between general SASL code and the specific implementations
[ https://issues.apache.org/jira/browse/PROTON-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532902#comment-16532902 ] ASF subversion and git services commented on PROTON-1865: - Commit 885d68aeaf522021a35b7b5cecb7c7c53663929b in qpid-proton's branch refs/heads/go1 from [~astitcher] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=885d68a ] PROTON-1865: Improve the split between general SASL code and the specific implementations > Improve split between general SASL code and the specific implementations > > > Key: PROTON-1865 > URL: https://issues.apache.org/jira/browse/PROTON-1865 > Project: Qpid Proton > Issue Type: Improvement > Components: proton-c >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.24.0 > > > There are a number of places where the SASL code needs to be tidied up since > it was split into general and plugin implementations. > Specifically checking for inclusion in the allowed mechanisms list only needs > to happen in the common code and the specific implementations only need to > receive a prefiltered list. -- 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-1867) Debug libs missing in Windows build
[ https://issues.apache.org/jira/browse/PROTON-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532904#comment-16532904 ] ASF subversion and git services commented on PROTON-1867: - Commit ba2975fc49da1761fd4c246d7898544b6b8c4c20 in qpid-proton's branch refs/heads/go1 from [~jr...@redhat.com] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=ba2975f ] PROTON-1867: Restore suffix for debug libs > Debug libs missing in Windows build > --- > > Key: PROTON-1867 > URL: https://issues.apache.org/jira/browse/PROTON-1867 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Reporter: Justin Ross >Assignee: Justin Ross >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=16532905#comment-16532905 ] ASF subversion and git services commented on PROTON-1852: - Commit b1b8322b2f8f29653c8970aad5d37b3b22c56923 in qpid-proton's branch refs/heads/go1 from [~jr...@redhat.com] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=b1b8322 ] PROTON-1852: Update SO versions after ABI change review > 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] [Created] (PROTON-1884) [python] examples don't work with other language brokers
Alan Conway created PROTON-1884: --- Summary: [python] examples don't work with other language brokers Key: PROTON-1884 URL: https://issues.apache.org/jira/browse/PROTON-1884 Project: Qpid Proton Issue Type: Bug Components: python-binding Affects Versions: proton-c-0.23.0 Reporter: Alan Conway Assignee: Andrew Stitcher The python simple_send client does not work with c, cpp or ruby example brokers. It hangs during the SASL negotiation. It does work with the python example broker. Based on hand testing a few combinations, the c, cpp and ruby examples all appear to interoperate. -- 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-1883) add interop smoke test for examples
Alan Conway created PROTON-1883: --- Summary: add interop smoke test for examples Key: PROTON-1883 URL: https://issues.apache.org/jira/browse/PROTON-1883 Project: Qpid Proton Issue Type: Bug Components: examples Affects Versions: proton-c-0.23.0 Reporter: Alan Conway Assignee: Alan Conway Add a simple interop smoke-test for the examples: run simple_send and simple_receive against example brokers to verify that each language pair can interoperate. -- 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-905) Long-lived connections leak sessions and links
[
https://issues.apache.org/jira/browse/PROTON-905?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16532420#comment-16532420
]
Pavel Moravec commented on PROTON-905:
--
I think this Jira is behind qdrouterd memory accumulation as described in
[https://issues.jboss.org/browse/ENTMQIC-2023] - copying the (more trivial,
slower) reproducer of a client connecting to qdrouterd here:
|{color:#00}import random{color}|
|{color:#00}from proton.utils import BlockingConnection{color}|
|{color:#00}from time import sleep{color}|
|{color:#00}from uuid import uuid4{color}|
| |
|{color:#00}ROUTER_ADDRESS = "proton+amqp://0.0.0.0:5672"{color}|
|{color:#00}ADDRESS = "test.address"{color}|
|{color:#00}HEARTBEAT = 5{color}|
|{color:#00}SLEEP_MIN = 0.1{color}|
|{color:#00}SLEEP_MAX = 0.2{color}|
| |
|{color:#00}conn = BlockingConnection(ROUTER_ADDRESS, ssl_domain=None,
heartbeat=HEARTBEAT){color}|
| |
|{color:#00}while True:{color}|
|{color:#00} recv = conn.create_receiver('%s' %(ADDRESS),
name=str(uuid4()), dynamic=False, options=None){color}|
|{color:#00} sleep(random.uniform(SLEEP_MIN,SLEEP_MAX)){color}|
|{color:#00} recv.close(){color}|
|{color:#00} sleep(random.uniform(SLEEP_MIN,SLEEP_MAX)) {color}|
> Long-lived connections leak sessions and links
> --
>
> Key: PROTON-905
> URL: https://issues.apache.org/jira/browse/PROTON-905
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
>Affects Versions: 0.9.1, 0.10
>Reporter: Ken Giusti
>Priority: Minor
> Labels: leak
> Fix For: proton-c-future
>
> Attachments: test-send.py
>
>
> I found this issue while debugging a crash dump of qpidd.
> Long lived connections do not free its sessions/link.
> This only applies when NOT using the event model. The version of qpidd I
> tested against (0.30) still uses the iterative model. Point to consider, I
> don't know why this is the case.
> Details: I have a test script that opens a single connection, then
> continually creates sessions/links over that connection, sending one message
> before closing and freeing the sessions/links. See attached.
> Over time the qpidd run time consumes all memory on the system and is killed
> by OOM. To be clear, I'm using drain to remove all sent messages - there is
> no message build up.
> On debugging this, I'm finding thousands of session objects on the
> connections free sessions weakref list. Every one of those sessions has a
> refcount of one.
> Once the connection is finalized, all session objects are freed. But until
> then, freed sessions continue to accumulate indefinitely.
--
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
