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
- ddc4866 Fixed Run method in XrdClOperations to create an async job when the request fails (instead of staying in sync)
File Changes
(1 file)
Patch Links:
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
Message ID: <xrootd/xrootd/pull/1741@github.com>
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/xrootd/xrootd/pull/1741",
"url": "https://github.com/xrootd/xrootd/pull/1741",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]
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
