Hi,
thanks for the response.
Trustin Lee wrote:
Hi Kerekes,
On Jan 16, 2008 12:21 AM, Kerekes András <[EMAIL PROTECTED]> wrote:
Hi,
after checking JIRA, I found this:
https://issues.apache.org/jira/browse/DIRMINA-272
Which was closed with the following note:
"It's not actually a bug. An SSLException can be sometimes thrown while
destroying the session if the connection was closed abnormally. You can
simply ignore that exception. That's why I logged that message in DEBUG
level."
So I can ignore this exception. But for me it still occurs on every call
to session.close(), not only sometimes.
It's probably because the remote peer is closing the connection
immediately not sending the last close_notify.
I've been debugging on both client and server side, and as I wrote the
problem is not that the close_notify is not sent but the IoProcessor at
the participant initiating the closure will terminate before the
close_notify message arrives as response to the closing from the other
side. It is sent, but not received.
Actually sending
close_notify message is not madatory in SSL, so it's OK IMO. But as
you pointed out, it's somewhat annoying. I don't have clear solution
for this for now. Any patch is welcome.
I was trying to figure out some fix, but so far nothing I could come up
with.
Cheers,
Andras
Thanks,
Trustin
