Print

Print

Actually, looking at the code I suspect the callback is being performed before the client got a wait_resp. Be aware that we try to interlock those two to prevent these kinds of occurrences. There is an additional exchange with the callback object which indicates whether or not we actually sent the kXR_waitresp as you can't do a callback until that happens. Please see the comments in XrdXrootdXeq.cc:3421 -- somehow I think we went through a similar issue some years ago with another callback situation in EOS, though I can't recall which callback that was but this sounds eerily similar to that one.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1148#issuecomment-606424975", "url": "https://github.com/xrootd/xrootd/issues/1148#issuecomment-606424975", "name": "View Issue" }, "description": "View this Issue 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