You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/07/03 22:13:00 UTC
[jira] [Commented] (PROTON-1847) container:schedule used from an
external thread can stop container::run loop processing other events
[ https://issues.apache.org/jira/browse/PROTON-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16532011#comment-16532011 ]
ASF subversion and git services commented on PROTON-1847:
---------------------------------------------------------
Commit 9fd19bcf960dacc046b2f6867c538149eceb8e5c in qpid-proton's branch refs/heads/go1 from [~astitcher]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=9fd19bc ]
PROTON-1847: [C++ binding] Ensure that excessive scheduled events can't starve other events
> container:schedule used from an external thread can stop container::run loop processing other events
> ----------------------------------------------------------------------------------------------------
>
> Key: PROTON-1847
> URL: https://issues.apache.org/jira/browse/PROTON-1847
> Project: Qpid Proton
> Issue Type: Bug
> Components: cpp-binding
> Reporter: Andrew Stitcher
> Assignee: Andrew Stitcher
> Priority: Major
> Fix For: proton-c-0.23.0
>
>
> There are 2 potential problems:
> # The code that runs the scheduled tasks still accepts new tasks at the same time. So if you keep on scheduling new tasks continuously you could make the scheduler run tasks continuously without ever leaving to process any other events.
> # The code that accepts timeout events will keep on reading the same event batch until it is empty. So in this case too new tasks could prevent any other events being processed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org