Increasing the maximum idle time

The maxIdleTime configuration property sets the maximum Idle time (in milliseconds) for a connection.

The Oracle Endeca Server comprises two main parts: The Oracle Endeca Server (a servlet deployed in Jetty), and the Dgraph process (a separate binary). Most queries to the Oracle Endeca Server are passed on to the Dgraph process for evaluation.

The Jetty default setting for the maxIdleTime property is 5 minutes (300000 milliseconds). This time-out can be triggered if evaluation time in the Dgraph process exceeds 5 minutes. If any queries sent to the Endeca Server are expected to take more than 5 minutes to process, this time-out should be increased.

The new value for maxIdleTime should be greater than your maximum expected query latency. It is desirable to never time out at this level, falling back to configurable time-outs in the Dgraph process or the client. We recommend a setting of 86400000 milliseconds (1 day).

Also note that this mechanism times out idle connections in Jetty both when reading from or writing to a connection to the servlet - it is simply the maximum amount of time that Jetty will wait for any information to travel in either direction.

To increase the maximum idle time:

  1. Stop the Oracle Endeca Server if it is running.
  2. Open the jetty.xml configuration file.
    The file is in the %EndecaServerInstall%/endeca-server/jetty-distribution-8.0.1.v20110908/etc directory.
  3. In the addConnector configuration section, increase the value for the maxIdleTime property, as in this example: 
    <Set name="maxIdleTime">86400000</Set>
  4. Save the file.
  5. Restart Oracle Endeca Server.