[jira] [Commented] (DISPATCH-1776) HTTP/2 - grpc call causes segfault

[ https://issues.apache.org/jira/browse/DISPATCH-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17231859#comment-17231859 ] ASF subversion and git services commented on DISPATCH-1776: ---

[jira] [Commented] (DISPATCH-1786) system_tests_fallback_dest failing in test_31_switchover_local_interior_alt_remote_interior

[ https://issues.apache.org/jira/browse/DISPATCH-1786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17231808#comment-17231808 ] ASF subversion and git services commented on DISPATCH-1786: ---

[jira] [Commented] (DISPATCH-1836) Policy config file 'vhost' parsing fails; diagnostic message is poor

[ https://issues.apache.org/jira/browse/DISPATCH-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17231795#comment-17231795 ] Charles E. Rolke commented on DISPATCH-1836: Issue https://issues.apache.o

[jira] [Created] (DISPATCH-1836) Policy config file 'vhost' parsing fails; diagnostic message is poor

Charles E. Rolke created DISPATCH-1836: -- Summary: Policy config file 'vhost' parsing fails; diagnostic message is poor Key: DISPATCH-1836 URL: https://issues.apache.org/jira/browse/DISPATCH-1836

[jira] [Commented] (PROTON-2297) [j] CompositeReadableBuffer UTF8 decode can fail if encoding crosses array boundaries

[ https://issues.apache.org/jira/browse/PROTON-2297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17231681#comment-17231681 ] ASF subversion and git services commented on PROTON-2297: - Commi

[jira] [Created] (PROTON-2302) c_threaderciser does not build on Windows

Jiri Daněk created PROTON-2302: -- Summary: c_threaderciser does not build on Windows Key: PROTON-2302 URL: https://issues.apache.org/jira/browse/PROTON-2302 Project: Qpid Proton Issue Type: Test

[jira] [Resolved] (DISPATCH-1832) deleting http/tcp listener/connectors causes segfault

[ https://issues.apache.org/jira/browse/DISPATCH-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim resolved DISPATCH-1832. -- Resolution: Fixed > deleting http/tcp listener/connectors causes segfault >

[jira] [Updated] (PROTON-2293) [c] Proactor: Raw connection wakes can crash the application

[ https://issues.apache.org/jira/browse/PROTON-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-2293: --- Affects Version/s: proton-c-0.32.0 > [c] Proactor: Raw connection wakes can crash the applic

[jira] [Updated] (PROTON-2301) [c] Proactor: badly timed raw connection wakes can still crash the application

[ https://issues.apache.org/jira/browse/PROTON-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-2301: --- Affects Version/s: proton-c-0.33.0 > [c] Proactor: badly timed raw connection wakes can stil

[jira] [Commented] (PROTON-2293) [c] Proactor: Raw connection wakes can crash the application

[ https://issues.apache.org/jira/browse/PROTON-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17231404#comment-17231404 ] Robbie Gemmell commented on PROTON-2293: Followup changes were made in PROTON-23

[jira] [Updated] (PROTON-2301) [c] Proactor: badly timed raw connection wakes can still crash the application

[ https://issues.apache.org/jira/browse/PROTON-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-2301: --- Fix Version/s: proton-c-0.34.0 > [c] Proactor: badly timed raw connection wakes can still cr

[jira] [Updated] (PROTON-2301) [c] Proactor: badly timed raw connection wakes can still crash the application

[ https://issues.apache.org/jira/browse/PROTON-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robbie Gemmell updated PROTON-2301: --- Description: This follows up with additional changes to those in PROTON-2293 > [c] Proactor:

[jira] [Updated] (QPID-8486) Upgrade legacy JMS client version

[ https://issues.apache.org/jira/browse/QPID-8486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8486: - Description: The legacy JMS client for AMQP 0-x version in use is an older version. This has to be upgrade

[jira] [Commented] (QPID-8486) Upgrade JMS client version

[ https://issues.apache.org/jira/browse/QPID-8486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17231364#comment-17231364 ] Alex Rudyy commented on QPID-8486: -- Hi [~DedeepyaT], [~robbie] is right. The release bran

[jira] [Updated] (QPID-8486) Upgrade legacy JMS client version

[ https://issues.apache.org/jira/browse/QPID-8486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Rudyy updated QPID-8486: - Summary: Upgrade legacy JMS client version (was: Upgrade JMS client version) > Upgrade legacy JMS client