Details
-
Type:
Bug
-
Status:
Resolved
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 6.1.0pre0
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Environment:Using the SslEnging connector using test webapp
-
Number of attachments :
Description
I occassionally get messages like:
bytesConsumed = 0 bytesProduced = 0
2006-11-05 14:41:18.423::WARN: unwrap Status = BUFFER_OVERFLOW HandshakeStatus = NEED_UNWRAP
The web app appears to work OK.
This is a warning message when the call to unwrap in the fill method results in a BUFFER_OVERFLOW. SslEngine documentation states BUFFER_OVERFLOW after unwrapping means that there is not enough destination buffer space available and that it should be reallocated to the sslsession.getApplicationBufferSize. In our case, the destination buffer is the passed in buffer who's buffer size is already set. Since the passed in buffer's size has already been allocated elsewhere, I just threw an exception when I get a buffer_overflow instead of reallocating to the packetbuffersize. It didn't seem to have any adverse effects since all the tests I made against it have been working. Any suggestions on how to handle this better?