SSLEngine closing prematurely on SSLHandshakeException?

Question

I have worked with the SSLEngine using non-blocked IO and it mostly works.
I do have a problem when a client connects and I get
WorkerThread-1, fatal error: 40: no cipher suites in common
javax.net.ssl.SSLHandshakeException: no cipher suites in common
WorkerThread-1, SEND TLSv1 ALERT:  fatal, description = handshake_failure
WorkerThread-1, WRITE: TLSv1 Alert, length = 2in a delegate task. The handshake status is NEED_WRAP after this but when
I call wrapHandshake I get
WorkerThread-1, fatal: engine already closed.  Rethrowing javax.net.ssl.SSLHandshakeException: no cipher suites in commonwhich means I'm not able to send the error reply to the connected client.
Is this a bug in SSLEngine or simply a misunderstanding on my part on what's going on.
I'm thankful for any insight on this.
regards
/Magnus Hulth�n

Answer 1

Thanks,
Yes that would make sense, and that is how I would expect it to work.
The problem is that when call wrap (not wrapHandshake as I mistakenly wrote in my previous post) I get the exception
WorkerThread-1, fatal: engine already closed.  Rethrowing javax.net.ssl.SSLHandshakeException: no cipher suites in commonJust to see if there was some timing issue involved I tried to call wrap immediately after the delegated task finished and still got the same exception.
What it looks like to me is that the engine needs to wrap the error message but is already closed by the handshake error and therefore not able to actually perform the wrap.