Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SslHandler may miss to notify write future if the SSLEngine was closed #601

Closed
normanmaurer opened this issue Sep 14, 2012 · 4 comments
Closed
Assignees
Labels
Milestone

Comments

@normanmaurer
Copy link
Member

We miss to notify the ChannelFuture of the pendingWrite which is just in progress if the SSLEngine was closed. This means the the ChannelFutureListener will never get notifived in that case.

@MattFriedman
Copy link

Hi Norman, Many thanks for this. We'd like to try it; is there a snapshot build we can get? Cheers, Matt

@normanmaurer
Copy link
Member Author

Yeah please try this one:

https://repository-netty.forge.cloudbees.com/snapshot/io/netty/netty/3.5.8.Final-SNAPSHOT/netty-3.5.8.Final-20120914.181149-4.jar

Bye,
Norman

Am 14.09.2012 um 16:42 schrieb MattFriedman notifications@github.com:

Hi Norman, Many thanks for this. We'd like to try it; is there a snapshot build we can get? Cheers, Matt


Reply to this email directly or view it on GitHub.

@MattFriedman
Copy link

Thanks again Norman, however, I believe we still have the issue for our scenario.

When I watch the success variable in wrap() it is always true for us so there is no SSLEngine already closed problem in our case. In our case we still never get the notification. Can I provide you more information? Shall I open another issue? Thanks, Matt

@normanmaurer
Copy link
Member Author

Yeah please... maybe you could even add some "example" code so I could reproduce it easily ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants