Yes it does without any error. I have tested 10 times with no errors
which never happened before and the value of int b does not affected
int rsv. So as far after these test I claim it is fixed in at least
7.0.53. I also filed a bug report for tomcat 7.0.53 and explained the
bug and the solution
I have tomcat 7.0.53 and have been having a problem with the following
error when sending a binary message CloseReason: code [1002], reason
[The client frame set the reserved bits to [x] which was not supported
by this endpoint] where x is between 1-7 when printed out. So I
remote debugged and
On 04/12/2014 15:26, Jason Ricles wrote:
I have tomcat 7.0.53 and have been having a problem with the following
error when sending a binary message CloseReason: code [1002], reason
[The client frame set the reserved bits to [x] which was not supported
by this endpoint] where x is between 1-7
Due to some regulations out of my control right now we can only use
tomcat 7.0.53. I also did a wireshark bug trace and going over the
line the reserved bits are 0 but when computed in tomcat that is when
the reserved are set to invalid bits. Is there any possible solution
or am I just out of luck
On 04/12/2014 18:04, Jason Ricles wrote:
Due to some regulations out of my control right now we can only use
tomcat 7.0.53. I also did a wireshark bug trace and going over the
line the reserved bits are 0 but when computed in tomcat that is when
the reserved are set to invalid bits. Is there
Well the trace is fine so I will upgrade and try and see what happens.
If it is not fixed I assume I should file a bug report.
On Thu, Dec 4, 2014 at 1:19 PM, Mark Thomas ma...@apache.org wrote:
On 04/12/2014 18:04, Jason Ricles wrote:
Due to some regulations out of my control right now we can
Yes it was a bug so we will try to get a waiver to use 7.0.57 for our
environment instead of 7.0.53
On Thu, Dec 4, 2014 at 1:20 PM, Jason Ricles jgr...@alum.lehigh.edu wrote:
Well the trace is fine so I will upgrade and try and see what happens.
If it is not fixed I assume I should file a bug
On 12/4/2014 4:32 PM, Jason Ricles wrote:
Yes it was a bug so we will try to get a waiver to use 7.0.57 for our
environment instead of 7.0.53
So it works as expected in 7.0.57?
On Thu, Dec 4, 2014 at 1:20 PM, Jason Ricles jgr...@alum.lehigh.edu wrote:
Well the trace is fine so I will
