 |
 |
OK, it isn't an explicit ForcedDisconnect but the call to RemoveSocket() is the common thing that happens when a connect fails or you do a ForceDisconnect. Sorry about the sloppy wording. Here a connect fails and an attempt is made to remove a socket while a timeout callback is occurring. Both execution paths get the stream lock which is what is causing the deadlock. The same would happen when a ForceDisconnect wold have been called IMHO. -- Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/1979#issuecomment-1485237986 You are receiving this because you commented. Message ID: <[log in to unmask]> ######################################################################## 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