Regression due to close listener order not respected

ari-ban / issue-test

0 stars 0 forks source link

Regression due to close listener order not respected #1968

Closed arinban closed 6 years ago

arinban commented 6 years ago

Changes for #1962 did not take into account the order in which the close listeners were registered. As a result the close reason could be missing when several filters where present (such as SSL). I'll be sending a PR to fix this.

arinban commented 6 years ago

Issue Imported From: https://github.com/javaee/grizzly/issues/1968
Original Issue Raised By:@afelisatti
Original Issue Assigned To:Unassigned
Original Issue Closed By:@rlubke

arinban commented 6 years ago

@afelisatti Commented Thanks, @rlubke. Any thoughts on when a 2.3.x release could be available to avoid this issue? I'd like to update GAHC to that version and wait for that release as well.

arinban commented 6 years ago

@rlubke Commented I'll work on a release this week.

Sent from my iPhone

On Sep 6, 2017, at 09:50, Ana Felisatti notifications@github.com wrote:

Thanks, @rlubke. Any thoughts on when a 2.3.x release could be available to avoid this issue?

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

arinban commented 6 years ago

@afelisatti Commented Thank you!

arinban commented 6 years ago

@rlubke Commented Release complete.

arinban commented 6 years ago

@afelisatti Commented PR sent to GAHC (https://github.com/javaee/grizzly-ahc/pull/16)