[ 
https://issues.apache.org/jira/browse/DISPATCH-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16980375#comment-16980375
 ] 

ASF GitHub Bot commented on DISPATCH-1475:
------------------------------------------

asfgit commented on pull request #627: DISPATCH-1475: use safe pointers in 
connection/link action messages
URL: https://github.com/apache/qpid-dispatch/pull/627
 
 
   
 
----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
[email protected]


> 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]

Reply via email to