[jira] [Commented] (PROTON-927) absolute-expiry-time and creation-time are encoded as 0 if not set

[ https://issues.apache.org/jira/browse/PROTON-927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16070060#comment-16070060 ] Gordon Sim commented on PROTON-927: --- Original commit was https://git-wip-us.apache.org/repos/asf?p=qpid

[jira] [Closed] (PROTON-1485) allow authentication against a remote server

[ https://issues.apache.org/jira/browse/PROTON-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim closed PROTON-1485. -- Resolution: Invalid Addressed by PROTON-1500 and DISPATCH-775. > allow authentication agai

Re: delete message from Queue through Java code

On 24/05/17 08:45, girishlc wrote: Hi Gordon, Thanks for the reply, Generally, messages are removed from the queue once they have been acknowledged by the consuming client. The default in JMS is (I believe) auto-acknowledge, so when your message listener's onMessage() returns, the library

Re: delete message from Queue through Java code

On 24/05/17 06:52, girish lc wrote: Hi Team, I need help in deleting the message from the Queue in Qpid through Java code. Current status: I am sending the messages to the Qpid Queue using JMS and from the Queue I'm reading the messages through read module and now I need to delete the

[jira] [Resolved] (PROTON-1488) Making Python server example more configurable

[ https://issues.apache.org/jira/browse/PROTON-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved PROTON-1488. Resolution: Fixed Fix Version/s: 0.18.0 > Making Python server example more configura

[jira] [Commented] (PROTON-1488) Making Python server example more configurable

[ https://issues.apache.org/jira/browse/PROTON-1488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16019844#comment-16019844 ] Gordon Sim commented on PROTON-1488: This is a good improvement. Just for the sake of consistency

[jira] [Commented] (DISPATCH-775) allow authentication against a remote server

[ https://issues.apache.org/jira/browse/DISPATCH-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014667#comment-16014667 ] Gordon Sim commented on DISPATCH-775: - WIP: https://reviews.apache.org/r/59352/ > al

[jira] [Commented] (PROTON-1485) allow authentication against a remote server

[ https://issues.apache.org/jira/browse/PROTON-1485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16014659#comment-16014659 ] Gordon Sim commented on PROTON-1485: WIP: https://reviews.apache.org/r/59351/ > allow authenticat

[jira] [Created] (PROTON-1485) allow authentication against a remote server

Gordon Sim created PROTON-1485: -- Summary: allow authentication against a remote server Key: PROTON-1485 URL: https://issues.apache.org/jira/browse/PROTON-1485 Project: Qpid Proton Issue Type

[jira] [Closed] (DISPATCH-776) allow authentication against a remote server

[ https://issues.apache.org/jira/browse/DISPATCH-776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim closed DISPATCH-776. --- Resolution: Invalid > allow authentication against a remote ser

[jira] [Created] (DISPATCH-776) allow authentication against a remote server

Gordon Sim created DISPATCH-776: --- Summary: allow authentication against a remote server Key: DISPATCH-776 URL: https://issues.apache.org/jira/browse/DISPATCH-776 Project: Qpid Dispatch Issue

[jira] [Created] (DISPATCH-775) allow authentication against a remote server

Gordon Sim created DISPATCH-775: --- Summary: allow authentication against a remote server Key: DISPATCH-775 URL: https://issues.apache.org/jira/browse/DISPATCH-775 Project: Qpid Dispatch Issue

[jira] [Commented] (PROTON-1466) Container.create_receiver() does not create all receivers with certain names

[ https://issues.apache.org/jira/browse/PROTON-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16003582#comment-16003582 ] Gordon Sim commented on PROTON-1466: A workaround in the meantime would be to use explicit link names

Re: Review Request 59108: PROTON-1466: proton-c mixing up links with names that are prefixes

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/59108/#review174377 --- Ship it! Ship It! - Gordon Sim On May 9, 2017, 8:24 p.m

[jira] [Resolved] (QPID-7693) SSL client socket leaks a file descriptor

[ https://issues.apache.org/jira/browse/QPID-7693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-7693. -- Resolution: Fixed > SSL client socket leaks a file descrip

Re: Review Request 57392: Avoid prototype socket for client SslSocket instances

/SslSocket.h 733a47a src/qpid/sys/ssl/SslSocket.cpp 731151c Diff: https://reviews.apache.org/r/57392/diff/2/ Changes: https://reviews.apache.org/r/57392/diff/1-2/ Testing --- Thanks, Gordon Sim

Re: Review Request 57392: Avoid prototype socket for client SslSocket instances

't want to spend ages analysing the implications, so kept it simple to fix the client leak quickly. - Gordon --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/57392/#review168176 --- On March 7, 2017, 7:42 p.m.

[jira] [Commented] (QPID-7693) SSL client socket leaks a file descriptor

[ https://issues.apache.org/jira/browse/QPID-7693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15900032#comment-15900032 ] Gordon Sim commented on QPID-7693: -- Suggested fix: https://reviews.apache.org/r/57392/ > SSL cli

Review Request 57392: Avoid prototype socket for client SslSocket instances

--- Thanks, Gordon Sim

[jira] [Created] (QPID-7693) SSL client socket leaks a file descriptor

Gordon Sim created QPID-7693: Summary: SSL client socket leaks a file descriptor Key: QPID-7693 URL: https://issues.apache.org/jira/browse/QPID-7693 Project: Qpid Issue Type: Bug Affects

Re: Review Request 56993: QPID-7677: C++ broker AMQP 1.0 subscription uses more memory than 0-10

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/56993/#review166562 --- Ship it! Ship It! - Gordon Sim On Feb. 23, 2017, 6:39 p.m

[jira] [Resolved] (DISPATCH-195) Router does not support transactional messages

[ https://issues.apache.org/jira/browse/DISPATCH-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved DISPATCH-195. - Resolution: Fixed Fix Version/s: 0.8.0 > Router does not support transactional messa

[jira] [Commented] (DISPATCH-195) Router does not support transactional messages

[ https://issues.apache.org/jira/browse/DISPATCH-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15858206#comment-15858206 ] Gordon Sim commented on DISPATCH-195: - Proposed fix for link routed propagation of transaction

Re: Review Request 55585: ensure sasl layer is decrypted when necessary

es before it receives the > > outcome. On first impression, this seems like it shouldn't happen! > > > > Having said that, this fix looks basically good, although I'd love to be > > able to simplify the logic somehow. > > Gordon Sim wrote: > The client doe

Re: Review Request 55585: ensure sasl layer is decrypted when necessary

reliably (i.e. while ./simple_send.py -a guest:guest@localhost -m 1; do echo ok; done against qpidd, with only DIGEST-MD5 allowed). Thanks, Gordon Sim

Re: Review Request 55585: ensure sasl layer is decrypted when necessary

es before it receives the > > outcome. On first impression, this seems like it shouldn't happen! > > > > Having said that, this fix looks basically good, although I'd love to be > > able to simplify the logic somehow. > > Gordon Sim wrote: > The client doe

[jira] [Created] (PROTON-1388) client fails to decrypt after sasl encryption is negotiated with qpidd

Gordon Sim created PROTON-1388: -- Summary: client fails to decrypt after sasl encryption is negotiated with qpidd Key: PROTON-1388 URL: https://issues.apache.org/jira/browse/PROTON-1388 Project: Qpid

Re: Review Request 55585: ensure sasl layer is decrypted when necessary

d e-mail. To reply, visit: https://reviews.apache.org/r/55585/#review161793 ------- On Jan. 16, 2017, 7:55 p.m., Gordon Sim wrote: > > --- > This is an a

Re: Review Request 55585: ensure sasl layer is decrypted when necessary

This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/55585/#review161793 ----------- On Jan. 16, 2017, 7:55 p.m., Gordon Sim wrote: > >

Review Request 55585: ensure sasl layer is decrypted when necessary

DIGEST-MD5 allowed). Thanks, Gordon Sim

[jira] [Closed] (QPID-7596) client-server example from proton python doesn't work

[ https://issues.apache.org/jira/browse/QPID-7596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim closed QPID-7596. Resolution: Duplicate > client-server example from proton python doesn't w

[jira] [Created] (QPID-7596) client-server example from proton python doesn't work

Gordon Sim created QPID-7596: Summary: client-server example from proton python doesn't work Key: QPID-7596 URL: https://issues.apache.org/jira/browse/QPID-7596 Project: Qpid Issue Type: Bug

Re: AMQP 1.0/Python - Question re. encoding of maps and lists : failing qpid_tests.broker_1_0.translation.TranslationTests.test_translate* against Java Broker

On 23/12/16 08:34, Keith W wrote: On 22 December 2016 at 12:11, Gordon Sim <g...@redhat.com> wrote: On 21/12/16 17:51, Keith W wrote: I believed that Python Messaging derived its AMQP 1.0 support by way of the swigged client. Are we saying this is deprecated? It is more that it has

Re: AMQP 1.0/Python - Question re. encoding of maps and lists : failing qpid_tests.broker_1_0.translation.TranslationTests.test_translate* against Java Broker

On 21/12/16 17:51, Keith W wrote: I believed that Python Messaging derived its AMQP 1.0 support by way of the swigged client. Are we saying this is deprecated? It is more that it has never been considered a recommended client. It was just something we used in testing. If so, what is the

Re: AMQP 1.0/Python - Question re. encoding of maps and lists : failing qpid_tests.broker_1_0.translation.TranslationTests.test_translate* against Java Broker

On 20/12/16 18:20, Keith W wrote: On 20 December 2016 at 10:14, Gordon Sim <g...@redhat.com> wrote: On 19/12/16 15:57, Keith W wrote: By debugging the Java Broker's translation module, I can see that the AMQP 1.0 publishing end is sending the map encoded within a DataSection. This sur

Re: AMQP 1.0/Python - Question re. encoding of maps and lists : failing qpid_tests.broker_1_0.translation.TranslationTests.test_translate* against Java Broker

On 19/12/16 15:57, Keith W wrote: By debugging the Java Broker's translation module, I can see that the AMQP 1.0 publishing end is sending the map encoded within a DataSection. This surprises me - I was expecting the application-data to be an amqp-value containing the map. The Java Broker

[jira] [Commented] (DISPATCH-595) dispositions propagated after link detach on link route

[ https://issues.apache.org/jira/browse/DISPATCH-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15748517#comment-15748517 ] Gordon Sim commented on DISPATCH-595: - In the second case the link has been detached with an error

[jira] [Updated] (DISPATCH-596) error is lost from rejected state in relayed disposition

[ https://issues.apache.org/jira/browse/DISPATCH-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated DISPATCH-596: Attachment: reject.py reproducer that created the trace in the description, just run against

[jira] [Created] (DISPATCH-596) error is lost from rejected state in relayed disposition

Gordon Sim created DISPATCH-596: --- Summary: error is lost from rejected state in relayed disposition Key: DISPATCH-596 URL: https://issues.apache.org/jira/browse/DISPATCH-596 Project: Qpid Dispatch

[jira] [Created] (DISPATCH-595) dispositions propagated after link detach on link route

Gordon Sim created DISPATCH-595: --- Summary: dispositions propagated after link detach on link route Key: DISPATCH-595 URL: https://issues.apache.org/jira/browse/DISPATCH-595 Project: Qpid Dispatch

[jira] [Updated] (QPID-7236) Uninitialised values in AclRule

[ https://issues.apache.org/jira/browse/QPID-7236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated QPID-7236: - Fix Version/s: (was: qpid-cpp-1.36.0) > Uninitialised values in AclR

[jira] [Commented] (PROTON-1140) [proton-c] Always set process name and process id as connection properties

[ https://issues.apache.org/jira/browse/PROTON-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15729235#comment-15729235 ] Gordon Sim commented on PROTON-1140: For me, the engine is supposed to be free from this sort

[jira] [Comment Edited] (PROTON-1140) [proton-c] Always set process name and process id as connection properties

[ https://issues.apache.org/jira/browse/PROTON-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15729092#comment-15729092 ] Gordon Sim edited comment on PROTON-1140 at 12/7/16 4:01 PM: - +1, I don't

[jira] [Commented] (PROTON-1140) [proton-c] Always set process name and process id as connection properties

[ https://issues.apache.org/jira/browse/PROTON-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15729092#comment-15729092 ] Gordon Sim commented on PROTON-1140: +1 > [proton-c] Always set process name and process

Re: Review Request 53876: add explicit sni option

in the open frame, this patch adds an explicit option. Diffs (updated) - proton-c/bindings/python/proton/reactor.py 3562aa9 Diff: https://reviews.apache.org/r/53876/diff/ Testing --- Thanks, Gordon Sim

Review Request 53876: add explicit sni option

an explicit option. Diffs - proton-c/bindings/python/proton/reactor.py 3562aa9 Diff: https://reviews.apache.org/r/53876/diff/ Testing --- Thanks, Gordon Sim

[jira] [Resolved] (PROTON-1355) Allow controlling peer_hostname independently of connection url

[ https://issues.apache.org/jira/browse/PROTON-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved PROTON-1355. Resolution: Fixed Thanks Ulf! > Allow controlling peer_hostname independently of connection

[jira] [Resolved] (QPID-7500) [AMQP 1.0] session close is not synchronous

[ https://issues.apache.org/jira/browse/QPID-7500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-7500. -- Resolution: Fixed > [AMQP 1.0] session close is not synchron

[jira] [Resolved] (QPID-7501) [AMQP 1.0] sessions and links should be freed under lock

[ https://issues.apache.org/jira/browse/QPID-7501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-7501. -- Resolution: Fixed > [AMQP 1.0] sessions and links should be freed under l

[jira] [Created] (QPID-7501) [AMQP 1.0] sessions and links should be freed under lock

Gordon Sim created QPID-7501: Summary: [AMQP 1.0] sessions and links should be freed under lock Key: QPID-7501 URL: https://issues.apache.org/jira/browse/QPID-7501 Project: Qpid Issue Type: Bug

[jira] [Created] (QPID-7500) [AMQP 1.0] session close is not synchronous

Gordon Sim created QPID-7500: Summary: [AMQP 1.0] session close is not synchronous Key: QPID-7500 URL: https://issues.apache.org/jira/browse/QPID-7500 Project: Qpid Issue Type: Bug

[jira] [Created] (DISPATCH-551) disconnect connections that do not complete initial protocol handshake within a given time

Gordon Sim created DISPATCH-551: --- Summary: disconnect connections that do not complete initial protocol handshake within a given time Key: DISPATCH-551 URL: https://issues.apache.org/jira/browse/DISPATCH-551

[jira] [Commented] (QPID-6868) [AMQP 1.0 C++ Client] No errors for rejected messages.

[ https://issues.apache.org/jira/browse/QPID-6868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15530678#comment-15530678 ] Gordon Sim commented on QPID-6868: -- Fix proposed for QPID-7415 has now been committed to master

[jira] [Resolved] (QPID-7415) [AMQP 1.0]: reject, release & modified ignored by qpid::messaging

[ https://issues.apache.org/jira/browse/QPID-7415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-7415. -- Resolution: Fixed > [AMQP 1.0]: reject, release & modified ignored by qpid::me

[jira] [Closed] (QPID-6868) [AMQP 1.0 C++ Client] No errors for rejected messages.

[ https://issues.apache.org/jira/browse/QPID-6868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim closed QPID-6868. Resolution: Duplicate > [AMQP 1.0 C++ Client] No errors for rejected messa

[jira] [Reopened] (QPID-7431) Support for message-annotations

[ https://issues.apache.org/jira/browse/QPID-7431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim reopened QPID-7431: -- Assignee: Gordon Sim > Support for message-annotati

[jira] [Comment Edited] (QPID-7431) Support for message-annotations

[ https://issues.apache.org/jira/browse/QPID-7431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529411#comment-15529411 ] Gordon Sim edited comment on QPID-7431 at 9/28/16 12:14 PM: Messages

[jira] [Commented] (QPID-7431) Support for message-annotations

[ https://issues.apache.org/jira/browse/QPID-7431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15529411#comment-15529411 ] Gordon Sim commented on QPID-7431: -- Messages with annotations can be received through qpid::messaging

Re: Review Request 51638: handle reject and release in qpid::messaging

src/qpid/messaging/amqp/SenderContext.cpp fe8b4d3 src/qpid/messaging/amqp/SessionContext.h 67b3c1e src/qpid/messaging/amqp/SessionContext.cpp 92bdea7 src/qpid/messaging/amqp/Transaction.cpp 754b00d Diff: https://reviews.apache.org/r/51638/diff/ Testing --- Thanks, Gordon Sim

[jira] [Commented] (DISPATCH-500) name in conf file is not sent in response to management query

[ https://issues.apache.org/jira/browse/DISPATCH-500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15491102#comment-15491102 ] Gordon Sim commented on DISPATCH-500: - Ignore me! > name in conf file is not sent in respo

[jira] [Resolved] (QPID-7430) Allow qpid::messaging addresses to be passed through to server

[ https://issues.apache.org/jira/browse/QPID-7430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-7430. -- Resolution: Fixed > Allow qpid::messaging addresses to be passed through to ser

[jira] [Created] (QPID-7430) Allow qpid::messaging addresses to be passed through to server

Gordon Sim created QPID-7430: Summary: Allow qpid::messaging addresses to be passed through to server Key: QPID-7430 URL: https://issues.apache.org/jira/browse/QPID-7430 Project: Qpid Issue

[jira] [Created] (DISPATCH-510) handle amqp:link:redirect

Gordon Sim created DISPATCH-510: --- Summary: handle amqp:link:redirect Key: DISPATCH-510 URL: https://issues.apache.org/jira/browse/DISPATCH-510 Project: Qpid Dispatch Issue Type: Improvement

[jira] [Commented] (DISPATCH-502) Seeing unexpected values in management query response

[ https://issues.apache.org/jira/browse/DISPATCH-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15487820#comment-15487820 ] Gordon Sim commented on DISPATCH-502: - The issue here seems to be that the create request message

Re: Review Request 51638: handle reject and release in qpid::messaging

tries? yes - Gordon --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/51638/#review148511 --- On Sept. 7, 2016, 11:01 a.m., Go

[jira] [Commented] (DISPATCH-506) Detach with no "error" sent by router on client TCP connection dropped

[ https://issues.apache.org/jira/browse/DISPATCH-506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484267#comment-15484267 ] Gordon Sim commented on DISPATCH-506: - The router uses a separate session per link for any links

[jira] [Commented] (DISPATCH-506) Detach with no "error" sent by router on client TCP connection dropped

[ https://issues.apache.org/jira/browse/DISPATCH-506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484265#comment-15484265 ] Gordon Sim commented on DISPATCH-506: - I agree that a session end without any link close *should

[jira] [Commented] (DISPATCH-506) Detach with no "error" sent by router on client TCP connection dropped

[ https://issues.apache.org/jira/browse/DISPATCH-506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15483945#comment-15483945 ] Gordon Sim commented on DISPATCH-506: - I'm in favour of an explicit detach with a link error

[jira] [Created] (DISPATCH-501) router segfaults if you sent a management query with an empty body

Gordon Sim created DISPATCH-501: --- Summary: router segfaults if you sent a management query with an empty body Key: DISPATCH-501 URL: https://issues.apache.org/jira/browse/DISPATCH-501 Project: Qpid

[jira] [Created] (DISPATCH-500) name in conf file is not sent in response to management query

Gordon Sim created DISPATCH-500: --- Summary: name in conf file is not sent in response to management query Key: DISPATCH-500 URL: https://issues.apache.org/jira/browse/DISPATCH-500 Project: Qpid Dispatch

[jira] [Updated] (DISPATCH-499) in propagating link detach the info field is dropped

[ https://issues.apache.org/jira/browse/DISPATCH-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated DISPATCH-499: Attachment: DISPATCH-499.patch Simple fix. > in propagating link detach the info fi

[jira] [Created] (DISPATCH-499) in propagating link detach the info field is dropped

Gordon Sim created DISPATCH-499: --- Summary: in propagating link detach the info field is dropped Key: DISPATCH-499 URL: https://issues.apache.org/jira/browse/DISPATCH-499 Project: Qpid Dispatch

Re: Review Request 51638: handle reject and release in qpid::messaging

/51638/diff/ Testing --- Thanks, Gordon Sim

Re: Review Request 51638: handle reject and release in qpid::messaging

t; > <https://reviews.apache.org/r/51638/diff/3/?file=1492014#file1492014line54> > > > > Why memmove? Is it legal for two EncodedMessages to have overlapping > > buffers? If not this might be clearer: > > > > if (data != other.data) m

Re: Review Request 51638: handle reject and release in qpid::messaging

/reject > > then I think we need a clearly marked exception hierarchy so the user can > > tell which exceptions destroy the link/session/connection and which don't. > > Gordon Sim wrote: > None of these destroy the hierachy as viewed by the client. > > Alan Conway

Review Request 51665: add the ability to have qpid::messaging address string passed through to server when using AMQP 1.0

ba3220c src/qpid/messaging/amqp/ConnectionContext.cpp 25dd68d Diff: https://reviews.apache.org/r/51665/diff/ Testing --- Thanks, Gordon Sim

Re: Review Request 51638: handle reject and release in qpid::messaging

/messaging/amqp/Transaction.cpp 754b00d Diff: https://reviews.apache.org/r/51638/diff/ Testing --- Thanks, Gordon Sim

Re: Review Request 51638: handle reject and release in qpid::messaging

src/qpid/messaging/amqp/Transaction.cpp 754b00d Diff: https://reviews.apache.org/r/51638/diff/ Testing --- Thanks, Gordon Sim

Re: Review Request 51638: handle reject and release in qpid::messaging

This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/51638/#review147837 ----------- On Sept. 5, 2016, 7:58 p.m., Gordon Sim wrote: > > --- &g

[jira] [Commented] (QPID-7415) [AMQP 1.0]: reject, release & modified ignored by qpid::messaging

[ https://issues.apache.org/jira/browse/QPID-7415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15466851#comment-15466851 ] Gordon Sim commented on QPID-7415: -- https://reviews.apache.org/r/51638/ > [AMQP 1.0]: reject, rele

Review Request 51638: handle reject and release in qpid::messaging

/amqp/SenderContext.cpp fe8b4d3 src/qpid/messaging/amqp/SessionContext.h 67b3c1e src/qpid/messaging/amqp/SessionContext.cpp 92bdea7 src/qpid/messaging/amqp/Transaction.cpp 754b00d Diff: https://reviews.apache.org/r/51638/diff/ Testing --- Thanks, Gordon Sim

[jira] [Created] (QPID-7415) [AMQP 1.0]: reject, release & modified ignored by qpid::messaging

Gordon Sim created QPID-7415: Summary: [AMQP 1.0]: reject, release & modified ignored by qpid::messaging Key: QPID-7415 URL: https://issues.apache.org/jira/browse/QPID-7415 Project: Qpid I

[jira] [Resolved] (QPID-7302) race between auto-delete and re-declare/consume

[ https://issues.apache.org/jira/browse/QPID-7302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-7302. -- Resolution: Fixed Fix Version/s: (was: qpid-cpp-next) qpid-cpp-1.35.0

[jira] [Resolved] (QPID-7406) release doesn't reset cursors for active consumers on LVQ

[ https://issues.apache.org/jira/browse/QPID-7406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-7406. -- Resolution: Fixed > release doesn't reset cursors for active consumers on

[jira] [Closed] (QPID-7407) LVQ does not respect released or modified outcomes

[ https://issues.apache.org/jira/browse/QPID-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim closed QPID-7407. Resolution: Duplicate > LVQ does not respect released or modified outco

[jira] [Created] (QPID-7406) release doesn't reset cursors for active consumers on LVQ

Gordon Sim created QPID-7406: Summary: release doesn't reset cursors for active consumers on LVQ Key: QPID-7406 URL: https://issues.apache.org/jira/browse/QPID-7406 Project: Qpid Issue Type: Bug

Re: Review Request 51336: PROTON-1287: c++: missing empty() method on message_id, annotation_key

> On Aug. 23, 2016, 4:50 p.m., Andrew Stitcher wrote: > > proton-c/bindings/cpp/include/proton/message_id.hpp, line 45 > > > > > > This is an actual API change (even if it is a correct one). > > > > Can

Re: [jira] [Created] (PROTON-1283) Adds support for transport layers not currently implemented in the library

On 19/08/16 19:12, Andrew Buckley wrote: Hi all, I don't want this to get lost. Just thought I'd send out a ping. Our team would like to know any thoughts on this, whether it's something that might be able to go in, or if it's something that definitely will not so we can make some decisions

[jira] [Created] (DISPATCH-476) qualified link routing

Gordon Sim created DISPATCH-476: --- Summary: qualified link routing Key: DISPATCH-476 URL: https://issues.apache.org/jira/browse/DISPATCH-476 Project: Qpid Dispatch Issue Type: Improvement

[jira] [Resolved] (QPID-7391) qpid-receive doesn't always honor the routing key from the reply-to address when replying

[ https://issues.apache.org/jira/browse/QPID-7391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-7391. -- Resolution: Fixed Thanks Jakub! > qpid-receive doesn't always honor the routing key from the re

[jira] [Closed] (QPID-5337) Memory leak in python client - unacked messages kept when no accept is necessary

[ https://issues.apache.org/jira/browse/QPID-5337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim closed QPID-5337. Resolution: Won't Fix > Memory leak in python client - unacked messages kept when no accept is > nec

[jira] [Closed] (QPID-3456) Python and C++ clients behave differently

[ https://issues.apache.org/jira/browse/QPID-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim closed QPID-3456. Resolution: Won't Fix > Python and C++ clients behave differen

[jira] [Closed] (QPID-3179) Revisit exeptional cases and resulting state of sessions, senders, receivers etc.

[ https://issues.apache.org/jira/browse/QPID-3179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim closed QPID-3179. Resolution: Won't Fix > Revisit exeptional cases and resulting state of sessions, senders, receivers &g

[jira] [Commented] (QPID-5337) Memory leak in python client - unacked messages kept when no accept is necessary

[ https://issues.apache.org/jira/browse/QPID-5337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15415456#comment-15415456 ] Gordon Sim commented on QPID-5337: -- I think I didn't feel a strong urge to commit

[jira] [Commented] (QPID-5337) Memory leak in python client - unacked messages kept when no accept is necessary

[ https://issues.apache.org/jira/browse/QPID-5337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15415457#comment-15415457 ] Gordon Sim commented on QPID-5337: -- When I say close, I mean as 'wont fix'. > Memory leak in pyt

Re: Review Request 50863: Avoid costly context lookup in Event constructor.

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/50863/#review144975 --- Ship it! Ship It! - Gordon Sim On Aug. 5, 2016, 7:39 p.m

[jira] [Commented] (QPID-7233) qpid-receive uses 0 prefetch unless an explicit message count is provided

[ https://issues.apache.org/jira/browse/QPID-7233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15406238#comment-15406238 ] Gordon Sim commented on QPID-7233: -- See also QPID-7376 for a further special case. > qpid-receive use

[jira] [Resolved] (QPID-7376) fetch with capacity=0 can hang or timeout if fetched message expires client-side

[ https://issues.apache.org/jira/browse/QPID-7376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-7376. -- Resolution: Fixed > fetch with capacity=0 can hang or timeout if fetched message expires > clien

[jira] [Created] (QPID-7376) fetch with capacity=0 can hang or timeout if fetched message expires client-side

Gordon Sim created QPID-7376: Summary: fetch with capacity=0 can hang or timeout if fetched message expires client-side Key: QPID-7376 URL: https://issues.apache.org/jira/browse/QPID-7376 Project: Qpid

[jira] [Resolved] (QPID-7361) [AMQP-1.0] sender sometimes waits for credit without flushing buffered transfers to disk

[ https://issues.apache.org/jira/browse/QPID-7361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved QPID-7361. -- Resolution: Fixed > [AMQP-1.0] sender sometimes waits for credit without flushing buffered > tra

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