You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Justin Ross (JIRA)" <ji...@apache.org> on 2016/11/04 01:50:58 UTC

[jira] [Updated] (PROTON-30) The driver cannot be cleanly used in a multi-threaded application due to pn_driver_wait

     [ https://issues.apache.org/jira/browse/PROTON-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Ross updated PROTON-30:
------------------------------
    Assignee: Alan Conway  (was: Ted Ross)

> The driver cannot be cleanly used in a multi-threaded application due to pn_driver_wait
> ---------------------------------------------------------------------------------------
>
>                 Key: PROTON-30
>                 URL: https://issues.apache.org/jira/browse/PROTON-30
>             Project: Qpid Proton
>          Issue Type: Wish
>          Components: proton-c
>            Reporter: Ted Ross
>            Assignee: Alan Conway
>
> An efficient multi-threaded application based on proton-c will want to have one thread blocked on pn_driver_wait if there's no other work for it to do.  Unfortunately, pn_driver_wait does thread-unsafe things with internal driver data structures before and after it blocks on the FD set.
> The alternatives are to quiesce all threads prior to calling pn_driver_wait (which is undesirable for performance reasons) or to divide pn_driver_wait into three sections, the first and third of which can be invoked with a lock held and the second of which (the poll call) can be invoked without a lock.
> Alternatively, a driver API better suited to multi-threading could be developed.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org