[jira] [Resolved] (PROTON-2454) Singular body section not always cleared when bulk adding multiple sections

[ https://issues.apache.org/jira/browse/PROTON-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy A. Bish resolved PROTON-2454. - Resolution: Fixed > Singular body section not always cleared when bulk adding multiple

[jira] [Commented] (PROTON-2454) Singular body section not always cleared when bulk adding multiple sections

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

[jira] [Created] (PROTON-2454) Singular body section not always cleared when bulk adding multiple sections

Timothy A. Bish created PROTON-2454: --- Summary: Singular body section not always cleared when bulk adding multiple sections Key: PROTON-2454 URL: https://issues.apache.org/jira/browse/PROTON-2454

[jira] [Commented] (DISPATCH-1958) Qdstat throws exception when router compiled with `DQD_MEMORY_STATS=OFF`

[ https://issues.apache.org/jira/browse/DISPATCH-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437607#comment-17437607 ] ASF GitHub Bot commented on DISPATCH-1958: -- kgiusti commented on pull request #1416: URL:

[GitHub] [qpid-dispatch] kgiusti commented on pull request #1416: DISPATCH-1958: Fixed error in qdstat when memory stats are turned off…

kgiusti commented on pull request #1416: URL: https://github.com/apache/qpid-dispatch/pull/1416#issuecomment-957878563 hmmm... I wonder if it would be simpler to make QD_MEMORY_STATS non-configurable? IOW, get rid of the flag and just always provide memory statistics. It's pretty

[jira] [Commented] (DISPATCH-1958) Qdstat throws exception when router compiled with `DQD_MEMORY_STATS=OFF`

[ https://issues.apache.org/jira/browse/DISPATCH-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437606#comment-17437606 ] ASF GitHub Bot commented on DISPATCH-1958: -- ted-ross commented on pull request #1416: URL:

[GitHub] [qpid-dispatch] ted-ross commented on pull request #1416: DISPATCH-1958: Fixed error in qdstat when memory stats are turned off…

ted-ross commented on pull request #1416: URL: https://github.com/apache/qpid-dispatch/pull/1416#issuecomment-958124314 > > hmmm... I wonder if it would be simpler to make QD_MEMORY_STATS non-configurable? IOW, get rid of the flag and just always provide memory statistics. It's pretty

[jira] [Commented] (DISPATCH-1958) Qdstat throws exception when router compiled with `DQD_MEMORY_STATS=OFF`

[ https://issues.apache.org/jira/browse/DISPATCH-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437604#comment-17437604 ] ASF GitHub Bot commented on DISPATCH-1958: -- ganeshmurthy opened a new pull request #1416:

[jira] [Commented] (QPIDJMS-552) JMS 2 Completion threads shouldn't scale with the number of sessions

[ https://issues.apache.org/jira/browse/QPIDJMS-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437601#comment-17437601 ] ASF GitHub Bot commented on QPIDJMS-552: franz1981 edited a comment on pull request #44: URL:

[GitHub] [qpid-jms] franz1981 edited a comment on pull request #44: QPIDJMS-552 JMS 2 Completion threads shouldn't scale with the number of sessions

franz1981 edited a comment on pull request #44: URL: https://github.com/apache/qpid-jms/pull/44#issuecomment-957253435 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To

[jira] [Commented] (QPIDJMS-552) JMS 2 Completion threads shouldn't scale with the number of sessions

[ https://issues.apache.org/jira/browse/QPIDJMS-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437595#comment-17437595 ] ASF GitHub Bot commented on QPIDJMS-552: gemmellr commented on pull request #44: URL:

[GitHub] [qpid-jms] gemmellr commented on pull request #44: QPIDJMS-552 JMS 2 Completion threads shouldn't scale with the number of sessions

gemmellr commented on pull request #44: URL: https://github.com/apache/qpid-jms/pull/44#issuecomment-957323951 I think single completion at a time is the way to go, at least by default, it just shouldn't really be a concern when using it whether the callback execution is fair or not. --

[jira] [Commented] (QPIDJMS-552) JMS 2 Completion threads shouldn't scale with the number of sessions

[ https://issues.apache.org/jira/browse/QPIDJMS-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437593#comment-17437593 ] ASF GitHub Bot commented on QPIDJMS-552: franz1981 commented on pull request #44: URL:

[jira] [Commented] (DISPATCH-1958) Qdstat throws exception when router compiled with `DQD_MEMORY_STATS=OFF`

[ https://issues.apache.org/jira/browse/DISPATCH-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437591#comment-17437591 ] ASF GitHub Bot commented on DISPATCH-1958: -- ganeshmurthy commented on pull request #1416:

[GitHub] [qpid-jms] franz1981 commented on pull request #44: QPIDJMS-552 JMS 2 Completion threads shouldn't scale with the number of sessions

franz1981 commented on pull request #44: URL: https://github.com/apache/qpid-jms/pull/44#issuecomment-957253435 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To

[GitHub] [qpid-dispatch] ganeshmurthy commented on pull request #1416: DISPATCH-1958: Fixed error in qdstat when memory stats are turned off…

ganeshmurthy commented on pull request #1416: URL: https://github.com/apache/qpid-dispatch/pull/1416#issuecomment-957887593 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment.

[jira] [Commented] (DISPATCH-1958) Qdstat throws exception when router compiled with `DQD_MEMORY_STATS=OFF`

[ https://issues.apache.org/jira/browse/DISPATCH-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437559#comment-17437559 ] ASF GitHub Bot commented on DISPATCH-1958: -- ganeshmurthy commented on pull request #1416:

[GitHub] [qpid-dispatch] ganeshmurthy commented on pull request #1416: DISPATCH-1958: Fixed error in qdstat when memory stats are turned off…

ganeshmurthy commented on pull request #1416: URL: https://github.com/apache/qpid-dispatch/pull/1416#issuecomment-958128206 > Let's do this the simple way and remove the flag. Sounds good. I will add a commit to this PR removing the flag. Thanks. -- This is an automated message

[jira] [Commented] (DISPATCH-1958) Qdstat throws exception when router compiled with `DQD_MEMORY_STATS=OFF`

[ https://issues.apache.org/jira/browse/DISPATCH-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437556#comment-17437556 ] ASF GitHub Bot commented on DISPATCH-1958: -- ted-ross commented on pull request #1416: URL:

[GitHub] [qpid-dispatch] ted-ross commented on pull request #1416: DISPATCH-1958: Fixed error in qdstat when memory stats are turned off…

ted-ross commented on pull request #1416: URL: https://github.com/apache/qpid-dispatch/pull/1416#issuecomment-958124314 > > hmmm... I wonder if it would be simpler to make QD_MEMORY_STATS non-configurable? IOW, get rid of the flag and just always provide memory statistics. It's pretty

[jira] [Updated] (DISPATCH-2144) Fatal Python error: _PyMem_DebugMalloc: Python memory allocator called without holding the GIL

[ https://issues.apache.org/jira/browse/DISPATCH-2144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2144: Fix Version/s: (was: 1.18.0) 1.19.0 > Fatal Python error:

[jira] [Updated] (DISPATCH-2102) Shutdown crash when console connected

[ https://issues.apache.org/jira/browse/DISPATCH-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2102: Fix Version/s: (was: 1.18.0) 1.19.0 > Shutdown crash when

[jira] [Updated] (DISPATCH-2021) [libuv] system_tests_topology test_01_topology_failover sometimes fails with wrong message trace

[ https://issues.apache.org/jira/browse/DISPATCH-2021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2021: Fix Version/s: (was: 1.18.0) 1.19.0 > [libuv]

[jira] [Updated] (DISPATCH-2180) Race: timer freeing qd_message_t during cleanup conflict with I/O threads

[ https://issues.apache.org/jira/browse/DISPATCH-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2180: Fix Version/s: (was: 1.18.0) 1.19.0 > Race: timer freeing

[jira] [Updated] (DISPATCH-2007) Need better allocation of sessions across inter-router links

[ https://issues.apache.org/jira/browse/DISPATCH-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2007: Fix Version/s: (was: 1.18.0) 1.19.0 > Need better allocation of

[jira] [Updated] (DISPATCH-2084) Leak of qdr_terminus_t in system_tests_link_route_credit

[ https://issues.apache.org/jira/browse/DISPATCH-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2084: Fix Version/s: (was: 1.18.0) 1.19.0 > Leak of qdr_terminus_t in

[jira] [Updated] (DISPATCH-2069) ThreadSanitizer: data race at qdr_core_free in system_tests_policy

[ https://issues.apache.org/jira/browse/DISPATCH-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2069: Fix Version/s: (was: 1.18.0) 1.19.0 > ThreadSanitizer: data race

[jira] [Updated] (DISPATCH-1844) sys_mutex leak detected by LeakSanitizer ASAN (shutdown)

[ https://issues.apache.org/jira/browse/DISPATCH-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1844: Fix Version/s: (was: 1.18.0) 1.19.0 > sys_mutex leak detected by

[jira] [Updated] (DISPATCH-1935) Interrouter streaming links accumulate credit

[ https://issues.apache.org/jira/browse/DISPATCH-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1935: Fix Version/s: (was: 1.18.0) 1.19.0 > Interrouter streaming

[jira] [Updated] (DISPATCH-2070) Data race when incrementing severity_histogram from logging calls

[ https://issues.apache.org/jira/browse/DISPATCH-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2070: Fix Version/s: (was: 1.18.0) Backlog > Data race when

[jira] [Updated] (DISPATCH-2127) message content races between readers and writers

[ https://issues.apache.org/jira/browse/DISPATCH-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2127: Fix Version/s: (was: 1.18.0) 1.19.0 > message content races

[jira] [Updated] (DISPATCH-2096) Did not get expected Aborted_Delivery in system_tests_delivery_abort

[ https://issues.apache.org/jira/browse/DISPATCH-2096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2096: Fix Version/s: (was: 1.18.0) 1.19.0 > Did not get expected

[jira] [Updated] (DISPATCH-1892) http1 json aggregation does not handle large messages

[ https://issues.apache.org/jira/browse/DISPATCH-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1892: Fix Version/s: (was: 1.18.0) 1.19.0 > http1 json aggregation

[jira] [Updated] (DISPATCH-1821) Double-free in qd_entity_configure_policy on error

[ https://issues.apache.org/jira/browse/DISPATCH-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1821: Fix Version/s: (was: 1.18.0) 1.19.0 > Double-free in

[jira] [Updated] (DISPATCH-1745) Link routing does not propagate link properties

[ https://issues.apache.org/jira/browse/DISPATCH-1745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1745: Fix Version/s: (was: 1.18.0) 1.19.0 > Link routing does not

[jira] [Updated] (DISPATCH-1910) Edge router asserts when interior router connection denied by policy

[ https://issues.apache.org/jira/browse/DISPATCH-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1910: Fix Version/s: (was: 1.18.0) 1.19.0 > Edge router asserts when

[jira] [Updated] (DISPATCH-2122) Data race on alloc pool descriptor initialization

[ https://issues.apache.org/jira/browse/DISPATCH-2122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2122: Fix Version/s: (was: 1.18.0) 1.19.0 > Data race on alloc pool

[jira] [Updated] (DISPATCH-2123) qd_entity_refresh_allocator race in alloc_pool.c

[ https://issues.apache.org/jira/browse/DISPATCH-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2123: Fix Version/s: (was: 1.18.0) 1.19.0 >

[jira] [Updated] (DISPATCH-2135) data race accessing Q2 holdoff state

[ https://issues.apache.org/jira/browse/DISPATCH-2135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2135: Fix Version/s: (was: 1.18.0) 1.19.0 > data race accessing Q2

[jira] [Updated] (DISPATCH-2128) delivery_tracker core process walks link->undelivered unlocked

[ https://issues.apache.org/jira/browse/DISPATCH-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2128: Fix Version/s: (was: 1.18.0) 1.19.0 > delivery_tracker core

[jira] [Updated] (DISPATCH-2126) qdr_delivery_t->settled flag race

[ https://issues.apache.org/jira/browse/DISPATCH-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2126: Fix Version/s: (was: 1.18.0) 1.19.0 > qdr_delivery_t->settled

[jira] [Updated] (DISPATCH-2124) qdr_link_t->drain_mode flag race

[ https://issues.apache.org/jira/browse/DISPATCH-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2124: Fix Version/s: (was: 1.18.0) 1.19.0 > qdr_link_t->drain_mode

[jira] [Updated] (DISPATCH-1967) TCP adaptor connections not counted against policy global count

[ https://issues.apache.org/jira/browse/DISPATCH-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1967: Fix Version/s: (was: 1.18.0) 1.19.0 > TCP adaptor connections

[jira] [Updated] (DISPATCH-1891) http1 multicast does not handle chunked content

[ https://issues.apache.org/jira/browse/DISPATCH-1891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1891: Fix Version/s: (was: 1.18.0) 1.19.0 > http1 multicast does not

[jira] [Updated] (DISPATCH-2078) system_tests_authz_service_plugin mysteriously broken on GitHub Actions CI

[ https://issues.apache.org/jira/browse/DISPATCH-2078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2078: Fix Version/s: (was: 1.18.0) Backlog >

[jira] [Updated] (DISPATCH-1978) TCP adaptor wake-after-close fix needs a self test

[ https://issues.apache.org/jira/browse/DISPATCH-1978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1978: Fix Version/s: (was: 1.18.0) 1.19.0 > TCP adaptor

[jira] [Updated] (DISPATCH-2138) qdr_link_t->detach_received flag race

[ https://issues.apache.org/jira/browse/DISPATCH-2138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2138: Fix Version/s: (was: 1.18.0) 1.19.0 >

[jira] [Updated] (DISPATCH-2134) qdr_link_process_initial_delivery_CT race clearing link pointer

[ https://issues.apache.org/jira/browse/DISPATCH-2134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2134: Fix Version/s: (was: 1.18.0) 1.19.0 >

[jira] [Updated] (DISPATCH-2057) TSAN data race from qdr_core_unbind_address_link_CT in system_tests_edge_router

[ https://issues.apache.org/jira/browse/DISPATCH-2057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2057: Fix Version/s: (was: 1.18.0) 1.19.0 > TSAN data race from

[jira] [Updated] (DISPATCH-2130) python lock inversion deadlock

[ https://issues.apache.org/jira/browse/DISPATCH-2130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2130: Fix Version/s: (was: 1.18.0) 1.19.0 > python lock inversion

[jira] [Updated] (DISPATCH-2143) race getting/setting qdr_delivery_t->disposition

[ https://issues.apache.org/jira/browse/DISPATCH-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2143: Fix Version/s: (was: 1.18.0) 1.19.0 > race getting/setting

[jira] [Updated] (DISPATCH-2140) race setting/reading qdr_connection_t context

[ https://issues.apache.org/jira/browse/DISPATCH-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2140: Fix Version/s: (was: 1.18.0) 1.19.0 > race setting/reading

[jira] [Updated] (DISPATCH-2141) race moving qdr_delivery_state_t

[ https://issues.apache.org/jira/browse/DISPATCH-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2141: Fix Version/s: (was: 1.18.0) 1.19.0 > race moving

[jira] [Updated] (DISPATCH-2101) [console] TCP clients/servers/traffic not shown

[ https://issues.apache.org/jira/browse/DISPATCH-2101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2101: Fix Version/s: (was: 1.18.0) 1.19.0 > [console] TCP

[jira] [Updated] (DISPATCH-2129) shutdown race accessing core->running flag

[ https://issues.apache.org/jira/browse/DISPATCH-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2129: Fix Version/s: (was: 1.18.0) 1.19.0 > shutdown race accessing

[jira] [Updated] (DISPATCH-2125) qdr_link_t->stalled_outbound flag race

[ https://issues.apache.org/jira/browse/DISPATCH-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2125: Fix Version/s: (was: 1.18.0) 1.19.0 >

[jira] [Updated] (DISPATCH-2206) ASAN use-after-free of qdr_link_t by I/O thread

[ https://issues.apache.org/jira/browse/DISPATCH-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2206: Fix Version/s: (was: 1.18.0) 1.19.0 > ASAN use-after-free of

[jira] [Updated] (DISPATCH-2234) Update JavaScript console packages for the 1.18.0 release

[ https://issues.apache.org/jira/browse/DISPATCH-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2234: Fix Version/s: (was: 1.18.0) 1.19.0 > Update JavaScript console

[jira] [Updated] (DISPATCH-2131) I/O thread data race in qdr_record_link_credit

[ https://issues.apache.org/jira/browse/DISPATCH-2131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2131: Fix Version/s: (was: 1.18.0) 1.19.0 > I/O thread data race in

[jira] [Updated] (DISPATCH-2132) core->uptime_ticks races

[ https://issues.apache.org/jira/browse/DISPATCH-2132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2132: Fix Version/s: (was: 1.18.0) 1.19.0 > core->uptime_ticks races >

[jira] [Updated] (DISPATCH-2265) TCP and HTTP adaptor: client connection leak on close if no connector present

[ https://issues.apache.org/jira/browse/DISPATCH-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2265: Fix Version/s: (was: 1.18.0) 1.19.0 > TCP and HTTP adaptor:

[jira] [Updated] (DISPATCH-1890) need tests for http1 multicast

[ https://issues.apache.org/jira/browse/DISPATCH-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1890: Fix Version/s: (was: 1.18.0) 1.19.0 > need tests for http1

[jira] [Updated] (DISPATCH-1861) TCP adaptor server addresses take long time to propagate

[ https://issues.apache.org/jira/browse/DISPATCH-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1861: Fix Version/s: (was: 1.18.0) Backlog > TCP adaptor server

[jira] [Commented] (DISPATCH-2234) Update JavaScript console packages for the 1.18.0 release

[ https://issues.apache.org/jira/browse/DISPATCH-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437519#comment-17437519 ] Ganesh Murthy commented on DISPATCH-2234: - Is this strictly required for 1.18.0 ? If we can

[jira] [Commented] (DISPATCH-1958) Qdstat throws exception when router compiled with `DQD_MEMORY_STATS=OFF`

[ https://issues.apache.org/jira/browse/DISPATCH-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437516#comment-17437516 ] ASF GitHub Bot commented on DISPATCH-1958: -- kgiusti commented on pull request #1416: URL:

[GitHub] [qpid-dispatch] kgiusti commented on pull request #1416: DISPATCH-1958: Fixed error in qdstat when memory stats are turned off…

kgiusti commented on pull request #1416: URL: https://github.com/apache/qpid-dispatch/pull/1416#issuecomment-957878563 hmmm... I wonder if it would be simpler to make QD_MEMORY_STATS non-configurable? IOW, get rid of the flag and just always provide memory statistics. It's pretty

[jira] [Commented] (DISPATCH-2085) system_tests_fallback_dest failure - addr_proxy.c:323: on_conn_event: Assertion `addr->edge_outlink == 0' failed

[ https://issues.apache.org/jira/browse/DISPATCH-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437515#comment-17437515 ] ASF GitHub Bot commented on DISPATCH-2085: -- kgiusti merged pull request #1415: URL:

[jira] [Commented] (DISPATCH-1958) Qdstat throws exception when router compiled with `DQD_MEMORY_STATS=OFF`

[ https://issues.apache.org/jira/browse/DISPATCH-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437511#comment-17437511 ] ASF GitHub Bot commented on DISPATCH-1958: -- ganeshmurthy opened a new pull request #1416:

[GitHub] [qpid-dispatch] kgiusti merged pull request #1415: DISPATCH-2085: remove bad assertion in addr_proxy connection handler

kgiusti merged pull request #1415: URL: https://github.com/apache/qpid-dispatch/pull/1415 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

[jira] [Commented] (QPIDJMS-552) JMS 2 Completion threads shouldn't scale with the number of sessions

[ https://issues.apache.org/jira/browse/QPIDJMS-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437509#comment-17437509 ] ASF GitHub Bot commented on QPIDJMS-552: franz1981 edited a comment on pull request #44: URL:

[GitHub] [qpid-jms] franz1981 edited a comment on pull request #44: QPIDJMS-552 JMS 2 Completion threads shouldn't scale with the number of sessions

franz1981 edited a comment on pull request #44: URL: https://github.com/apache/qpid-jms/pull/44#issuecomment-957253435 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To

[jira] [Commented] (QPIDJMS-552) JMS 2 Completion threads shouldn't scale with the number of sessions

[ https://issues.apache.org/jira/browse/QPIDJMS-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437501#comment-17437501 ] ASF GitHub Bot commented on QPIDJMS-552: franz1981 commented on pull request #44: URL:

[jira] [Commented] (QPIDJMS-552) JMS 2 Completion threads shouldn't scale with the number of sessions

[ https://issues.apache.org/jira/browse/QPIDJMS-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437493#comment-17437493 ] ASF GitHub Bot commented on QPIDJMS-552: gemmellr commented on pull request #44: URL:

[GitHub] [qpid-jms] franz1981 commented on pull request #44: QPIDJMS-552 JMS 2 Completion threads shouldn't scale with the number of sessions

franz1981 commented on pull request #44: URL: https://github.com/apache/qpid-jms/pull/44#issuecomment-957253435 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To

[jira] [Commented] (DISPATCH-1958) Qdstat throws exception when router compiled with `DQD_MEMORY_STATS=OFF`

[ https://issues.apache.org/jira/browse/DISPATCH-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437500#comment-17437500 ] ASF GitHub Bot commented on DISPATCH-1958: -- ganeshmurthy commented on pull request #1416:

[GitHub] [qpid-dispatch] ganeshmurthy commented on pull request #1416: DISPATCH-1958: Fixed error in qdstat when memory stats are turned off…

ganeshmurthy commented on pull request #1416: URL: https://github.com/apache/qpid-dispatch/pull/1416#issuecomment-957887593 > hmmm... I wonder if it would be simpler to make QD_MEMORY_STATS non-configurable? IOW, get rid of the flag and just always provide memory statistics. It's pretty

[jira] [Commented] (PROTON-2406) [cpp] Use of reconnect_options::failover_urls triggers -Wdeprecated-declarations in examples/cpp/reconnect_client.cpp

[ https://issues.apache.org/jira/browse/PROTON-2406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437497#comment-17437497 ] ASF GitHub Bot commented on PROTON-2406: cliffjansen commented on pull request #337: URL:

[GitHub] [qpid-proton] cliffjansen commented on pull request #337: PROTON-2406: [cpp] Replace uses of deprecated reconnect_options::failover_urls with conn…

cliffjansen commented on pull request #337: URL: https://github.com/apache/qpid-proton/pull/337#issuecomment-956502433 As I read the documentation for reconnect_url() and failover_urls() I implicitly expect the same intention for: - default reconnect timing options - change

[GitHub] [qpid-jms] gemmellr commented on pull request #44: QPIDJMS-552 JMS 2 Completion threads shouldn't scale with the number of sessions

gemmellr commented on pull request #44: URL: https://github.com/apache/qpid-jms/pull/44#issuecomment-957323951 I think single completion at a time is the way to go, at least by default, it just shouldn't really be a concern when using it whether the callback execution is fair or not. --

[jira] [Commented] (DISPATCH-2247) "Received MAU from an unknown router" error message must include unknown router id

[ https://issues.apache.org/jira/browse/DISPATCH-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437491#comment-17437491 ] ASF GitHub Bot commented on DISPATCH-2247: -- asfgit merged pull request #1414: URL:

[GitHub] [qpid-dispatch] asfgit merged pull request #1414: DISPATCH-2247: Added router id to log message

asfgit merged pull request #1414: URL: https://github.com/apache/qpid-dispatch/pull/1414 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail:

[jira] [Updated] (DISPATCH-2093) [tcp] TCP deliveries are counted as modified

[ https://issues.apache.org/jira/browse/DISPATCH-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2093: Fix Version/s: (was: 1.18.0) 1.19.0 > [tcp] TCP deliveries are

[jira] [Updated] (DISPATCH-2092) [tools] Scraper does not expose TCP adaptor information

[ https://issues.apache.org/jira/browse/DISPATCH-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2092: Fix Version/s: (was: 1.18.0) Backlog > [tools] Scraper does not

[jira] [Updated] (DISPATCH-2071) system_tests_authz_service_plugin test failure

[ https://issues.apache.org/jira/browse/DISPATCH-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2071: Fix Version/s: (was: 1.18.0) Backlog >

[jira] [Updated] (DISPATCH-2133) qd_log_enabled() race

[ https://issues.apache.org/jira/browse/DISPATCH-2133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2133: Fix Version/s: (was: 1.18.0) 1.19.0 > qd_log_enabled() race >

[jira] [Updated] (DISPATCH-1903) Remote upload of certificate files for new TLS configurations

[ https://issues.apache.org/jira/browse/DISPATCH-1903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1903: Fix Version/s: (was: 1.18.0) 1.19.0 > Remote upload of

[jira] [Updated] (DISPATCH-2036) TCP adaptor deliveries reported as "stuck" by delayed delivery detection

[ https://issues.apache.org/jira/browse/DISPATCH-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2036: Fix Version/s: (was: 1.18.0) 1.19.0 > TCP adaptor deliveries

[jira] [Updated] (DISPATCH-1915) Remove deprecated Proton Url python class

[ https://issues.apache.org/jira/browse/DISPATCH-1915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1915: Fix Version/s: (was: 1.18.0) 1.19.0 > Remove deprecated Proton

[jira] [Updated] (DISPATCH-2137) multiple data races in the SASL plugin

[ https://issues.apache.org/jira/browse/DISPATCH-2137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2137: Fix Version/s: (was: 1.18.0) Backlog > multiple data races in

[jira] [Updated] (DISPATCH-1992) [tcp] Use PN_RAW_CONNECTION_DRAIN_BUFFERS in tcp adaptor

[ https://issues.apache.org/jira/browse/DISPATCH-1992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1992: Fix Version/s: (was: 1.18.0) 1.19.0 > [tcp] Use

[jira] [Updated] (DISPATCH-1994) [http2] Use PN_RAW_CONNECTION_DRAIN_BUFFERS in http2 adaptor

[ https://issues.apache.org/jira/browse/DISPATCH-1994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1994: Fix Version/s: (was: 1.18.0) 1.19.0 > [http2] Use

[jira] [Updated] (DISPATCH-1993) [http1] Use PN_RAW_CONNECTION_DRAIN_BUFFERS in http1 adaptor

[ https://issues.apache.org/jira/browse/DISPATCH-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-1993: Fix Version/s: (was: 1.18.0) 1.19.0 > [http1] Use

[jira] [Resolved] (DISPATCH-1957) Leaked objects in system_tests_delivery_abort

[ https://issues.apache.org/jira/browse/DISPATCH-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy resolved DISPATCH-1957. - Resolution: Fixed > Leaked objects in system_tests_delivery_abort >

[jira] [Updated] (DISPATCH-2000) Consider increasing default internal buffer size

[ https://issues.apache.org/jira/browse/DISPATCH-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2000: Fix Version/s: (was: 1.18.0) 1.19.0 > Consider increasing

[jira] [Updated] (DISPATCH-2000) Consider increasing default internal buffer size

[ https://issues.apache.org/jira/browse/DISPATCH-2000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2000: Priority: Major (was: Critical) > Consider increasing default internal buffer size >

[jira] [Updated] (DISPATCH-2005) [http2] grpc performance test with buoyantio lot slower with router in the middle

[ https://issues.apache.org/jira/browse/DISPATCH-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ganesh Murthy updated DISPATCH-2005: Fix Version/s: (was: 1.18.0) 1.19.0 > [http2] grpc performance

[jira] [Commented] (DISPATCH-1958) Qdstat throws exception when router compiled with `DQD_MEMORY_STATS=OFF`

[ https://issues.apache.org/jira/browse/DISPATCH-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437446#comment-17437446 ] ASF GitHub Bot commented on DISPATCH-1958: -- ganeshmurthy commented on pull request #1416:

[GitHub] [qpid-dispatch] ganeshmurthy commented on pull request #1416: DISPATCH-1958: Fixed error in qdstat when memory stats are turned off…

ganeshmurthy commented on pull request #1416: URL: https://github.com/apache/qpid-dispatch/pull/1416#issuecomment-957887593 > hmmm... I wonder if it would be simpler to make QD_MEMORY_STATS non-configurable? IOW, get rid of the flag and just always provide memory statistics. It's pretty

[jira] [Commented] (DISPATCH-1821) Double-free in qd_entity_configure_policy on error

[ https://issues.apache.org/jira/browse/DISPATCH-1821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437445#comment-17437445 ] Jiri Daněk commented on DISPATCH-1821: -- [~kgiusti] The code in question is quite weird and could

[jira] [Assigned] (DISPATCH-2103) Log the actual HTTP websocket listener port when 0 was specified in config

[ https://issues.apache.org/jira/browse/DISPATCH-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Daněk reassigned DISPATCH-2103: Assignee: Jiri Daněk > Log the actual HTTP websocket listener port when 0 was

  1   2   >