Deadlock bettween two SSLEngines

Question

This may be related to my previous post or may be a different issue. I have the same implementation of my SSLEngine running in client and server...here is what occurs between the two SSLEngines
client writes 100 bytes, server receives
server writes 1217 bytes back, client receives
client writes 139 bytes
client writes 6 bytes
client writes 53 bytes (SSLEngine status goes from WRAP to UNRWAP)
server receives 100 bytes
server receives 98 bytes (SSLEngine status stays in UNWRAP)
This is very similar to my previous post...all the packet sizes are the same, but the server received the 6 bytes and processed the handshake until the failure exception I posted. If it receives all the bytes, it all the sudden doesn't process it and waits for more while the client has no more to send.
What in the world could be going on? Thanks for any ideas,
dean

Answer 1

I think I figured this out, but I still have a deadlock and this time I kind of know what it is....with my fixed code, it is doing this
Last few exchanges.....
client send 6 bytes(status=OK, hsStatus=NEEDWRAP)
client send 53 bytes(status=OK, hsStatus=NEEDUNWRAP)
server receives 59 bytes(status=OK, hsStatus=NEEDUNWRAP)
I notice that when I fed the 59 bytes to the SSLEngine, it only read 6 bytes and did not read up to the 59. I am assuming the engine is missing these bytes and needs them refed to it.....there is a problem with this though.....how do I know when to stop refeeding bytes to the engine and when to get more from the socket as it doesn't have enough.....
I guess I loop till are bytes are consumed.....I will have to go try that.