[jira] [Commented] (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:comment-tabpanel=17437443#comment-17437443 ] Jiri Daněk commented on DISPATCH-2103: -- [~kgiusti] I'm putting this off to 1.19 where I plan to

[jira] [Updated] (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 updated DISPATCH-2103: - Fix Version/s: 1.19.0 > Log the actual HTTP websocket listener port when 0 was specified in

[jira] [Updated] (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 updated DISPATCH-2103: - Fix Version/s: (was: 1.18.0) > Log the actual HTTP websocket listener port when 0 was

[jira] [Updated] (DISPATCH-2208) Dispatch docs build fails if -DRUNTIME_CHECK=asan is used

[ https://issues.apache.org/jira/browse/DISPATCH-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Daněk updated DISPATCH-2208: - Fix Version/s: (was: 1.18.0) 1.19.0 > Dispatch docs build fails if

[jira] [Resolved] (DISPATCH-2246) The 'Address already in use` test issue, in echo server

[ https://issues.apache.org/jira/browse/DISPATCH-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Daněk resolved DISPATCH-2246. -- Resolution: Fixed > The 'Address already in use` test issue, in echo server >

[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=17437441#comment-17437441 ] 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] [Updated] (DISPATCH-2256) edge router fallback links and addresses incorrect on interior failover

[ https://issues.apache.org/jira/browse/DISPATCH-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti updated DISPATCH-2256: - Description: Scenario: Configure an edge router with two separate interior connectors - one

[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=17437425#comment-17437425 ] ASF GitHub Bot commented on DISPATCH-1958: -- ganeshmurthy opened a new pull request #1416:

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

ganeshmurthy opened a new pull request #1416: URL: https://github.com/apache/qpid-dispatch/pull/1416 … (-DQD_MEMORY_STATS=OFF) -- 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

[jira] [Updated] (DISPATCH-2256) edge router fallback links and addresses incorrect on interior failover

[ https://issues.apache.org/jira/browse/DISPATCH-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti updated DISPATCH-2256: - Summary: edge router fallback links and addresses incorrect on interior failover (was:

[jira] [Updated] (DISPATCH-2256) outgoing fallback links fail to re-establish on edge-router interior fallback

[ https://issues.apache.org/jira/browse/DISPATCH-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ken Giusti updated DISPATCH-2256: - Description: (was: When the interior router connected to an edge router with attached

[jira] [Created] (PROTON-2453) [proton-python] Create MyPy CI job and fix found inconsistencies

Jiri Daněk created PROTON-2453: -- Summary: [proton-python] Create MyPy CI job and fix found inconsistencies Key: PROTON-2453 URL: https://issues.apache.org/jira/browse/PROTON-2453 Project: Qpid Proton

[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=17437281#comment-17437281 ] 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=17437248#comment-17437248 ] 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 I've sent a change that it's introducing `HolderSuppliers` (bad name, so happy to receive feedbacks/suggestions) and `SharedDisposable` as a util that could be used on

[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=17437221#comment-17437221 ] ASF GitHub Bot commented on QPIDJMS-552: franz1981 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-957261604 I see that a version that just handle one completion task at time to guarantee FJ to handle fairness of completions isn't working that bad, really, but I need to perform some

[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=17437215#comment-17437215 ] 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 I've sent a change that it's introducing `HolderSuppliers` (bad name, so happy to receive feedbacks/suggestions) and `SharedDisposable` as a util that could be used on

[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=17437214#comment-17437214 ] ASF GitHub Bot commented on QPIDJMS-552: franz1981 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 I've sent a change that it's introducing `HolderSuppliers` (bad name, so happy to receive feedbacks/suggestions) and `SharedDisposable` as a util that could be used on

[jira] [Commented] (DISPATCH-2274) system_tests_router_mesh: ERROR: AddressSanitizer: use-after-poison in qd_link_pn container.c:1029

[ https://issues.apache.org/jira/browse/DISPATCH-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437206#comment-17437206 ] Jiri Daněk commented on DISPATCH-2274: -- Present in main and in the 1.18 freeze tag

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

[ https://issues.apache.org/jira/browse/DISPATCH-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17437203#comment-17437203 ] Jiri Daněk commented on DISPATCH-2126: --

<    1   2