[
https://issues.apache.org/jira/browse/DISPATCH-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076661#comment-17076661
]
ASF GitHub Bot commented on DISPATCH-1614:
--
asfgit commented on pull request
[
https://issues.apache.org/jira/browse/DISPATCH-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076660#comment-17076660
]
ASF subversion and git services commented on DISPATCH-1614:
---
asfgit closed pull request #714: DISPATCH-1614: Nullify address inlink and
outlink when connection lost
URL: https://github.com/apache/qpid-dispatch/pull/714
This is an automated message from the Apache Git Service.
To respo
[
https://issues.apache.org/jira/browse/DISPATCH-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076640#comment-17076640
]
ASF subversion and git services commented on DISPATCH-1616:
---
[
https://issues.apache.org/jira/browse/DISPATCH-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076601#comment-17076601
]
ASF GitHub Bot commented on DISPATCH-1615:
--
ChugR commented on pull request #
ChugR opened a new pull request #715: DISPATCH-1615: Improve recent backtrace
debug output
URL: https://github.com/apache/qpid-dispatch/pull/715
Add searchable summary line that includes router identifier,
timestamp, object type, and object address.
-
[
https://issues.apache.org/jira/browse/DISPATCH-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076591#comment-17076591
]
ASF GitHub Bot commented on DISPATCH-1614:
--
ChugR commented on pull request #
ChugR opened a new pull request #714: DISPATCH-1614: Nullify address inlink and
outlink when connection lost
URL: https://github.com/apache/qpid-dispatch/pull/714
Prevent segfault referencing deleted links when connection is lost.
Assert that the pointers are null when a connection is cr
Charles E. Rolke created DISPATCH-1616:
--
Summary: Scraper could export facts for creating sequence diagrams
Key: DISPATCH-1616
URL: https://issues.apache.org/jira/browse/DISPATCH-1616
Project: Qpi
[
https://issues.apache.org/jira/browse/DISPATCH-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charles E. Rolke reassigned DISPATCH-1614:
--
Assignee: Charles E. Rolke
> Edge router crash when interior closes edge up
[
https://issues.apache.org/jira/browse/DISPATCH-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-1531:
Fix Version/s: (was: 1.12.0)
> Connection fails if client creates a rx link with add
[
https://issues.apache.org/jira/browse/DISPATCH-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-1530:
Fix Version/s: (was: 1.12.0)
> system_tests_multi_tenancy fails occasionally
>
Charles E. Rolke created DISPATCH-1615:
--
Summary: Backtrace of leaked allocations does not show object
address
Key: DISPATCH-1615
URL: https://issues.apache.org/jira/browse/DISPATCH-1615
Project:
[
https://issues.apache.org/jira/browse/DISPATCH-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ganesh Murthy updated DISPATCH-1533:
Fix Version/s: (was: 1.12.0)
> Connection drop if > 255 links per conn opened with a
>
>
> *Hey Mick, *
> *That did the trick - color me impressed.*
>
OK.
Ken, impressed:
[image: image.png]
On Mon, Apr 6, 2020 at 9:18 AM Ken Giusti wrote:
> Hey Mick,
>
> That did the trick - color me impressed.
>
> If that's the intended behavior for sending streaming messages it wasn't
> cl
[
https://issues.apache.org/jira/browse/PROTON-2189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17076338#comment-17076338
]
Ken Giusti commented on PROTON-2189:
Mick has designed a proactor client that can pr
[
https://issues.apache.org/jira/browse/PROTON-2189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti updated PROTON-2189:
---
Attachment: 0001-tweak-clogger-to-fix-streaming.patch
> proactor C client has abnormally long pauses
Hey Mick,
That did the trick - color me impressed.
If that's the intended behavior for sending streaming messages it wasn't
clear to me. I'll update the JIRA with your recommendations, thanks!
On Sat, Apr 4, 2020 at 12:32 PM Michael Goulish wrote:
> Ken --
>
> I have a proactor client in Me
18 matches
Mail list logo
