instantiated rails virtual host uses old timeout values

Discussion in 'Bug Reports' started by fantasydreaming, Dec 8, 2006.

  1. fantasydreaming

    fantasydreaming Well-Known Member

    There should be an abililty to change the LSAPI_MAX_IDLE=900 variable and the "Max Idle Time" (yes, both are set to the same value) under the "Context" => "Rails" section.

    I've tried changing it under the "Server" => "Rails" tab, but it's still using the default of 300, rather than 900 which I've set it to.

    2006-12-08 00:56:43.419 [INFO] [58.169.139.134:60061-0#ap] Connection idle time: 301 while in state: 2 watching for event: 25,close!
    2006-12-08 00:56:43.426 [INFO] [58.169.139.134:60061-0#ap] Content len: 15, Request line:
    POST /chat/say HTTP/1.1
    2006-12-08 00:56:43.426 [INFO] [58.169.139.134:60061-0#ap] Request body size: 15, received: 0.
    2006-12-08 05:08:11.209 [INFO] [63.16.156.168:1377-0#ap] Connection idle time: 301 while in state: 2 watching for event: 25,close!
     
  2. mistwang

    mistwang LiteSpeed Staff

    That's "Connection Timeout", how long the server keep a idle client connection alive, has nothing to do with ruby process idle time.
    You should change "Server"->"Tuning"->"Connection timeout" instead.
     

Share This Page