https://bz.apache.org/bugzilla/show_bug.cgi?id=69938
--- Comment #2 from Remy Maucherat <[email protected]> --- This is an async operation. Now the channel is being reset right away to save memory, and only after that is it replaced by the closed channel in the socket wrapper. Since doClose is not synced, then presumably this can happen. I doubt it is a good idea to sync doClose so it's never going to be perfect. I'll make some adjustments over handling the SSL engine after checking the closed flag, and move the getSocket().reset(null, null); from the socket wrapper doClose into its finally. This should be good enough to avoid this. This is cosmetic though. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
