Hi Brian,

Thanks for reporting it.

Could you see if it can be reproduced with xrootd-4.6.0?
A similar problem has been fixed in #483 (which is included in 4.6.0)

In particular, we have seen that if the read time-out kicks in and the stream is broken the request and its handler due to an error are owned both by the outgoing and incoming queue. This triggers all sorts of errors.
I'm suspecting that in your case a second read time-out kicked in and the handler and its request were transferred for a second time to the incoming queue (from what I see in the back trace there were two read time-outs, right?). Then, the thread-pool simply invoked both handlers/callbacks.

Cheers,
Michal

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/xrootd/xrootd","title":"xrootd/xrootd","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/xrootd/xrootd"}},"updates":{"snippets":[{"icon":"PERSON","message":"@simonmichal in #488: Hi Brian,\r\n\r\nThanks for reporting it.\r\n\r\nCould you see if it can be reproduced with xrootd-4.6.0?\r\nA similar problem has been fixed in #483 (which is included in 4.6.0)\r\n\r\nIn particular, we have seen that if the read time-out kicks in and the stream is broken the request and its handler due to an error are owned both by the outgoing and incoming queue. This triggers all sorts of errors. \r\nI'm suspecting that in your case a second read time-out kicked in and the handler and its request were transferred for a second time to the incoming queue (from what I see in the back trace there were two read time-outs, right?). Then, the thread-pool simply invoked both handlers/callbacks.\r\n\r\nCheers,\r\nMichal"}],"action":{"name":"View Issue","url":"https://github.com/xrootd/xrootd/issues/488#issuecomment-290432805"}}}

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