# Ruby LSAPI 1.9 + LSWS 2.2.2

**URL:** <https://www.ruby-forum.com/t/ruby-lsapi-1-9-lsws-2-2-2/69965>\
**Category:** Rails\
**Created:** [September 25, 2006, 10:55pm UTC](https://www.ruby-forum.com/t/ruby-lsapi-1-9-lsws-2-2-2/69965 "2006-09-25T22:55:58Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![finster](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/f/ac8455/32.png) [@finster](https://www.ruby-forum.com/u/finster)\
**Post date:** [September 25, 2006, 10:55pm UTC](https://www.ruby-forum.com/t/ruby-lsapi-1-9-lsws-2-2-2/69965/1 "2006-09-25T22:55:58Z")

</div>

Hi,

If you have been using or evaluating LiteSpeed web server + Ruby LSAPI  
setup for Rails application, please make sure your are using the latest  
release, Ruby LSAPI 1.9 and LSWS 2.2.2. We have been fixing a few bugs  
that causes DB connection errors, incompatibilities with WEBrick/Mongrel  
and ruby process management issues, currently, all bug reported has been  
addressed in timely manner and there is no outstanding issues. Thank you  
all who had submitted bug reports to us.

Best Regards,  
George W.

---

<div class="post-metadata">

**Author:** ![finster](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/f/ac8455/32.png) [@finster](https://www.ruby-forum.com/u/finster)\
**Post date:** [September 26, 2006, 5:27am UTC](https://www.ruby-forum.com/t/ruby-lsapi-1-9-lsws-2-2-2/69965/2 "2006-09-26T05:27:26Z")

</div>

On 9/26/06, George W. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> please make sure your are using the latest  
> release, Ruby LSAPI 1.9 and LSWS 2.2.2…  
> all bug reported has been  
> addressed in timely manner and there is no outstanding issues.

We have only problems with all Ruby LSAPI after version 1.6.

OS: Debian Sarge and Ubuntu Dapper  
Ruby: 1.8.4  
Rails: various, up to 1.1.6  
Litespeed: currently 2.2.2

We are using rubygems (ruby-lsapi) installation.

With ruby-lsapi-1.8 there was segfaults. The current 1.9 give us 503  
error after several minutes of usage. Only the 1.6 release is working  
without problems on the same systems.

---

<div class="post-metadata">

**Author:** ![finster](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/f/ac8455/32.png) [@finster](https://www.ruby-forum.com/u/finster)\
**Post date:** [September 26, 2006, 7:15am UTC](https://www.ruby-forum.com/t/ruby-lsapi-1-9-lsws-2-2-2/69965/3 "2006-09-26T07:15:39Z")

</div>

I’m running a free hosting site using LSWS 2.2.2 and LSAPI 1.9 - and  
it works like a charm. Yet to receive a single error.

Thanks,  
Pratik

On 9/25/06, Stoyan Z. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> OS: Debian Sarge and Ubuntu Dapper
> 
> >

–  
rm -rf / 2\>/dev/null - [http://null.in](http://null.in)

Dont judge those who try and fail, judge those who fail to try…

---

<div class="post-metadata">

**Author:** ![finster](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/f/ac8455/32.png) [@finster](https://www.ruby-forum.com/u/finster)\
**Post date:** [September 26, 2006, 9:13am UTC](https://www.ruby-forum.com/t/ruby-lsapi-1-9-lsws-2-2-2/69965/4 "2006-09-26T09:13:45Z")

</div>

On 9/26/06, Pratik [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> I’m running a free hosting site using LSWS 2.2.2 and LSAPI 1.9 - and  
> it works like a charm. Yet to receive a single error.

/opt/lsws/logs/stderr.log

/opt/rubygems/gems/ruby-lsapi-1.9/lib/lsapi.so: warning: already  
initialized constant ENV  
/opt/lsws/fcgi-bin/RailsRunner.rb:11:in `replace': method `respond\_to?’ called on terminated object (0x40acdd30)  
(NotImplementedError)  
from /opt/lsws/fcgi-bin/RailsRunner.rb:11

---

<div class="post-metadata">

**Author:** ![finster](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/f/ac8455/32.png) [@finster](https://www.ruby-forum.com/u/finster)\
**Post date:** [September 27, 2006, 7:47pm UTC](https://www.ruby-forum.com/t/ruby-lsapi-1-9-lsws-2-2-2/69965/5 "2006-09-27T19:47:39Z")

</div>

Thanks Stoyan, I think I figured out what exactly causes this bug, that  
because “env\_copy” has been garbage collected.  
The bug should be fixed in ruby-lsapi 1.10, anyone who get 503 errors,  
please uninstall 1.9 and try 1.10 attached.

Or get it from  
[http://www.litespeedtech.com/packages/lsapi/ruby-lsapi-1.10.tar.gz](http://www.litespeedtech.com/packages/lsapi/ruby-lsapi-1.10.tar.gz)

Thanks,  
George W.

---

<div class="post-metadata">

**Author:** ![finster](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/f/ac8455/32.png) [@finster](https://www.ruby-forum.com/u/finster)\
**Post date:** [September 26, 2006, 6:49pm UTC](https://www.ruby-forum.com/t/ruby-lsapi-1-9-lsws-2-2-2/69965/6 "2006-09-26T18:49:33Z")

</div>

Hi Stoyan Z.,

Can you please fill a bug report on our forum, we need to more  
information to address this issue. It will be really great if we can  
access your test server if there is one.

We can exchange more information off the list.

Best Regards,  
George W.
