>
> Thanks for your answer Jens, I am new to GWT so I don't know if my next
> question is doable or not. From logs I can see that the service is still
> running on the server after I get the alert message. So when I detect this
> error can I go back and restart another callback that will wait
On 02/24/2014 01:16 PM, Jeffrey Argo wrote:
Thanks for your answer Jens, I am new to GWT so I don't know if my
next question is doable or not. From logs I can see that the service
is still running on the server after I get the alert message. So when
I detect this error can I go back and restar
Thanks for your answer Jens, I am new to GWT so I don't know if my next
question is doable or not. From logs I can see that the service is still
running on the server after I get the alert message. So when I detect this
error can I go back and restart another callback that will wait again for
TLS defines the alert protocol and alert code 21 means "Decryption failed",
see: http://en.wikipedia.org/wiki/Transport_Layer_Security#Alert_protocol
Quoting wikipedia:
*"This record should normally not be sent during normal handshaking or
application exchanges. However, this message can be s
HI,
I am working on an application that is deployed on Tomcat 7.0 and when I
make a RPC call from the client to the server after 1 minute the connection
is reset, because of an Alert Encrypted message from the server. The alert
message type is a 21, which means that the connection should be re