[
https://issues.apache.org/jira/browse/DISPATCH-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16976656#comment-16976656
]
Charles E. Rolke commented on DISPATCH-1475:
--------------------------------------------
I'm attaching some cuts from a different failure but one that is possibly
relevant.
The router for this test was printing extra logging information including the
addresses of connections and links. Then the addresses in the core dump can be
tied directly to events in the log file. Facts are:
* The failing connection [C2] at address 0x7f469401e158 is the connection
between the edge router and the interior
* The failing link [L870] at address 0x7f4690088ad8 is the link that is being
used after it has been freed
> Seg fault in qdr_link_cleanup_CT after 12,400+ connections
> ----------------------------------------------------------
>
> Key: DISPATCH-1475
> URL: https://issues.apache.org/jira/browse/DISPATCH-1475
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Router Node
> Affects Versions: 1.9.0
> Environment: Two systems: Fedora 29
> Reporter: Charles E. Rolke
> Assignee: Ken Giusti
> Priority: Major
> Attachments: D-1475-2.txt, DISPATCH-1475-core-writeup.txt
>
>
> Running millions of messages on network described in DISPATCH-1474. This
> morning's dispatch master Debug build, and proton 0.29.0 Debug build.
> While a stream of unsettled multicast messages is flowing, then a separate
> process connects to EC1, receives a few messages, and then disconnects.
> Eventually the EC1 edge router seg faults with qdr_link_cleanup_CT receiving
> a conn=0x9999999999999999.
> This setup ran for hours before failing.
> For this command S_RECV is a softlink in my path for proton simple_receive.
> {{var=1; while true; do S_RECV -a $EC1_normal/multicast/q1 -m $var;
> var=$((var+1)); done}}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
