HTTP Connection Timeout

HTTP Connection Timeout

Applies to

Alert
All versions of Cryptshare Server

Symptom

HTTP connections are interrupted either when performing downloads or uploads. The Cryptshare error log shows messages like this one:

Notes
Logview

[...]
    at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
    at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.wicket.protocol.http.servlet.ResponseIOException: java.io.IOException: java.util.concurrent.TimeoutException: Idle timeout expired: 10000/10000 ms
    at org.apache.wicket.protocol.http.servlet.ServletWebResponse.write(ServletWebResponse.java:139)
    at org.apache.wicket.protocol.http.HeaderBufferingWebResponse.write(HeaderBufferingWebResponse.java:191)
    at org.apache.wicket.request.Response$StreamAdapter.write(Response.java:148)
    at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
    at java.io.BufferedOutputStream.write(BufferedOutputStream.java:126)
    at com.befinesolutions.cryptshare.server.business.Crypt$Decrypter.decrypt(wk:212)
    ... 38 common frames omitted
Caused by: java.io.IOException: java.util.concurrent.TimeoutException: Idle timeout expired: 10000/10000 ms
    at org.eclipse.jetty.util.SharedBlockingCallback$Blocker.block(SharedBlockingCallback.java:234)
    at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:141)
    at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:378)
    at org.apache.wicket.protocol.http.servlet.ServletWebResponse.write(ServletWebResponse.java:135)
    ... 43 common frames omitted
[...]

Cause

The Client the user is currently working on, has a bad connection to the Cryptshare Server or the server load is currently to high, so that new requests cannot be handled in time. Open HTTP-Connections are running into the pre-configured connection timeout. 

Solution

If the server is not under high load and should therefore be able to handle the request properly, the connection timeout can be increased so slow connections will be kept open for a longer time.

1. Open the Jetty configuration file for the User Interface:

<installation directory>/resources/WEB-INF/ui-config.xml

2. Search for a 'Set'-Tag with the attribute 'idleTimeout' (2 times). 


3. Change the value from '10000' milliseconds to the preferred value (recommended maximum is '60000')

4. Save the changes and restart the Cryptshare Server

    • Related Articles

    • The Cryptshare Server becomes unresponsive under high load.

      Applies to: All versions of Cryptshare Server Symptom: The Cryptshare Server responds slowly when it is used by a large amount of users at a time. Cause: The Cryptshare Server tries to respond to all requests but cannot answer the requests faster ...

    • Error code 5000

      Applies to: All versions of Cryptshare for Notes Situation: Error code 5000 in Cryptshare for Notes application Cause: This error code occurs, if the Domino Server and the Cryptshare Server cannot establish a connection. Solution: Check Firewall, ...

    • Improve performance for systems under high load

      Inhaltsverzeichnis 1 Applies to: 2 Purpose: 3 Solution: 3.1 1. Update Cryptshare Server 3.2 2. Check system hardware 3.3 3. Assign more memory to Cryptshare application 3.4 4. Change Guest OS settings 3.5 5. Adjust the Web Server Configuration ...

    • Configuring the Cryptshare Appliance to use a proxy server

      Applies to: All versions of Cryptshare Appliance Purpose: The Operating System of the Cryptshare Appliance needs to know the Proxy Settings to get the connection to the internet, e.g. to install OS patches, update the antivirus database etc. ...

    • File pre-processing errors with ClamAV

      Applies to: All Linux-based Cryptshare Servers Symptoms: Several users report that after the file upload has finished, the following message is shown: The following warnings may be shown in the logs: WARN yyyy-mm-dd hh:MM:SS FileProcessorService - ...