On Sun, Nov 10, 2013 at 5:08 PM, Igor Cicimov <icici...@gmail.com> wrote:
> > In my experience SocketTimeoutException comes up in case of misbehaving > browser (read IE 8 and older), i.e. the client fails to send the complete > request and the socket timeout strikes. interesting, thanks. This error occurs when different endusers are accessing web application via Google Chrome on Android tablet or phone, and Google Chrome (or Safari) on iPad. > > You don't provide information about the Java and OS version you are running > your app on since this might be related to one of them (or maybe I missed > that info). my apologies, JVM: Java HotSpot(TM) 64-Bit Server VM (24.45-b08, mixed mode) Java: version 1.7.0_45, vendor Oracle Corporation OS: Microsoft Windows Server 2008 R2 64-bit > For Sun Java for example you can try the following: > > -Dsun.net.client.defaultReadTimeout=1800000 > > which will increase the socket timeout to 30 minutes lets say if the > default one is not enough in case or slow client. Another thing to check is > your OS socket timeout setting, on linux systems for example: > > net.ipv4.tcp_keepalive_time = 300 > > and try adjusting it according to your needs. > noted, thanks. > > Would love to hear some other people experiences and thoughts regarding > this as well, this is really annoying one to troubleshoot. > agreed/ditto. thanks for your response.
