On 12/05/2016 06:16, Tejas Nandanikar wrote:
> I am using Apache Tomcat 8.0.33.
> I was going through Java documentation about RemoteEndpoint.Basic
> which says that sendText(String text) blocks until all of the message
> has been transmitted.
> But I noticed that when the client loses internet con
Thank you for your quick reply.
So consider a case where client abruptly loses internet connection.
In that scenario, the sendText() would return normally as the server
hasn't received 'close' packet from the client, did I get it right?
On Thu, May 12, 2016 at 12:43 PM, Mark Thomas wrote:
> On 12
On 12/05/2016 08:24, Tejas Nandanikar wrote:
> Thank you for your quick reply.
> So consider a case where client abruptly loses internet connection.
> In that scenario, the sendText() would return normally as the server
> hasn't received 'close' packet from the client, did I get it right?
Assuming
Isn't there any workaround to this situation? In my application, a
database update operation depends on whether the message was delivered
to the client or not, so in that scenario, I would never know if the
message was delivered. And even if onError() is called later, I can
never know which message
On 10/05/2016 22:00, Thomas Meyer wrote:
> Hi,
>
> I noticed that I can block tomcat 8 by opening 200 connection to the
> http 1.1 connector and send 512 bytes of zero in each connection.
>
> Tomcat 8 seems to block in parseRequestLine() method for 20 seconds
> (connectionTimeout) and times out a
Hi,
short update: I got HTTP/2 with Apache Wicket running on Jetty, now.
Sadly I couldn't solve the issues with Tomcat. :-(
kind regards
Tobias
> Am 05.04.2016 um 05:00 schrieb Christopher Schultz
> :
>
> Tobias,
>
>> On 4/4/16 4:49 AM, Tobias Soloschenko wrote:
>> I just figured out that t
