[Bug 55233] [websocket] Problem reading many subsequent binary messages

2013-07-11 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=55233 --- Comment #4 from Stoyan Boshev --- I have rerun the tests. Everything is working fine now. Mark, thanks a lot for your prompt reaction and fixes! -- You are receiving this mail because: You are the assignee for the bug. -

[Bug 55233] [websocket] Problem reading many subsequent binary messages

2013-07-11 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=55233 Mark Thomas changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 55233] [websocket] Problem reading many subsequent binary messages

2013-07-11 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=55233 --- Comment #2 from Stoyan Boshev --- With the updated code the error messages are always the same: Connection closed: Buffer overflow. [16,916] bytes to write into a [8,192] byte buffer that already contained [0] bytes. Connection closed:

[Bug 55233] [websocket] Problem reading many subsequent binary messages

2013-07-10 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=55233 --- Comment #1 from Mark Thomas --- I've improved the error message so it now reports exactly how many bytes the SSLEngine needs to write. The fix I suspect will be required looks like it will need some fairly major surgery to the current c