LISTSERV 16.5 - XROOTD-DEV Archives

Until now, the failed request resulted in the responsehandler being called immediately. 
This meant that no new thread was created and the reading mutex would be blocking forever (even when a pipeline is started as Async).
By replacing it with a job a new thread is created for the answer.
You can view, comment on, or merge this pull request online at:

  https://github.com/xrootd/xrootd/pull/1741

-- Commit Summary --

  * Fixed Run method in XrdClOperations to create an async job when the request fails (instead of staying in sync)

-- File Changes --

    M src/XrdCl/XrdClOperations.hh (11)

-- Patch Links --

https://github.com/xrootd/xrootd/pull/1741.patch
https://github.com/xrootd/xrootd/pull/1741.diff

-- 
Reply to this email directly or view it on GitHub:
https://github.com/xrootd/xrootd/pull/1741
You are receiving this because you are subscribed to this thread.

Message ID: &lt;[log in to unmask]&gt;

########################################################################
Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1