[jira] [Commented] (PROTON-1077) receiver link and transport view of credit can become disjoint when sending link sends flow frames
[ https://issues.apache.org/jira/browse/PROTON-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15057682#comment-15057682 ] Keith Wall commented on PROTON-1077: Robbie, I repeated the test described by QPID-6863 against the Java Broker with the above Proton change applied. I was no longer able to reproduce the issue. I ran for fifteen minutes with no recurrence. We'll be looking at the Java Broker issue (QPID-6947) separately. > receiver link and transport view of credit can become disjoint when sending > link sends flow frames > -- > > Key: PROTON-1077 > URL: https://issues.apache.org/jira/browse/PROTON-1077 > Project: Qpid Proton > Issue Type: Bug > Components: proton-j >Affects Versions: 0.11 >Reporter: Robbie Gemmell > > If a recieving link receives flow frames from the sending peer updating > advancing the delivery count [and setting credit to 0], then recieves flow > frames from the sender updating credit but not advancing the delivery count, > then receives messages, the Link and TransportLink views of the credit can > become disjoint, leading applications to think they have a different amount > of credit than they actually do, and leading to a different amount of new > credit being flowed to the sender than expected, even none. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PROTON-1077) receiver link and transport view of credit can become disjoint when sending link sends flow frames
[ https://issues.apache.org/jira/browse/PROTON-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058221#comment-15058221 ] ASF subversion and git services commented on PROTON-1077: - Commit a8d87bb3c6d54458d7041d38374feb8b7cf30667 in qpid-proton's branch refs/heads/master from Robert Gemmell [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=a8d87bb ] PROTON-1077: adjust the receivers transport credit state by the same delta as the link credit state when deliveryCount advances to keep them in sync > receiver link and transport view of credit can become disjoint when sending > link sends flow frames > -- > > Key: PROTON-1077 > URL: https://issues.apache.org/jira/browse/PROTON-1077 > Project: Qpid Proton > Issue Type: Bug > Components: proton-j >Affects Versions: 0.11 >Reporter: Robbie Gemmell > > If a recieving link receives flow frames from the sending peer updating > advancing the delivery count [and setting credit to 0], then recieves flow > frames from the sender updating credit but not advancing the delivery count, > then receives messages, the Link and TransportLink views of the credit can > become disjoint, leading applications to think they have a different amount > of credit than they actually do, and leading to a different amount of new > credit being flowed to the sender than expected, even none. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PROTON-1077) receiver link and transport view of credit can become disjoint when sending link sends flow frames
[ https://issues.apache.org/jira/browse/PROTON-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058225#comment-15058225 ] ASF subversion and git services commented on PROTON-1077: - Commit 3a8782b9871fa35db0c69c994c4c4667251242b0 in qpid-proton's branch refs/heads/0.11.x from Robert Gemmell [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=3a8782b ] PROTON-1077: adjust the receivers transport credit state by the same delta as the link credit state when deliveryCount advances to keep them in sync (cherry picked from commit a8d87bb3c6d54458d7041d38374feb8b7cf30667) > receiver link and transport view of credit can become disjoint when sending > link sends flow frames > -- > > Key: PROTON-1077 > URL: https://issues.apache.org/jira/browse/PROTON-1077 > Project: Qpid Proton > Issue Type: Bug > Components: proton-j >Affects Versions: 0.11 >Reporter: Robbie Gemmell > > If a recieving link receives flow frames from the sending peer updating > advancing the delivery count [and setting credit to 0], then recieves flow > frames from the sender updating credit but not advancing the delivery count, > then receives messages, the Link and TransportLink views of the credit can > become disjoint, leading applications to think they have a different amount > of credit than they actually do, and leading to a different amount of new > credit being flowed to the sender than expected, even none. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[VOTE] Release Qpid Proton 0.11.1
Hi all, I have put up an RC for 0.11.1, please test it and vote accordingly. The release archive and sig/checksums can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/proton/0.11.1-rc1/ Maven artifacts for the Java bits can be found in a temporary staging repo at: https://repository.apache.org/content/repositories/orgapacheqpid-1057 Other than version updates, there are only two changes since 0.11.0: https://issues.apache.org/jira/browse/PROTON-1059 https://issues.apache.org/jira/browse/PROTON-1077 It was created using commit 99ee72b897395b0abb72df001709095b498edbc5 on the 0.11.x branch, and is tagged as 0.11.1-rc1. Regards, Robbie
[jira] [Created] (PROTON-1080) have container attribute on any relevant event
Gordon Sim created PROTON-1080: -- Summary: have container attribute on any relevant event Key: PROTON-1080 URL: https://issues.apache.org/jira/browse/PROTON-1080 Project: Qpid Proton Issue Type: Bug Components: python-binding Affects Versions: 0.11 Reporter: Gordon Sim Assignee: Gordon Sim Fix For: 0.12.0 At present event.container is an alias for event.reactor only for the on_start() event (and obviously only when a Container instance is actually being used). It would be nicer to make that alias available on all events. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (PROTON-1049) Reactor needs an alternative to using the URL to pass user authentication information.
[ https://issues.apache.org/jira/browse/PROTON-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim reassigned PROTON-1049: -- Assignee: Gordon Sim > Reactor needs an alternative to using the URL to pass user authentication > information. > -- > > Key: PROTON-1049 > URL: https://issues.apache.org/jira/browse/PROTON-1049 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: 0.11 >Reporter: Ken Giusti >Assignee: Gordon Sim >Priority: Blocker > Fix For: 0.12.0 > > > When creating a connection using the Container class, the only way to specify > the username/password credentials is via the URL. This may cause the > credentials to be leaked via the "ps" command if the URL is passed via a > command line argument. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PROTON-1026) Invalid queue/destination causes a segmentation fault
[ https://issues.apache.org/jira/browse/PROTON-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058883#comment-15058883 ] ASF subversion and git services commented on PROTON-1026: - Commit 87ece507eddc90f51561b184c080553e1eb41f1e in qpid-proton's branch refs/heads/master from Clifford Jansen [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=87ece50 ] PROTON-1026: Fix core dump. Code is treating cooked event as a raw one. But also doing both delegated and default actions instead of just the former (there is always a delegate). > Invalid queue/destination causes a segmentation fault > - > > Key: PROTON-1026 > URL: https://issues.apache.org/jira/browse/PROTON-1026 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Affects Versions: 0.11 > Environment: Fedora Linux 22, 64bit. > > Using built-in specs. > COLLECT_GCC=/usr/bin/gcc > COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/5.1.1/lto-wrapper > Target: x86_64-redhat-linux > Configured with: ../configure --enable-bootstrap > --enable-languages=c,c++,objc,obj-c++,fortran,ada,go,lto --prefix=/usr > --mandir=/usr/share/man --infodir=/usr/share/info > --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-shared > --enable-threads=posix --enable-checking=release --enable-multilib > --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions > --enable-gnu-unique-object --enable-linker-build-id > --with-linker-hash-style=gnu --enable-plugin --enable-initfini-array > --disable-libgcj --with-default-libstdcxx-abi=c++98 --with-isl > --enable-libmpx --enable-gnu-indirect-function --with-tune=generic > --with-arch_32=i686 --build=x86_64-redhat-linux > Thread model: posix > gcc version 5.1.1 20150618 (Red Hat 5.1.1-4) (GCC) > > Compiled with: > cmake -DCMAKE_INSTALL_PREFIX=/opt/devel/qpid-proton-0.11-SNAPSHOT > -DSYSINSTALL_BINDINGS=ON -DBUILD_PYTHON=OFF -DBUILD_PERL=OFF .. > --- >Reporter: Otavio Rodolfo Piske >Assignee: Cliff Jansen >Priority: Critical > Labels: crash > Fix For: 0.12.0 > > Attachments: proton-1026-backtrace.txt > > > Using an invalid path/destination in the address causes the code to crash > with SIGSEGV. > Having the QPid Proton code compiled, please use these teps to reproduce: > 1. Configure a broker > 2. Use the server example to send a message to a non-existent queue: > ./server -a server_address:5672/this_destination_does_no_exist -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (PROTON-1026) Invalid queue/destination causes a segmentation fault
[ https://issues.apache.org/jira/browse/PROTON-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Cliff Jansen closed PROTON-1026. Resolution: Fixed > Invalid queue/destination causes a segmentation fault > - > > Key: PROTON-1026 > URL: https://issues.apache.org/jira/browse/PROTON-1026 > Project: Qpid Proton > Issue Type: Bug > Components: cpp-binding >Affects Versions: 0.11 > Environment: Fedora Linux 22, 64bit. > > Using built-in specs. > COLLECT_GCC=/usr/bin/gcc > COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/5.1.1/lto-wrapper > Target: x86_64-redhat-linux > Configured with: ../configure --enable-bootstrap > --enable-languages=c,c++,objc,obj-c++,fortran,ada,go,lto --prefix=/usr > --mandir=/usr/share/man --infodir=/usr/share/info > --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-shared > --enable-threads=posix --enable-checking=release --enable-multilib > --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions > --enable-gnu-unique-object --enable-linker-build-id > --with-linker-hash-style=gnu --enable-plugin --enable-initfini-array > --disable-libgcj --with-default-libstdcxx-abi=c++98 --with-isl > --enable-libmpx --enable-gnu-indirect-function --with-tune=generic > --with-arch_32=i686 --build=x86_64-redhat-linux > Thread model: posix > gcc version 5.1.1 20150618 (Red Hat 5.1.1-4) (GCC) > > Compiled with: > cmake -DCMAKE_INSTALL_PREFIX=/opt/devel/qpid-proton-0.11-SNAPSHOT > -DSYSINSTALL_BINDINGS=ON -DBUILD_PYTHON=OFF -DBUILD_PERL=OFF .. > --- >Reporter: Otavio Rodolfo Piske >Assignee: Cliff Jansen >Priority: Critical > Labels: crash > Fix For: 0.12.0 > > Attachments: proton-1026-backtrace.txt > > > Using an invalid path/destination in the address causes the code to crash > with SIGSEGV. > Having the QPid Proton code compiled, please use these teps to reproduce: > 1. Configure a broker > 2. Use the server example to send a message to a non-existent queue: > ./server -a server_address:5672/this_destination_does_no_exist -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PROTON-1080) have container attribute on any relevant event
[ https://issues.apache.org/jira/browse/PROTON-1080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058915#comment-15058915 ] ASF subversion and git services commented on PROTON-1080: - Commit 7ccd632974cc643030a8580ca72da645f6a22766 in qpid-proton's branch refs/heads/master from [~gsim] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=7ccd632 ] PROTON-1080: add alias for reactor when using any Reactor subclass > have container attribute on any relevant event > -- > > Key: PROTON-1080 > URL: https://issues.apache.org/jira/browse/PROTON-1080 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: 0.11 >Reporter: Gordon Sim >Assignee: Gordon Sim > Fix For: 0.12.0 > > > At present event.container is an alias for event.reactor only for the > on_start() event (and obviously only when a Container instance is actually > being used). It would be nicer to make that alias available on all events. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PROTON-1049) Reactor needs an alternative to using the URL to pass user authentication information.
[ https://issues.apache.org/jira/browse/PROTON-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058916#comment-15058916 ] ASF subversion and git services commented on PROTON-1049: - Commit fefb81d2c506074cbb6d1eea9d8432ddd3e1fa53 in qpid-proton's branch refs/heads/master from [~gsim] [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=fefb81d ] PROTON-1049: allow username/password to be specified on conatiner or via keyword args to connect() method > Reactor needs an alternative to using the URL to pass user authentication > information. > -- > > Key: PROTON-1049 > URL: https://issues.apache.org/jira/browse/PROTON-1049 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: 0.11 >Reporter: Ken Giusti >Assignee: Gordon Sim >Priority: Blocker > Fix For: 0.12.0 > > > When creating a connection using the Container class, the only way to specify > the username/password credentials is via the URL. This may cause the > credentials to be leaked via the "ps" command if the URL is passed via a > command line argument. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
