You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Jiri Daněk (Jira)" <ji...@apache.org> on 2022/10/26 19:40:00 UTC
[jira] [Commented] (PROTON-2553) Hang in proactor thread waiting for PN_PROACTOR_INTERRUPT
[ https://issues.apache.org/jira/browse/PROTON-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17624709#comment-17624709 ]
Jiri Daněk commented on PROTON-2553:
------------------------------------
It happened on main, https://github.com/skupperproject/skupper-router/issues/535#issuecomment-1292545296
Proton main was at https://github.com/apache/qpid-proton/commit/800722dd08c9bf75c70f2b6adce2e60fb3302283
> Hang in proactor thread waiting for PN_PROACTOR_INTERRUPT
> ---------------------------------------------------------
>
> Key: PROTON-2553
> URL: https://issues.apache.org/jira/browse/PROTON-2553
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
> Affects Versions: proton-c-0.37.0
> Reporter: Ken Giusti
> Assignee: Clifford Jansen
> Priority: Major
>
> Recently changed (~2 weeks) the Skupper-router project's CI to help diagnose very occasional timeout error that appear to be happening during router shutdown. The CI test infrastructure now sends a SIGABORT to a router that has not exited within 60 seconds of receiving a SIGTERM.
> This resulted in a weird test failure - only captured once so far - that appears as if the router is stuck in proactor.
> See [https://github.com/skupperproject/skupper-router/runs/6698510074#step:29:84] for the gdb crash traceback.
> And the related skupper-router issue: [https://github.com/skupperproject/skupper-router/issues/535]
> Unable to reproduce.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org