[jira] [Commented] (PROTON-1999) [c] Crash in pn_connection_finalize

[ https://issues.apache.org/jira/browse/PROTON-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16758319#comment-16758319 ] Jeremy commented on PROTON-1999: Hello [~ODelbeke] and [~cliffjansen], [~ODelbeke]: Bef

[jira] [Resolved] (PROTON-1917) [proton-c] the c++ proton consumer with retry should continue to retry if virtual host not active

[ https://issues.apache.org/jira/browse/PROTON-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy resolved PROTON-1917. Resolution: Fixed > [proton-c] the c++ proton consumer with retry should continue to retry if > virtual h

[jira] [Comment Edited] (PROTON-1999) [c] Crash in pn_connection_finalize

[ https://issues.apache.org/jira/browse/PROTON-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16758319#comment-16758319 ] Jeremy edited comment on PROTON-1999 at 2/1/19 1:59 PM: Hello [~

[jira] [Comment Edited] (PROTON-1999) [c] Crash in pn_connection_finalize

[ https://issues.apache.org/jira/browse/PROTON-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16758319#comment-16758319 ] Jeremy edited comment on PROTON-1999 at 2/1/19 1:55 PM: Hello [~

[jira] [Comment Edited] (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:comment-tabpanel&focusedCommentId=16739208#comment-16739208 ] Jeremy edited comment on PROTON-1615 at 1/10/19 8:54 AM: - Hello

[jira] [Comment Edited] (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:comment-tabpanel&focusedCommentId=16739208#comment-16739208 ] Jeremy edited comment on PROTON-1615 at 1/10/19 8:51 AM: - Hello

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16739208#comment-16739208 ] Jeremy commented on PROTON-1615: Hello [~aconway] A further analysis of the hello world

[jira] [Updated] (PROTON-1952) Add possibility to set link-credit in proton receiver API

[ https://issues.apache.org/jira/browse/PROTON-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy updated PROTON-1952: --- Description: In the amqp standard, [link-credit|http://docs.oasis-open.org/amqp/core/v1.0/cos01/amqp-core-t

[jira] [Updated] (PROTON-1952) Add possibility to set link-credit in proton receiver API

[ https://issues.apache.org/jira/browse/PROTON-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy updated PROTON-1952: --- Description: In the amqp standard, [link-credit|http://docs.oasis-open.org/amqp/core/v1.0/cos01/amqp-core-t

[jira] [Updated] (PROTON-1952) Add possibility to set link-credit in proton receiver API

[ https://issues.apache.org/jira/browse/PROTON-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy updated PROTON-1952: --- Description: In the amqp standard, [link-credit|http://docs.oasis-open.org/amqp/core/v1.0/cos01/amqp-core-t

[jira] [Updated] (PROTON-1952) Add possibility to set link-credit in proton receiver API

[ https://issues.apache.org/jira/browse/PROTON-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy updated PROTON-1952: --- Description: (was: We faced an issue with the idle timeout on linux. On windows, it seems to work. In o

[jira] [Created] (PROTON-1952) Add possibility to set link-credit in proton receiver API

Jeremy created PROTON-1952: -- Summary: Add possibility to set link-credit in proton receiver API Key: PROTON-1952 URL: https://issues.apache.org/jira/browse/PROTON-1952 Project: Qpid Proton Issue Typ

[jira] [Updated] (PROTON-1862) idle timeout not working on linux

[ https://issues.apache.org/jira/browse/PROTON-1862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy updated PROTON-1862: --- Summary: idle timeout not working on linux (was: on_connection_open is being called on linux without a con

[jira] [Updated] (PROTON-1862) on_connection_open is being called on linux without a connected remote peer

[ https://issues.apache.org/jira/browse/PROTON-1862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy updated PROTON-1862: --- Summary: on_connection_open is being called on linux without a connected remote peer (was: Idle timeout not

[jira] [Updated] (PROTON-1923) Closing the connection yields random behavior for a receiver with reconnect options, due to the specified idle timeout value

[ https://issues.apache.org/jira/browse/PROTON-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy updated PROTON-1923: --- Description: I have a test case, where I launch a mocked broker, that sends messages when a consumer is con

[jira] [Created] (PROTON-1923) Closing the connection yields random behavior for a receiver with reconnect options, due to the specified idle timeout value

Jeremy created PROTON-1923: -- Summary: Closing the connection yields random behavior for a receiver with reconnect options, due to the specified idle timeout value Key: PROTON-1923 URL: https://issues.apache.org/jira/brow

[jira] [Commented] (PROTON-1917) [proton-c] the c++ proton consumer with retry should continue to retry if virtual host not active

[ https://issues.apache.org/jira/browse/PROTON-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593598#comment-16593598 ] Jeremy commented on PROTON-1917: Hello [~rgodfrey] With the updated zip, the problem is

[jira] [Commented] (PROTON-1917) [proton-c] the c++ proton consumer with retry should continue to retry if virtual host not active

[ https://issues.apache.org/jira/browse/PROTON-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593281#comment-16593281 ] Jeremy commented on PROTON-1917: My bad. As I said, I was testing from a different host

[jira] [Commented] (PROTON-1917) [proton-c] the c++ proton consumer with retry should continue to retry if virtual host not active

[ https://issues.apache.org/jira/browse/PROTON-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16590468#comment-16590468 ] Jeremy commented on PROTON-1917: Hello [~rgodfrey] and [~gemmellr] I tested with the pa

[jira] [Commented] (PROTON-1917) [proton-c] the c++ proton consumer with retry should continue to retry if virtual host not active

[ https://issues.apache.org/jira/browse/PROTON-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16590031#comment-16590031 ] Jeremy commented on PROTON-1917: I am using broker-j version 7.0.3. > [proton-c] the c+

[jira] [Commented] (PROTON-1917) [proton-c] the c++ proton consumer with retry should continue to retry if virtual host not active

[ https://issues.apache.org/jira/browse/PROTON-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16589995#comment-16589995 ] Jeremy commented on PROTON-1917: Ok, so how do you propose we proceed? it is also worth

[jira] [Comment Edited] (PROTON-1917) [proton-c] the c++ proton consumer with retry should continue to retry if virtual host not active

[ https://issues.apache.org/jira/browse/PROTON-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16589943#comment-16589943 ] Jeremy edited comment on PROTON-1917 at 8/23/18 9:29 AM: - Indeed

[jira] [Comment Edited] (PROTON-1917) [proton-c] the c++ proton consumer with retry should continue to retry if virtual host not active

[ https://issues.apache.org/jira/browse/PROTON-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16589943#comment-16589943 ] Jeremy edited comment on PROTON-1917 at 8/23/18 9:25 AM: - Indeed

[jira] [Comment Edited] (PROTON-1917) [proton-c] the c++ proton consumer with retry should continue to retry if virtual host not active

[ https://issues.apache.org/jira/browse/PROTON-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16589943#comment-16589943 ] Jeremy edited comment on PROTON-1917 at 8/23/18 9:24 AM: - Indeed

[jira] [Updated] (PROTON-1917) [proton-c] the c++ proton consumer with retry should continue to retry if virtual host not active

[ https://issues.apache.org/jira/browse/PROTON-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy updated PROTON-1917: --- Description: I have a running broker, and a configured queue containing messages. I also have a consumer, w

[jira] [Comment Edited] (PROTON-1917) [proton-c] the c++ proton consumer with retry should continue to retry if virtual host not active

[ https://issues.apache.org/jira/browse/PROTON-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16589943#comment-16589943 ] Jeremy edited comment on PROTON-1917 at 8/23/18 9:14 AM: - Indeed

[jira] [Commented] (PROTON-1917) [proton-c] the c++ proton consumer with retry should continue to retry if virtual host not active

[ https://issues.apache.org/jira/browse/PROTON-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16589943#comment-16589943 ] Jeremy commented on PROTON-1917: Indeed, it is a broker-j. I agree that the problem is

[jira] [Updated] (PROTON-1917) [proton-c] When qpid broker is killed and started, the c++ proton consumer (with retry) is randomly exiting with an error

[ https://issues.apache.org/jira/browse/PROTON-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy updated PROTON-1917: --- Description: I have a running broker, and a configured queue containing messages. I also have a consumer, w

[jira] [Updated] (PROTON-1917) [proton-c] When qpid broker is killed and started, the c++ proton consumer (with retry) is randomly exiting with an error

[ https://issues.apache.org/jira/browse/PROTON-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy updated PROTON-1917: --- Description: I have a running broker, and a configured queue containing messages. I also have a consumer, w

[jira] [Updated] (PROTON-1917) [proton-c] When qpid broker is killed and started, the c++ proton consumer (with retry) is randomly exiting with an error

[ https://issues.apache.org/jira/browse/PROTON-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy updated PROTON-1917: --- Description: I have a running broker, and a configured queue and containing messages. I also have a consume

[jira] [Updated] (PROTON-1917) [proton-c] When qpid broker is killed and started, the c++ proton consumer (with retry) is randomly exiting with an error

[ https://issues.apache.org/jira/browse/PROTON-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy updated PROTON-1917: --- Description: I have a running broker, and a configured queue and containing messages. I also have a consume

[jira] [Updated] (PROTON-1917) [proton-c] When qpid broker is killed and started, the c++ proton consumer (with retry) is randomly exiting with an error

[ https://issues.apache.org/jira/browse/PROTON-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy updated PROTON-1917: --- Summary: [proton-c] When qpid broker is killed and started, the c++ proton consumer (with retry) is randomly

[jira] [Updated] (PROTON-1917) [proton-c] When qpid broker is killed and started, the c++ proton consumer (with retry) is randomly receiving an exception

[ https://issues.apache.org/jira/browse/PROTON-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy updated PROTON-1917: --- Description: I have a running broker, and a configured queue and containing messages. I also have a consume

[jira] [Created] (PROTON-1917) [proton-c] When qpid broker is killed and started, the c++ proton consumer (with retry) is randomly receiving an exception

Jeremy created PROTON-1917: -- Summary: [proton-c] When qpid broker is killed and started, the c++ proton consumer (with retry) is randomly receiving an exception Key: PROTON-1917 URL: https://issues.apache.org/jira/browse

[jira] [Updated] (PROTON-1899) Qpid proton reconnect_options.max_attempts is not inline with Qpid JMS failover.maxReconnectAttempts

[ https://issues.apache.org/jira/browse/PROTON-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy updated PROTON-1899: --- Description: In Qpid JMS, the default value of [failover.maxReconnectAttempts|https://qpid.apache.org/relea

[jira] [Updated] (PROTON-1899) Qpid proton reconnect_options.max_attempts is not inline with Qpid JMS failover.maxReconnectAttempts

[ https://issues.apache.org/jira/browse/PROTON-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy updated PROTON-1899: --- Description: In Qpid JMS, the default value of [failover.maxReconnectAttempts|https://qpid.apache.org/relea

[jira] [Updated] (PROTON-1899) Qpid proton reconnect_options.max_attempts is not inline with Qpid JMS failover.maxReconnectAttempts

[ https://issues.apache.org/jira/browse/PROTON-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy updated PROTON-1899: --- Description: In Qpid JMS, the default value of [failover.maxReconnectAttempts|https://qpid.apache.org/relea

[jira] [Updated] (PROTON-1899) Qpid proton reconnect_options.max_attempts is not inline with Qpid JMS failover.maxReconnectAttempts

[ https://issues.apache.org/jira/browse/PROTON-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy updated PROTON-1899: --- Affects Version/s: proton-c-0.22.0 > Qpid proton reconnect_options.max_attempts is not inline with Qpid JMS

[jira] [Created] (PROTON-1899) Qpid proton reconnect_options.max_attempts is not inline with Qpid JMS failover.maxReconnectAttempts

Jeremy created PROTON-1899: -- Summary: Qpid proton reconnect_options.max_attempts is not inline with Qpid JMS failover.maxReconnectAttempts Key: PROTON-1899 URL: https://issues.apache.org/jira/browse/PROTON-1899

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16541488#comment-16541488 ] Jeremy commented on PROTON-1615: Hello [~aconway] Our lsan and valgrind caught the leak

[jira] [Comment Edited] (PROTON-1862) Idle timeout not working on Linux

[ https://issues.apache.org/jira/browse/PROTON-1862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16524842#comment-16524842 ] Jeremy edited comment on PROTON-1862 at 6/27/18 9:50 AM: - Any up

[jira] [Commented] (PROTON-1862) Idle timeout not working on Linux

[ https://issues.apache.org/jira/browse/PROTON-1862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16524842#comment-16524842 ] Jeremy commented on PROTON-1862: Any updates as to when can this issue be addressed? I

[jira] [Updated] (PROTON-1862) Idle timeout not working on Linux

[ https://issues.apache.org/jira/browse/PROTON-1862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy updated PROTON-1862: --- Description: We faced an issue with the idle timeout on linux. On windows, it seems to work. In our proton

[jira] [Updated] (PROTON-1862) Idle timeout not working on Linux

[ https://issues.apache.org/jira/browse/PROTON-1862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy updated PROTON-1862: --- Description: We faced an issue with the idle timeout on Linux. On windows, it seems to work. In our proton

[jira] [Updated] (PROTON-1862) Idle timeout not working on Linux

[ https://issues.apache.org/jira/browse/PROTON-1862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy updated PROTON-1862: --- Description: We faced an issue with the idle timeout on Linux. On windows, it seems to work. On the session

[jira] [Updated] (PROTON-1862) Idle timeout not working on Linux

[ https://issues.apache.org/jira/browse/PROTON-1862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy updated PROTON-1862: --- Attachment: test_case.cpp > Idle timeout not working on Linux > - > >

[jira] [Created] (PROTON-1862) Idle timeout not working on Linux

Jeremy created PROTON-1862: -- Summary: Idle timeout not working on Linux Key: PROTON-1862 URL: https://issues.apache.org/jira/browse/PROTON-1862 Project: Qpid Proton Issue Type: Bug Compone

[jira] [Comment Edited] (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&focusedCommentId=16274549#comment-16274549 ] Jeremy edited comment on DISPATCH-878 at 12/1/17 3:55 PM: -- [~ac

[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&focusedCommentId=16274549#comment-16274549 ] Jeremy commented on DISPATCH-878: - [~aconway] Indeed, I'm aware of that. I did not clar

[jira] [Comment Edited] (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&focusedCommentId=16268982#comment-16268982 ] Jeremy edited comment on DISPATCH-878 at 11/28/17 4:17 PM: --- In

[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&focusedCommentId=16268982#comment-16268982 ] Jeremy commented on DISPATCH-878: - Indeed, at Murex, we use the qpid _java _broker and i

[jira] [Updated] (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:all-tabpanel ] Jeremy updated DISPATCH-878: Summary: qdrouterd should log real port if port 0 was specified for the listener port property in qdrouter

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

Jeremy created DISPATCH-878: --- Summary: qdrouterd logs real port if port 0 was specified for the listener port property in qdrouterd.conf Key: DISPATCH-878 URL: https://issues.apache.org/jira/browse/DISPATCH-878