Search results

  1. M

    Is the LiteSpeed Ruby LSAPI my best choice?

    Should be soon. In the final packing stage. Will let you known when the package is ready.
  2. M

    Rails/lsapi spawns too many processes under heavy load

    Have you patch the code to stop spawning extra? Some ruby functions may fork, like popen() or popen3(). It should not be lsapi forking again from a child process. Maybe you can strace that process to figure something out. :)
  3. M

    Is the LiteSpeed Ruby LSAPI my best choice?

    It is a layer7 content aware, session aware load balancer, which support HTTP, LSAPI, FCGI and AJP backends. It can direct request to different backend based on domain names, URL, Session, etc. It supports URL rewrite and request filtering. Load balancing algorithms are: round-robin, least load...
  4. M

    LiteSpeed not honoring my optimistic locking setting

    Please verify that WEBrick is started in production mode if LiteSpeed is in production mode. LiteSpeed will not touch connection properties. However, for technical reason, LSAPI closes all ActiveRecord connections after Rails framework initialization before forking a child process, and the...
  5. M

    Client never gets server response

    You can turn on LSWS debug logging by set "Debug Level" to "HIGH" at server level. You need to increase http://www.litespeedtech.com/docs/webserver/config/tuning/#connTimeout http://www.litespeedtech.com/docs/webserver/config/extapps/#initTimeout under ruby tab. Make sure to leave enough...
  6. M

    lot's of Failed to open file

    Are *.lsz file there? Maybe you need to fix the fill permission. If you css or js file changed, you need to do the above command again to regenerate the cache.
  7. M

    changing content-type on reverse proxy

    LiteSpeed can add "; charset=", but cannot remove it from a response header. Why do you need to do that? Usually, charset is useful. Anyway, you need to fix it from the external app side.
  8. M

    Rewrite Engine does not pick up correct REQUEST_FILENAME when using PATH_INFO

    This problem should be fixed in 3.0.3
  9. M

    Rewrite Engine does not pick up correct REQUEST_FILENAME when using PATH_INFO

    The rewrite engine in LiteSpeed 3 has been changed a little bit to match the behavior of Apache's. We will investigate.
  10. M

    Rails/lsapi spawns too many processes under heavy load

    Hi Kevin, You can manually patch the lsapilib.c to turn it off around line 1692, change if ( pServer->m_iCurChildren >= (pServer->m_iMaxChildren << 1 ) ) to if ( pServer->m_iCurChildren >= (pServer->m_iMaxChildren ) ) recompile then install, this should disable all temporary processes. For...
  11. M

    Setting Litespeed up on port 80

    does not work, should change it to "128.178.156.236:80", and remove the other listener. Change <vhostMapList> section to <vhostMapList> <vhostMap> <vhost>routerank</vhost> <domain>rrg.epfl.ch</domain> </vhostMap> <vhostMap>...
  12. M

    Subversion support?

    Here is one PHP based. http://websvn.tigris.org/
  13. M

    Subversion support?

    A Rails plugin for browsing svn repositories. https://bssvnbrowser.bountysource.com/
  14. M

    Subversion support?

    There are svn module available for PHP, Perl, Python as well as for Ruby, I believe. http://pecl.php.net/package/svn http://svn.collab.net/repos/svn/trunk/subversion/bindings/swig/ruby/ libsvn-ruby, etc If the svn traffic is not very high, you can write scripts using the svn bindings.
  15. M

    Setting Litespeed up on port 80

    I think you'd better not proxying through Apache if you want to comapre something. Everything can be done via LiteSpeed. You need to use name based vhost, for example, using IP address for admin, domain name for your rails app. First, setup admin on port 80, setup rails app on port 8088 or...
  16. M

    Subversion support?

    Yes, right now proxying to backend apache is the only solution. However, we don't aware any problem with proxying WebDAV requests. We are interested in sponsoring a open source mod_subversion equivalent LSAPI implementation, if anyone are interested, just contact us.
  17. M

    Setting Litespeed up on port 80

    You can setup a proxy on port 80 or 443, forward requests to admin console on port 7080.
  18. M

    [WARN] Can't find ruby interpreter

    We will have this issue addressed in 3.0.3 release.
  19. M

    Virtual Host List Not Updating on CP

    Please try a restart from command line, maybe the restart from admin console did not really work, control panel will show the current mapping after the change has been applied successfully.
Top