tomaswolf commented on issue #473:

   Thank you. That is useful and gives me a starting point to analyze this 
deeper. The log confirms my initial suspicion: it looks as if closing the 
channel by mistake also closes the session. Plus there's a race between this 
closing of the session (which is too early) and sending the CLOSE message for 
the channel. If the session closes earlier, the client doesn't get the CLOSE 
message and complains, plus we get that "write on closing session" exception on 
the server. If sending the CLOSE is earlier, the client might be happy, 
especially if it manages to send back its own CLOSE before the network 
connection goes down.
   I'll try to come up with some unit test, and I'll have to dig deeper to 
figure out why the session is closed at all at that point. It should not be 
closed yet.
   Not sure the race and bug are new since 2.10.0; but it's possible that 
changes made since then make an old bug surface now more frequently.

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail:

For queries about this service, please contact Infrastructure at:

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to