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

Ganesh Murthy commented on DISPATCH-414:
----------------------------------------

You can reliably reproduce this issue without involving Ernie's console using 
the following steps - 

1. Start the router using the console.conf attached to this ticket
2. start a receiver on port 20009 using simple_recv.py
{noformat}
python simple_recv.py --address localhost:20009/examples -m1
{noformat}
3. Delete the listener with name ProxyListener
{noformat}
qdmanage -b localhost:20009 DELETE --type=listener --name=ProxyListener
{noformat}
4. Now run, qdstat -c , several times (say 10-15 times) and the router will 
crash. The reason that the crash is happening is because the role field that 
the qd_refresh_connection function in server.c is trying to access has already 
been freed.
5. The pull request (https://github.com/apache/qpid-dispatch/pull/89) will 
solve this problem by introducing a new field called role on the connection.

> Deleting a ProxyListener from dispatch-console segfaults the router
> -------------------------------------------------------------------
>
>                 Key: DISPATCH-414
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-414
>             Project: Qpid Dispatch
>          Issue Type: Bug
>          Components: Console
>    Affects Versions: 0.6.1
>            Reporter: Jiri Danek
>            Assignee: Ganesh Murthy
>         Attachments: backtrace.log, console.conf, core.bz2, qdrouterd.log
>
>
> Start qdrouterd with the attached config (default, except for the log and 
> console sections).
> Start dispatch-console, connect to the router, go to Entities tab
> Open listener/ProxyListener, click Delete, confirm
> Wait for qdrouterd to crash



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to