[jira] [Commented] (QPIDJMS-389) JMS 2.0 Async CompletionListener can be notified in error

[ https://issues.apache.org/jira/browse/QPIDJMS-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16506713#comment-16506713 ] ASF subversion and git services commented on QPIDJMS-389: - Commit

[jira] [Commented] (DISPATCH-976) Allow policy for sources and targets to handle multiple wildcards

[ https://issues.apache.org/jira/browse/DISPATCH-976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16506544#comment-16506544 ] ASF GitHub Bot commented on DISPATCH-976: - GitHub user fgiorgetti opened a pull request:

[GitHub] qpid-dispatch pull request #320: DISPATCH-976 - System test to validate vhos...

GitHub user fgiorgetti opened a pull request: https://github.com/apache/qpid-dispatch/pull/320 DISPATCH-976 - System test to validate vhost policies on source and t… …arget addresses NOTE: If this gets merged before PR#319 and before DISPATCH-1026 is fixed (no PR

[jira] [Updated] (QPIDJMS-391) Add support for SSL provider netty-tcnative-boringssl-static

[ https://issues.apache.org/jira/browse/QPIDJMS-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated QPIDJMS-391: - Priority: Minor (was: Major) > Add support for SSL provider netty-tcnative-boringssl-static >

[jira] [Created] (QPIDJMS-391) Add support for SSL provider netty-tcnative-boringssl-static

Johan Stenberg created QPIDJMS-391: -- Summary: Add support for SSL provider netty-tcnative-boringssl-static Key: QPIDJMS-391 URL: https://issues.apache.org/jira/browse/QPIDJMS-391 Project: Qpid JMS

[jira] [Updated] (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:all-tabpanel ] Alex Rudyy updated QPID-8207: - Status: Reviewable (was: In Progress) > [Broker-J] Flow to disk might not be triggered in some

[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=16506287#comment-16506287 ] ASF subversion and git services commented on QPID-8207: --- Commit

[jira] [Updated] (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:all-tabpanel ] Alex Rudyy updated QPID-8207: - Attachment: 0001-QPID-8207-Broker-J-Fix-evaluation-of-flow-to-disk-th.patch > [Broker-J] Flow to disk

[jira] [Commented] (QPIDJMS-390) Use Atomic Field Updater for case where we create many AtomicBoolean instances

[ https://issues.apache.org/jira/browse/QPIDJMS-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16506279#comment-16506279 ] ASF subversion and git services commented on QPIDJMS-390: - Commit

[jira] [Updated] (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:all-tabpanel ] Alex Rudyy updated QPID-8207: - Summary: [Broker-J] Flow to disk might not be triggered in some circumstances (was: [Broker-J] Flow to

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

[ https://issues.apache.org/jira/browse/QPID-8207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8207: - Summary: [Broker-J] Flow to disk might not be triggered in some situations (was: [Broker-J] Flow to disk

[jira] [Created] (QPIDJMS-390) Use Atomic Field Updater for case where we create many AtomicBoolean instances

Timothy Bish created QPIDJMS-390: Summary: Use Atomic Field Updater for case where we create many AtomicBoolean instances Key: QPIDJMS-390 URL: https://issues.apache.org/jira/browse/QPIDJMS-390

[jira] [Assigned] (QPID-8207) [Broker-J] Flow to disk might not be triggered for direct memory sizes above 3GB

[ https://issues.apache.org/jira/browse/QPID-8207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy reassigned QPID-8207: Assignee: Alex Rudyy > [Broker-J] Flow to disk might not be triggered for direct memory sizes

[jira] [Updated] (QPID-8207) [Broker-J] Flow to disk might not be triggered for direct memory sizes above 3GB

[ https://issues.apache.org/jira/browse/QPID-8207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8207: - Fix Version/s: qpid-java-broker-7.0.5 > [Broker-J] Flow to disk might not be triggered for direct memory

[jira] [Created] (QPID-8207) [Broker-J] Flow to disk might not be triggered for direct memory sizes above 3GB

Alex Rudyy created QPID-8207: Summary: [Broker-J] Flow to disk might not be triggered for direct memory sizes above 3GB Key: QPID-8207 URL: https://issues.apache.org/jira/browse/QPID-8207 Project: Qpid

[jira] [Updated] (QPID-8206) [linearstore] Deadlock possible in InactivityFireEvent if fire() is called at the same time as cancel()

[ https://issues.apache.org/jira/browse/QPID-8206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim van der Riet updated QPID-8206: --- Status: Reviewable (was: In Progress) > [linearstore] Deadlock possible in

[jira] [Commented] (QPID-8206) [linearstore] Deadlock possible in InactivityFireEvent if fire() is called at the same time as cancel()

[ https://issues.apache.org/jira/browse/QPID-8206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16506066#comment-16506066 ] ASF subversion and git services commented on QPID-8206: --- Commit

[jira] [Resolved] (PROTON-1857) [cpp] no access to AMQP connection offered/desired capabilities

[ https://issues.apache.org/jira/browse/PROTON-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Conway resolved PROTON-1857. - Resolution: Fixed > [cpp] no access to AMQP connection offered/desired capabilities >

[jira] [Commented] (PROTON-1857) [cpp] no access to AMQP connection offered/desired capabilities

[ https://issues.apache.org/jira/browse/PROTON-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16506050#comment-16506050 ] ASF subversion and git services commented on PROTON-1857: - Commit

[jira] [Commented] (PROTON-1833) [cpp] Crash on Windows after calling container::stop()

[ https://issues.apache.org/jira/browse/PROTON-1833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16505880#comment-16505880 ] VincentSa commented on PROTON-1833: --- same issues with version 0.23.0 : * Unit test 'c-proactor-tests'

[jira] [Updated] (DISPATCH-1027) Cannot connect to router using WS when amqp protocol is specified

[ https://issues.apache.org/jira/browse/DISPATCH-1027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Kornel updated DISPATCH-1027: --- Description: I cannot connect using websocket connection to router when http is enabled

[jira] [Created] (DISPATCH-1027) Cannot connect to router using WS when amqp protocol is specified

David Kornel created DISPATCH-1027: -- Summary: Cannot connect to router using WS when amqp protocol is specified Key: DISPATCH-1027 URL: https://issues.apache.org/jira/browse/DISPATCH-1027 Project: