[jira] [Commented] (DISPATCH-1656) Allow user-configured connection properties in the Open performative

[ https://issues.apache.org/jira/browse/DISPATCH-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17107415#comment-17107415 ] Keith Wall commented on DISPATCH-1656: -- As the AMQP open field properties is of type fields[1

[jira] [Comment Edited] (DISPATCH-1656) Allow user-configured connection properties in the Open performative

[ https://issues.apache.org/jira/browse/DISPATCH-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17107415#comment-17107415 ] Keith Wall edited comment on DISPATCH-1656 at 5/14/20, 3:40 PM

[jira] [Commented] (DISPATCH-1635) Allow listener to specify an optional request for TLS client auth

[ https://issues.apache.org/jira/browse/DISPATCH-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17095331#comment-17095331 ] Keith Wall commented on DISPATCH-1635: -- I *think* delivering this might invoke a Proton API

[jira] [Created] (DISPATCH-1635) Allow listener to specify an optional request for TLS client auth

Keith Wall created DISPATCH-1635: Summary: Allow listener to specify an optional request for TLS client auth Key: DISPATCH-1635 URL: https://issues.apache.org/jira/browse/DISPATCH-1635 Project: Qpid

[jira] [Comment Edited] (DISPATCH-1634) Expose client X509 certificate identity (TLS client auth) to the auth service delegate

[ https://issues.apache.org/jira/browse/DISPATCH-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17095275#comment-17095275 ] Keith Wall edited comment on DISPATCH-1634 at 4/29/20, 9:20 AM

[jira] [Comment Edited] (DISPATCH-1634) Expose client X509 certificate identity (TLS client auth) to the auth service delegate

[ https://issues.apache.org/jira/browse/DISPATCH-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17095275#comment-17095275 ] Keith Wall edited comment on DISPATCH-1634 at 4/29/20, 9:18 AM

[jira] [Commented] (DISPATCH-1634) Expose client X509 certificate identity (TLS client auth) to the auth service delegate

[ https://issues.apache.org/jira/browse/DISPATCH-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17095275#comment-17095275 ] Keith Wall commented on DISPATCH-1634: -- In the case where the SASL EXTERNAL mechanism is selected

[jira] [Created] (DISPATCH-1634) Expose client X509 certificate identity (TLS client auth) to the auth service delegate

Keith Wall created DISPATCH-1634: Summary: Expose client X509 certificate identity (TLS client auth) to the auth service delegate Key: DISPATCH-1634 URL: https://issues.apache.org/jira/browse/DISPATCH-1634

[jira] [Commented] (DISPATCH-1439) Expose create time/last transfer time through the Connection management entity

[ https://issues.apache.org/jira/browse/DISPATCH-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16962089#comment-16962089 ] Keith Wall commented on DISPATCH-1439: -- [~tross] seconds since connection creation and seconds

[jira] [Commented] (DISPATCH-1409) Update qdstat -l output to include the current credit

[ https://issues.apache.org/jira/browse/DISPATCH-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16960877#comment-16960877 ] Keith Wall commented on DISPATCH-1409: -- I think a zero credit reached timestamp would need

[jira] [Created] (DISPATCH-1439) Expose create time/last transfer time through the Connection management entity

Keith Wall created DISPATCH-1439: Summary: Expose create time/last transfer time through the Connection management entity Key: DISPATCH-1439 URL: https://issues.apache.org/jira/browse/DISPATCH-1439

[jira] [Comment Edited] (DISPATCH-1414) Include source/target address in the policy DENY info messages

[ https://issues.apache.org/jira/browse/DISPATCH-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16926379#comment-16926379 ] Keith Wall edited comment on DISPATCH-1414 at 9/10/19 7:24 AM: --- Sorry

[jira] [Commented] (DISPATCH-1414) Include source/target address in the policy DENY info messages

[ https://issues.apache.org/jira/browse/DISPATCH-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16926379#comment-16926379 ] Keith Wall commented on DISPATCH-1414: -- Sorry - my error. I thought that '' was the link

[jira] [Created] (DISPATCH-1414) Include source/target address in the policy DENY info messages

Keith Wall created DISPATCH-1414: Summary: Include source/target address in the policy DENY info messages Key: DISPATCH-1414 URL: https://issues.apache.org/jira/browse/DISPATCH-1414 Project: Qpid

[jira] [Updated] (PROTON-1998) [Proton-J] Add SASL protocol trace

[ https://issues.apache.org/jira/browse/PROTON-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated PROTON-1998: --- Summary: [Proton-J] Add SASL protocol trace (was: [Proton-J] Add SASL proton trace) > [Proto

[jira] [Created] (PROTON-1998) [Proton-J] Add SASL proton trace

Keith Wall created PROTON-1998: -- Summary: [Proton-J] Add SASL proton trace Key: PROTON-1998 URL: https://issues.apache.org/jira/browse/PROTON-1998 Project: Qpid Proton Issue Type: Improvement

[jira] [Commented] (QPID-8269) [Broker-J] Enforce password complexity in authentication providers managing credentials

[ https://issues.apache.org/jira/browse/QPID-8269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16733407#comment-16733407 ] Keith Wall commented on QPID-8269: -- I think for production use-cases, Broker-J users ought

[jira] [Updated] (QPID-8245) [Broker-J] [AMQP 0-8..0-91] Decode FieldTable fields on demand

[ https://issues.apache.org/jira/browse/QPID-8245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8245: - Summary: [Broker-J] [AMQP 0-8..0-91] Decode FieldTable fields on demand (was: [Broker-J] [AMQP 0-8..0-91

[jira] [Commented] (QPID-8238) [Broker-J] Improve performance of asynchronous publishing of transient messages into topic exchange having queues bound using non-overlapping selectors

[ https://issues.apache.org/jira/browse/QPID-8238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16611738#comment-16611738 ] Keith Wall commented on QPID-8238: -- Hi Alex I think separating the work in separate JIRAs would help. I

[jira] [Commented] (QPID-8238) [Broker-J] Improve performance of asynchronous publishing of transient messages into topic exchange having queues bound using non-overlapping selectors

[ https://issues.apache.org/jira/browse/QPID-8238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16610224#comment-16610224 ] Keith Wall commented on QPID-8238: -- I think it would be better to separate the FieldTable optimisation

[jira] [Comment Edited] (QPID-8238) [Broker-J] Improve performance of asynchronous publishing of transient messages into topic exchange having queues bound using non-overlapping selectors

[ https://issues.apache.org/jira/browse/QPID-8238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16610224#comment-16610224 ] Keith Wall edited comment on QPID-8238 at 9/11/18 7:52 AM: --- I think it would

[jira] [Resolved] (QPID-8233) [Broker-J][AMQP 1.0] Failure on connecting to a virtual host which is not yet active should use connection-forced error

[ https://issues.apache.org/jira/browse/QPID-8233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8233. -- Resolution: Fixed > [Broker-J][AMQP 1.0] Failure on connecting to a virtual host which is not

[jira] [Commented] (QPID-8233) [Broker-J][AMQP 1.0] Failure on connecting to a virtual host which is not yet active should use connection-forced error

[ https://issues.apache.org/jira/browse/QPID-8233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16609815#comment-16609815 ] Keith Wall commented on QPID-8233: -- Looks reasonable to me. > [Broker-J][AMQP 1.0] Failure on connect

[jira] [Resolved] (QPID-8231) [Broker-J] [AMQP 0-8...0-9-1] Broker crashes on delivery of messages from queue having attribute 'messageGroupKeyOverride' set to an empty string

[ https://issues.apache.org/jira/browse/QPID-8231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8231. -- Resolution: Fixed > [Broker-J] [AMQP 0-8...0-9-1] Broker crashes on delivery of messages from >

[jira] [Commented] (QPID-8231) [Broker-J] [AMQP 0-8...0-9-1] Broker crashes on delivery of messages from queue having attribute 'messageGroupKeyOverride' set to an empty string

[ https://issues.apache.org/jira/browse/QPID-8231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16609806#comment-16609806 ] Keith Wall commented on QPID-8231: -- Looks reasonable to me. > [Broker-J] [AMQP 0-8...0-9-1] Bro

[jira] [Comment Edited] (QPID-8238) [Broker-J] Improve performance of asynchronous publishing of transient messages into topic exchange having queues bound using non-overlapping selectors

[ https://issues.apache.org/jira/browse/QPID-8238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598574#comment-16598574 ] Keith Wall edited comment on QPID-8238 at 8/31/18 10:50 AM:   Your comments

[jira] [Commented] (QPID-8238) [Broker-J] Improve performance of asynchronous publishing of transient messages into topic exchange having queues bound using non-overlapping selectors

[ https://issues.apache.org/jira/browse/QPID-8238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598574#comment-16598574 ] Keith Wall commented on QPID-8238: --   Your comments made me remember a investigation I made a few months

[jira] [Comment Edited] (QPID-8238) [Broker-J] Improve performance of asynchronous publishing of transient messages into topic exchange having queues bound using non-overlapping selectors

[ https://issues.apache.org/jira/browse/QPID-8238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16598574#comment-16598574 ] Keith Wall edited comment on QPID-8238 at 8/31/18 10:49 AM:   Your comments

[jira] [Resolved] (QPID-8229) [Broker-J][6.x] Queue bindings are not removed on queue deletion when BDB/DERBY/JDBC configuration stores are used

[ https://issues.apache.org/jira/browse/QPID-8229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8229. -- Resolution: Fixed > [Broker-J][6.x] Queue bindings are not removed on queue deletion when > BDB

[jira] [Commented] (QPID-8229) [Broker-J][6.x] Queue bindings are not removed on queue deletion when BDB/DERBY/JDBC configuration stores are used

[ https://issues.apache.org/jira/browse/QPID-8229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16597162#comment-16597162 ] Keith Wall commented on QPID-8229: -- Seems okay to me. > [Broker-J][6.x] Queue bindings are not remo

[jira] [Resolved] (QPID-8236) [Broker-J] Changing of group name, address or node name in BDB HA virtual host node should be disallowed

[ https://issues.apache.org/jira/browse/QPID-8236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8236. -- Resolution: Fixed > [Broker-J] Changing of group name, address or node name in BDB HA virtual >

[jira] [Commented] (QPID-8236) [Broker-J] Changing of group name, address or node name in BDB HA virtual host node should be disallowed

[ https://issues.apache.org/jira/browse/QPID-8236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16597154#comment-16597154 ] Keith Wall commented on QPID-8236: -- Change looks reasonable to me. > [Broker-J] Changing of group n

[jira] [Updated] (QPID-8231) [Broker-J] [AMQP 0-8...0-9-1] Broker crashes on delivery of messages from queue having attribute 'messageGroupKeyOverride' set to an empty string

[ https://issues.apache.org/jira/browse/QPID-8231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8231: - Summary: [Broker-J] [AMQP 0-8...0-9-1] Broker crashes on delivery of messages from queue having attribute

[jira] [Updated] (PROTON-1915) [Proton-J] Message codec encodes messageId values with types other than those permitted

[ https://issues.apache.org/jira/browse/PROTON-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated PROTON-1915: --- Description: The message codec (message format 0) codec of Proton-J is prepared to send {{message

[jira] [Updated] (PROTON-1915) [Proton-J] Message codec encodes messageId values with types other than those permitted

[ https://issues.apache.org/jira/browse/PROTON-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated PROTON-1915: --- Description: The message codec (message format 0) codec of Proton-J is prepared to send {{message

[jira] [Updated] (PROTON-1915) [Proton-J] Message codec encodes messageId values with types other than those permitted

[ https://issues.apache.org/jira/browse/PROTON-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated PROTON-1915: --- Description: The message codec (message format 0) codec of Proton-J is prepared to send {{message

[jira] [Updated] (PROTON-1915) [Proton-J] Message codec encodes messageId values with types other than those permitted

[ https://issues.apache.org/jira/browse/PROTON-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated PROTON-1915: --- Description: The message codec (message format 0) codec of Proton-J is prepared to send {{message

[jira] [Commented] (PROTON-1915) [Proton-J] Message codec encodes messageId values with types other than those permitted

[ https://issues.apache.org/jira/browse/PROTON-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16579462#comment-16579462 ] Keith Wall commented on PROTON-1915: >From a brief look at Proton-C, I would say Proto

[jira] [Updated] (PROTON-1915) [Proton-J] Message codec encodes messageId values with types other than those permitted

[ https://issues.apache.org/jira/browse/PROTON-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated PROTON-1915: --- Summary: [Proton-J] Message codec encodes messageId values with types other than those permitted

[jira] [Updated] (PROTON-1915) [Proton-J] Message codec encodes messageId values with types other than those permitted

[ https://issues.apache.org/jira/browse/PROTON-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated PROTON-1915: --- Description: The message codec (message format 0) codec of Proton-J is prepared to send {{message

[jira] [Created] (PROTON-1915) [Proton-J] Message codec encodes messageId values with types other than permitted

Keith Wall created PROTON-1915: -- Summary: [Proton-J] Message codec encodes messageId values with types other than permitted Key: PROTON-1915 URL: https://issues.apache.org/jira/browse/PROTON-1915

[jira] [Commented] (QPID-8227) [Broker-J] Replace qpidbrokerversion.properties with jar metadata

[ https://issues.apache.org/jira/browse/QPID-8227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16574426#comment-16574426 ] Keith Wall commented on QPID-8227: -- It is used when running Broker-J from classes rather than jars

[jira] [Commented] (DISPATCH-1086) Dispatch Router sporadically goes into a state where TLS connections to the auth service fail

[ https://issues.apache.org/jira/browse/DISPATCH-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16568067#comment-16568067 ] Keith Wall commented on DISPATCH-1086: -- I've spent considerable time trying to reproduce

[jira] [Comment Edited] (PROTON-1886) Expose diagnostic information from the openssl error queue when SSL_new fails.

[ https://issues.apache.org/jira/browse/PROTON-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16568060#comment-16568060 ] Keith Wall edited comment on PROTON-1886 at 8/3/18 10:25 AM: - Currently

[jira] [Commented] (PROTON-1886) Expose diagnostic information from the openssl error queue when SSL_new fails.

[ https://issues.apache.org/jira/browse/PROTON-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16568060#comment-16568060 ] Keith Wall commented on PROTON-1886: Currently if {{SSL_new}} fails, Proton does not record

[jira] [Updated] (PROTON-1905) CompositeReadableBuffer.duplicate seen to throw a NPE

[ https://issues.apache.org/jira/browse/PROTON-1905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated PROTON-1905: --- Description: Whilst verifying the RC1 candidate for the 0.27.3 RC1

[jira] [Updated] (PROTON-1905) CompositeReadableBuffer.duplicate seen to throw a NPE during frame logging

[ https://issues.apache.org/jira/browse/PROTON-1905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated PROTON-1905: --- Summary: CompositeReadableBuffer.duplicate seen to throw a NPE during frame logging

[jira] [Updated] (PROTON-1905) CompositeReadableBuffer.duplicate seen to throw a NPE

[ https://issues.apache.org/jira/browse/PROTON-1905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated PROTON-1905: --- Affects Version/s: (was: proton-j-0.27.3) > CompositeReadableBuffer.duplicate seen to th

[jira] [Updated] (PROTON-1905) CompositeReadableBuffer.duplicate seen to throw a NPE

[ https://issues.apache.org/jira/browse/PROTON-1905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated PROTON-1905: --- Affects Version/s: proton-j-0.27.0 proton-j-0.28.0

[jira] [Updated] (PROTON-1905) CompositeReadableBuffer.duplicate seen to throw a NPE

[ https://issues.apache.org/jira/browse/PROTON-1905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated PROTON-1905: --- Description: Whilst verifying the RC1 candidate for the 0.27.3 RC1

[jira] [Updated] (PROTON-1905) CompositeReadableBuffer.duplicate seen to throw a NPE

[ https://issues.apache.org/jira/browse/PROTON-1905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated PROTON-1905: --- Description: Whilst verifying the RC1 candidate for the 0.27.3 RC1

[jira] [Created] (PROTON-1905) CompositeReadableBuffer.duplicate seen to throw a NPE

Keith Wall created PROTON-1905: -- Summary: CompositeReadableBuffer.duplicate seen to throw a NPE Key: PROTON-1905 URL: https://issues.apache.org/jira/browse/PROTON-1905 Project: Qpid Proton

[jira] [Commented] (DISPATCH-1090) Transfer/Disposition(state=release) loop forms when application disconnects abruptly from brokered queue until link credit is exhausted.

[ https://issues.apache.org/jira/browse/DISPATCH-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16559985#comment-16559985 ] Keith Wall commented on DISPATCH-1090: -- It seems that in the case where there is no other

[jira] [Updated] (DISPATCH-1090) Transfer/Disposition(state=release) loop forms when application disconnects abruptly from brokered queue until link credit is exhausted.

[ https://issues.apache.org/jira/browse/DISPATCH-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated DISPATCH-1090: - Description: I have configured a single Dispatch Router instance to route messages through

[jira] [Updated] (DISPATCH-1090) Transfer/Disposition(state=release) loop forms when application disconnects abruptly from brokered queue until link credit is exhausted.

[ https://issues.apache.org/jira/browse/DISPATCH-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated DISPATCH-1090: - Environment: Version 1.3.0-SNAPSHOT

[jira] [Updated] (DISPATCH-1090) Transfer/Disposition(state=release) loop forms when application disconnects abruptly from brokered queue until link credit is exhausted.

[ https://issues.apache.org/jira/browse/DISPATCH-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated DISPATCH-1090: - Description: I have configured a single Dispatch Router instance to route messages through

[jira] [Updated] (DISPATCH-1090) Transfer/Disposition(state=release) loop forms when application disconnects abruptly from brokered queue until link credit is exhausted.

[ https://issues.apache.org/jira/browse/DISPATCH-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated DISPATCH-1090: - Attachment: DISPATCH-1090_dispatch_server.log > Transfer/Disposition(state=release) l

[jira] [Created] (DISPATCH-1090) Transfer/Disposition(state=release) loop forms when application disconnects abruptly from brokered queue until link credit is exhausted.

Keith Wall created DISPATCH-1090: Summary: Transfer/Disposition(state=release) loop forms when application disconnects abruptly from brokered queue until link credit is exhausted. Key: DISPATCH-1090 URL: https

[jira] [Created] (DISPATCH-1086) Dispatch Router sporadically goes into a state where TLS connections to the auth service fail

Keith Wall created DISPATCH-1086: Summary: Dispatch Router sporadically goes into a state where TLS connections to the auth service fail Key: DISPATCH-1086 URL: https://issues.apache.org/jira/browse/DISPATCH-1086

[jira] [Commented] (QPID-8219) [Broker-J] Authentication results are cached in SimpleLdap Authentication provider per connection basis

[ https://issues.apache.org/jira/browse/QPID-8219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16546328#comment-16546328 ] Keith Wall commented on QPID-8219: -- Wouldn't this problem also affect OAuth2AuthenticationProvider which

[jira] [Commented] (QPID-8212) [JMS AMQP 0-x][AMQP 0-8..0-91] Consumer close can block for 60 seconds and endup in time-out exception

[ https://issues.apache.org/jira/browse/QPID-8212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16534863#comment-16534863 ] Keith Wall commented on QPID-8212: -- I can't say that addition of the new method to AMQSession

[jira] [Created] (PROTON-1886) Expose diagnostic information from the openssl error queue when SSL_new fails.

Keith Wall created PROTON-1886: -- Summary: Expose diagnostic information from the openssl error queue when SSL_new fails. Key: PROTON-1886 URL: https://issues.apache.org/jira/browse/PROTON-1886 Project

[jira] [Updated] (QPID-8213) [Broker-J] InputStream is not closed in SSLUtil#readCertificates(URL)

[ https://issues.apache.org/jira/browse/QPID-8213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8213: - Priority: Minor (was: Major) > [Broker-J] InputStream is not closed in SSLUtil#readCertificates(

[jira] [Resolved] (QPID-8213) [Broker-J] InputStream is not closed in SSLUtil#readCertificates(URL)

[ https://issues.apache.org/jira/browse/QPID-8213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8213. -- Resolution: Fixed Fix Version/s: qpid-java-broker-7.1.0 > [Broker-J] InputStream is not clo

[jira] [Commented] (QPID-8213) [Broker-J] InputStream is not closed in SSLUtil#readCertificates(URL)

[ https://issues.apache.org/jira/browse/QPID-8213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524951#comment-16524951 ] Keith Wall commented on QPID-8213: -- Change looks good to me. I noticed qpid-jms-amqp-0-x had the same

Re: Review Request 67678: when indicating a routed link has been detached due to loss of connection, set close flag based on ability of terminus to survive disconnection

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/67678/#review205155 --- Looks good to me. - Keith Wall On June 20, 2018, 9:29 p.m

[jira] [Commented] (QPID-8210) [Broker-J] Consumer attach when message is being released and requeued can end-up in broker crash due to unhandled NullPointerException

[ https://issues.apache.org/jira/browse/QPID-8210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517872#comment-16517872 ] Keith Wall commented on QPID-8210: -- Changes look good. > [Broker-J] Consumer attach when mess

[jira] [Commented] (QPID-8210) [Broker-J] Consumer attach when message is being released and requeued can end-up in broker crash due to unhandled NullPointerException

[ https://issues.apache.org/jira/browse/QPID-8210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517867#comment-16517867 ] Keith Wall commented on QPID-8210: -- In addition the following cherry picks into 7.0.x are missing from

[jira] [Resolved] (QPID-8210) [Broker-J] Consumer attach when message is being released and requeued can end-up in broker crash due to unhandled NullPointerException

[ https://issues.apache.org/jira/browse/QPID-8210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8210. -- Resolution: Fixed > [Broker-J] Consumer attach when message is being released and requeued can &g

[jira] [Updated] (QPID-8210) [Broker-J] Consumer attach when message is being released and requeued can end-up in broker crash due to unhandled NullPointerException

[ https://issues.apache.org/jira/browse/QPID-8210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8210: - Description: The consumer node is currently set after consumer is added into queue consumer manager

[jira] [Comment Edited] (QPID-8210) [Broker-J] Set queue consumer node before adding consumer into queue consumer manager

[ https://issues.apache.org/jira/browse/QPID-8210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517377#comment-16517377 ] Keith Wall edited comment on QPID-8210 at 6/19/18 6:00 PM: --- Change looks

[jira] [Comment Edited] (QPID-8210) [Broker-J] Set queue consumer node before adding consumer into queue consumer manager

[ https://issues.apache.org/jira/browse/QPID-8210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517377#comment-16517377 ] Keith Wall edited comment on QPID-8210 at 6/19/18 5:57 PM: --- Change looks

[jira] [Comment Edited] (QPID-8210) [Broker-J] Set queue consumer node before adding consumer into queue consumer manager

[ https://issues.apache.org/jira/browse/QPID-8210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517377#comment-16517377 ] Keith Wall edited comment on QPID-8210 at 6/19/18 5:56 PM: --- Change looks

[jira] [Commented] (QPID-8210) [Broker-J] Set queue consumer node before adding consumer into queue consumer manager

[ https://issues.apache.org/jira/browse/QPID-8210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16517377#comment-16517377 ] Keith Wall commented on QPID-8210: -- Change looks reasonable to me, but I notice

[jira] [Commented] (QPID-8208) [Broker-J] Improve unexpected exception handling for LDAP connections in SimpleLDAPAuthenticationProvider

[ https://issues.apache.org/jira/browse/QPID-8208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16508312#comment-16508312 ] Keith Wall commented on QPID-8208: -- Alex That looks to me to be a Java platform defect rather than

[jira] [Commented] (QPID-8207) [Broker-J] Flow to disk might not be triggered in some circumstances

[ https://issues.apache.org/jira/browse/QPID-8207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16507795#comment-16507795 ] Keith Wall commented on QPID-8207: -- Alex, the algebraic refactoring look good to me. > [Broker-J] F

[jira] [Commented] (QPID-8202) [Broker-J][AMQP 0-8...0-91] Large flowed to disk message can be re-loaded from store for every content chunk sent to the client

[ https://issues.apache.org/jira/browse/QPID-8202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16504619#comment-16504619 ] Keith Wall commented on QPID-8202: -- Changes look reasonable to me. > [Broker-J][AMQP 0-8...0-91] La

[jira] [Commented] (QPID-8204) [Broker-J] Add statistics to report the maximum size of incoming messages

[ https://issues.apache.org/jira/browse/QPID-8204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16504610#comment-16504610 ] Keith Wall commented on QPID-8204: -- Changes look reasonable to me. > [Broker-J] Add statistics to rep

[jira] [Comment Edited] (QPID-8203) [Broker-J][AMQP 0-9] Improve maximum message size check

[ https://issues.apache.org/jira/browse/QPID-8203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16503972#comment-16503972 ] Keith Wall edited comment on QPID-8203 at 6/7/18 7:43 AM: -- Production code change

[jira] [Comment Edited] (QPID-8204) [Broker-J] Add statistics to report the maximum size of incoming messages

[ https://issues.apache.org/jira/browse/QPID-8204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16504040#comment-16504040 ] Keith Wall edited comment on QPID-8204 at 6/7/18 7:42 AM

[jira] [Commented] (QPID-8204) [Broker-J] Add statistics to report the maximum size of incoming messages

[ https://issues.apache.org/jira/browse/QPID-8204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16504040#comment-16504040 ] Keith Wall commented on QPID-8204: -- Is the {{maxMessageSizeStatisticsEnabled}} switch really justifiable

[jira] [Commented] (QPID-8202) [Broker-J][AMQP 0-9] Large flowed to disk message can be re-loaded from store for every content chunk sent to the client

[ https://issues.apache.org/jira/browse/QPID-8202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16504028#comment-16504028 ] Keith Wall commented on QPID-8202: -- Isn't 6.1 affected by this problem too?  I haven't run the code

[jira] [Commented] (QPID-8203) [Broker-J][AMQP 0-9] Improve maximum message size check

[ https://issues.apache.org/jira/browse/QPID-8203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16503972#comment-16503972 ] Keith Wall commented on QPID-8203: -- Production code change (master.7.0.x) looked reasonable.   The new

[jira] [Resolved] (QPID-8203) [Broker-J][AMQP 0-9] Improve maximum message size check

[ https://issues.apache.org/jira/browse/QPID-8203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8203. -- Resolution: Fixed > [Broker-J][AMQP 0-9] Improve maximum message size ch

[jira] [Commented] (QPID-8204) [Broker-J] Add statistics to report the maximum size of incoming messages

[ https://issues.apache.org/jira/browse/QPID-8204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16503478#comment-16503478 ] Keith Wall commented on QPID-8204: -- I am curious to understand the use-case for these new statistics

[jira] [Updated] (QPID-8201) [Broker-J] [AMQP1.0] Queue backing temporary subscription deleted twice during link close

[ https://issues.apache.org/jira/browse/QPID-8201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8201: - Description: Running the following code using the Qpid JMS Client (I am using master) that creates

[jira] [Updated] (QPID-8201) [Broker-J] [AMQP1.0] Queue backing temporary subscription deleted twice during link close

[ https://issues.apache.org/jira/browse/QPID-8201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8201: - Affects Version/s: qpid-java-broker-7.0.4 > [Broker-J] [AMQP1.0] Queue backing temporary subscript

[jira] [Updated] (QPID-8201) [Broker-J] Queue backing temporary subscription deleted twice during link close

[ https://issues.apache.org/jira/browse/QPID-8201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8201: - Description: Running the following code using the Qpid JMS Client (I am using master) that creates

[jira] [Updated] (QPID-8201) [Broker-J] [AMQP1.0] Queue backing temporary subscription deleted twice during link close

[ https://issues.apache.org/jira/browse/QPID-8201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8201: - Summary: [Broker-J] [AMQP1.0] Queue backing temporary subscription deleted twice during link close

[jira] [Created] (QPID-8201) [Broker-J] Queue backing temporary subscription deleted twice during link close

Keith Wall created QPID-8201: Summary: [Broker-J] Queue backing temporary subscription deleted twice during link close Key: QPID-8201 URL: https://issues.apache.org/jira/browse/QPID-8201 Project: Qpid

[jira] [Created] (DISPATCH-1020) Detach expiring links with closed=true when peer connectivity lost

Keith Wall created DISPATCH-1020: Summary: Detach expiring links with closed=true when peer connectivity lost Key: DISPATCH-1020 URL: https://issues.apache.org/jira/browse/DISPATCH-1020 Project: Qpid

[jira] [Commented] (QPID-8139) [Broker-J] [AMQP1-0] [JMSBINDMAP] JMS selectors using JMSMessageID or JMSCorrelationID expressed using the AMQP type encoded form values fail to select target message

[ https://issues.apache.org/jira/browse/QPID-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16492167#comment-16492167 ] Keith Wall commented on QPID-8139: -- I don't think the commit at {{f1ce866}} solves the problem. It has

[jira] [Updated] (QPID-8194) [Protocol Tests] [AMQP 1.0] TransferTests seen to fail on Windows

[ https://issues.apache.org/jira/browse/QPID-8194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8194: - Status: Reviewable (was: In Progress) > [Protocol Tests] [AMQP 1.0] TransferTests seen to fail on Wind

[jira] [Updated] (QPID-8194) [Protocol Tests] [AMQP 1.0] TransferTests seen to fail on Windows

[ https://issues.apache.org/jira/browse/QPID-8194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8194: - Priority: Minor (was: Major) > [Protocol Tests] [AMQP 1.0] TransferTests seen to fail on Wind

[jira] [Assigned] (QPID-8194) [Protocol Tests] [AMQP 1.0] TransferTests seen to fail on Windows

[ https://issues.apache.org/jira/browse/QPID-8194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall reassigned QPID-8194: Assignee: Keith Wall > [Protocol Tests] [AMQP 1.0] TransferTests seen to fail on Wind

[jira] [Resolved] (QPID-8181) [Broker-J] Add statistics for a total number of connections established on AMQP port

[ https://issues.apache.org/jira/browse/QPID-8181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall resolved QPID-8181. -- Resolution: Fixed > [Broker-J] Add statistics for a total number of connections established on >

[jira] [Commented] (QPID-8181) [Broker-J] Add statistics for a total number of connections established on AMQP port

[ https://issues.apache.org/jira/browse/QPID-8181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16488068#comment-16488068 ] Keith Wall commented on QPID-8181: -- Changes look reasonable to me. > [Broker-J] Add statist

[jira] [Commented] (QPID-7153) Allow expired messages to be sent to DLQ

[ https://issues.apache.org/jira/browse/QPID-7153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483705#comment-16483705 ] Keith Wall commented on QPID-7153: -- One comment. If as a user I want the expired messages that that land

[jira] [Updated] (QPID-8194) [Protocol Tests] [AMQP 1.0] TransferTests seens to fail on Windows

[ https://issues.apache.org/jira/browse/QPID-8194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8194: - Summary: [Protocol Tests] [AMQP 1.0] TransferTests seens to fail on Windows (was: [Protocol Tests] [AMQP

[jira] [Updated] (QPID-8194) [Protocol Tests] [AMQP 1.0] TransferTests seen to fail on Windows

[ https://issues.apache.org/jira/browse/QPID-8194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keith Wall updated QPID-8194: - Summary: [Protocol Tests] [AMQP 1.0] TransferTests seen to fail on Windows (was: [Protocol Tests] [AMQP

  1   2   3   4   5   6   7   8   9   10   >