[
https://issues.apache.org/jira/browse/DISPATCH-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16171842#comment-16171842
]
Chuck Rolke commented on DISPATCH-814:
--------------------------------------
I've seen qdrouterd processes stuck in *<defunct>* state. This issue suggests
an error in the testing framework where the router has exited but its process
is still in the process table.
I do not have a decent reproducer for getting the qdrouterd into this state. It
happens most for me when I run a bash script that starts one or more routers
and then type ^C to exit the script.
> Killing qdrouterd process takes a long time
> -------------------------------------------
>
> Key: DISPATCH-814
> URL: https://issues.apache.org/jira/browse/DISPATCH-814
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Routing Engine
> Environment: This test runs in fedora 26 container.
> Reporter: Irina Boverman
>
> Often killing router fails to complete:
> ++ ps -C qdrouterd -o pid=
> + pid=' 1455'
> + kill 1455
> + set +e
> + wait 1455
> Build timed out (after 30 minutes). Marking the build as failed.
> Build was aborted
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
