Mongrel users - Dec 2006 - running mongrel in production on win32

Hey guys, I''m running the mongrel server that comes with rails-1.2rc1
for development on a winxp box, anticipating taking it into production
on a win2k3 box in the next few weeks. I''ve had a couple of crashes
occur during development that give me pause, however. I made a ticket
for the last one here:

http://dev.rubyonrails.org/ticket/6841

I know, or at least believe, that mongrel isn''t responsible for these,
but I''m curious if or how folks maintain stable production services
relying on mongrel on win32. If installed as a service, does the service
restart cleanly if the mongrel instance crashes? (I''ve seen reports to
indicate this is not the case.) Am I just asking for trouble pursuing
this as a production environment? Is the mongrel_cluster code ready for
primetime on win32 yet?

Thanks for any tips. Cheers.

- donald

On 12/15/06, Ball, Donald A Jr (Library) <donald.ball at nashville.gov>
wrote:
> Hey guys, I''m running the mongrel server that comes with
rails-1.2rc1
> for development on a winxp box, anticipating taking it into production
> on a win2k3 box in the next few weeks.
Ok, which version of mongrel is bundled with rails-1.2? Please list
the gems you have installed, because, AFAIK, script\server will only
load mongrel if the gem is found.

You are starting it using mongrel_rails or script/server?
> I''ve had a couple of crashes
> occur during development that give me pause, however. I made a ticket
> for the last one here:
>
> http://dev.rubyonrails.org/ticket/6841
That bug seems weird, also unrelated to rails but Ruby itself.
>
> I know, or at least believe, that mongrel isn''t responsible for
these,
> but I''m curious if or how folks maintain stable production
services
> relying on mongrel on win32. If installed as a service, does the service
> restart cleanly if the mongrel instance crashes? (I''ve seen
reports to
> indicate this is not the case.) Am I just asking for trouble pursuing
> this as a production environment? Is the mongrel_cluster code ready for
> primetime on win32 yet?
>
Lastest mongrel_service gem provide what you need, if somehow the ruby
process die (due a unhandled exception) the service will automatically
spawn a new one.

There is no way (yet, still need to test some things) to monitor
deeply if the ruyb process hang and not die.

The mongrel_cluster base his "magic" on daemonize, which requires
fork() and isn''t compatible with win32.

Its planned for mongrel_service to provide this functionality, maybe
during january.
> Thanks for any tips. Cheers.
>
> - donald
Will be very helpful if you provide more information about your
database (and version), mongrel, rails, ruby and windows version to we
could get a better picture of your situation.

Regards and good weekend,

-- 
Luis Lavena
Multimedia systems
-
Leaders are made, they are not born. They are made by hard effort,
which is the price which all of us must pay to achieve any goal that
is worthwhile.
Vince Lombardi

> On 12/15/06, Ball, Donald A Jr (Library) 
> <donald.ball at nashville.gov> wrote:
> > Hey guys, I''m running the mongrel server that comes with 
> rails-1.2rc1 
> > for development on a winxp box, anticipating taking it into 
> production 
> > on a win2k3 box in the next few weeks.
> 
> Ok, which version of mongrel is bundled with rails-1.2? 
> Please list the gems you have installed, because, AFAIK, 
> script\server will only load mongrel if the gem is found.
I''m using mongrel-0.3.13.3-mswin32, the latest publicly available
mswin32 gem, along with mongrel_service-0.2, though I''m not using the
service in development. I tried to install 0.3.19 but got odd
compilation warnings when I did so and the server failed to start.
> You are starting it using mongrel_rails or script/server?
script/server
> > I''ve had a couple of crashes
> > occur during development that give me pause, however. I 
> made a ticket 
> > for the last one here:
> >
> > http://dev.rubyonrails.org/ticket/6841
> 
> That bug seems weird, also unrelated to rails but Ruby itself.
So you believe I''ve run into a bug in ruby-1.8.4-mswin32? Looked to me
more like an unhandled exception in activesupport, but the rails folks
seemed to think that was not the case.
> Lastest mongrel_service gem provide what you need, if somehow 
> the ruby process die (due a unhandled exception) the service 
> will automatically spawn a new one.
I''ll give that a whirl, thanks! Would the log files indicate when/if
this occurs?
> There is no way (yet, still need to test some things) to 
> monitor deeply if the ruyb process hang and not die.
> 
> The mongrel_cluster base his "magic" on daemonize, which requires
> fork() and isn''t compatible with win32.
> 
> Its planned for mongrel_service to provide this 
> functionality, maybe during january.
If I can help in this endeavor in any way, please let me know. I''m a
beginning ruby developer, but I''ve been doing web development for time
out of mind and I have a copy of visual studio 2003 if needed for
compilation.
> Will be very helpful if you provide more information about 
> your database (and version), mongrel, rails, ruby and windows 
> version to we could get a better picture of your situation.
Sure thing. I''m using mssql2k with the ADO driver, mongrel-0.3.13.3,
rails-1.2rc1, ruby-1.8.4, winxpsp2 (but will be deploying to win2k3). I
am using RMagick with file_column, though the crashes have not (yet)
occurred while testing that portion of the application.
> Regards and good weekend,
Thanks for your help and for your work in providing rails folks with a
potentially workable solution for win32 deployment! It would not be my
choice for a production environment, but it''s out of my hands.

- donald

On 12/15/06, Ball, Donald A Jr (Library) <donald.ball at nashville.gov>
wrote:
> > On 12/15/06, Ball, Donald A Jr (Library)
> > <donald.ball at nashville.gov> wrote:
> > > Hey guys, I''m running the mongrel server that comes with
> > rails-1.2rc1
> > > for development on a winxp box, anticipating taking it into
> > production
> > > on a win2k3 box in the next few weeks.
> >
> > Ok, which version of mongrel is bundled with rails-1.2?
> > Please list the gems you have installed, because, AFAIK,
> > script\server will only load mongrel if the gem is found.
>
> I''m using mongrel-0.3.13.3-mswin32, the latest publicly available
> mswin32 gem, along with mongrel_service-0.2, though I''m not using
the
> service in development. I tried to install 0.3.19 but got odd
> compilation warnings when I did so and the server failed to start.
>
That is the *latest* stable gem available via rubyforge, but no the latest one:

http://rubyforge.org/pipermail/mongrel-users/2006-December/002352.html
>From my site you could download the pre-compiled win32 gem based on
latest svn. Just change 0.3.18 to 0.3.20 and you''re done.

Install it manually using ''gem install'' and the full pathname,
including extension of the gem file.
> > You are starting it using mongrel_rails or script/server?
>
> script/server
>
Then is rails which is loading mongrel, and not the way around. Please
try doing:

mongrel_rails start

inside your application folder and see if that report any problem
> > > I''ve had a couple of crashes
> > > occur during development that give me pause, however. I
> > made a ticket
> > > for the last one here:
> > >
> > > http://dev.rubyonrails.org/ticket/6841
> >
> > That bug seems weird, also unrelated to rails but Ruby itself.
>
> So you believe I''ve run into a bug in ruby-1.8.4-mswin32? Looked
to me
> more like an unhandled exception in activesupport, but the rails folks
> seemed to think that was not the case.
>
Its look like a bug with the GC, but I only could say that if your
application isn''t doing something memory intensive or nasty to the
whole Ruby VM.
> > Lastest mongrel_service gem provide what you need, if somehow
> > the ruby process die (due a unhandled exception) the service
> > will automatically spawn a new one.
>
> I''ll give that a whirl, thanks! Would the log files indicate
when/if
> this occurs?
>
The current mongrel_service will report when something like that
happens, but, mea culpa, I forgot to include timestamp information of
that! (will do a fix in the svn).
> > There is no way (yet, still need to test some things) to
> > monitor deeply if the ruyb process hang and not die.
> >
> > The mongrel_cluster base his "magic" on daemonize, which
requires
> > fork() and isn''t compatible with win32.
> >
> > Its planned for mongrel_service to provide this
> > functionality, maybe during january.
>
> If I can help in this endeavor in any way, please let me know. I''m
a
> beginning ruby developer, but I''ve been doing web development for
time
> out of mind and I have a copy of visual studio 2003 if needed for
> compilation.
>
So far testing for one or N child process is the same, I''ll want to
test the single service a bit longer to iron the logging issues it
currently present (or lack of).
> > Will be very helpful if you provide more information about
> > your database (and version), mongrel, rails, ruby and windows
> > version to we could get a better picture of your situation.
>
> Sure thing. I''m using mssql2k with the ADO driver,
mongrel-0.3.13.3,
> rails-1.2rc1, ruby-1.8.4, winxpsp2 (but will be deploying to win2k3). I
> am using RMagick with file_column, though the crashes have not (yet)
> occurred while testing that portion of the application.
>
Ok, are you sure about RMagick? you know when your application
crashes? doing what, which kind of request, the exact line of the
controller or something?

The stack trace on this situation will be very helpful.

Based on some web searching, the "rb_gc_mark: unknown data type" bug
is related to some memory allocated that didn''t conform any of the
known data types by the Garbage Collector.

Maybe some C extension (RMagick or any other) is allocating memory and
not freeing it in the right way.
> > Regards and good weekend,
>
> Thanks for your help and for your work in providing rails folks with a
> potentially workable solution for win32 deployment! It would not be my
> choice for a production environment, but it''s out of my hands.
>
You''re welcome, but you should thank a lot of ppl, win32utils guys and
Zed for their work directly or indirectly to this :-)

Regards and good weekend.

-- 
Luis Lavena
Multimedia systems
-
Leaders are made, they are not born. They are made by hard effort,
which is the price which all of us must pay to achieve any goal that
is worthwhile.
Vince Lombardi

> > I''m using mongrel-0.3.13.3-mswin32, the latest publicly
available
> > mswin32 gem, along with mongrel_service-0.2, though I''m not 
> using the 
> > service in development. I tried to install 0.3.19 but got odd 
> > compilation warnings when I did so and the server failed to start.
> 
> That is the *latest* stable gem available via rubyforge, but 
> no the latest one:
> 
> http://rubyforge.org/pipermail/mongrel-users/2006-December/002352.html
huh, that''s handy, might be worthwhile posting that on the mongrel site
somewhere if you want to encourage win32 users to test it.
> Then is rails which is loading mongrel, and not the way 
> around. Please try doing:
> 
> mongrel_rails start
> 
> inside your application folder and see if that report any problem
Sure. Actually, I have a problem to report already... sessions are not
working when I start mongrel in this fashion. Is there somewhere i
should be configuring session behavior that I''m not?

To be more specific, the browser doesn''t report a session_id cookie in
its cookie list. The server-side code happily stores objects in the
session, but the session is empty on the next request.

For the record, both webrick and mongrel started via script/server have
working sessions.
> > So you believe I''ve run into a bug in ruby-1.8.4-mswin32? 
> Looked to me 
> > more like an unhandled exception in activesupport, but the 
> rails folks 
> > seemed to think that was not the case.
> 
> Its look like a bug with the GC, but I only could say that if 
> your application isn''t doing something memory intensive or 
> nasty to the whole Ruby VM.
I can pretty much guarantee that''s not the case. It''s a very
vanilla
application, the most weird thing I''m doing is a lot of screen scraping
with Mechanize.
> The current mongrel_service will report when something like 
> that happens, but, mea culpa, I forgot to include timestamp 
> information of that! (will do a fix in the svn).
Cool. Note I haven''t yet installed or tested mongrel_service, hope to
be
able to do that soon.
> > > Will be very helpful if you provide more information about your 
> > > database (and version), mongrel, rails, ruby and windows 
> version to 
> > > we could get a better picture of your situation.
> >
> > Sure thing. I''m using mssql2k with the ADO driver, 
> mongrel-0.3.13.3, 
> > rails-1.2rc1, ruby-1.8.4, winxpsp2 (but will be deploying 
> to win2k3). 
> > I am using RMagick with file_column, though the crashes 
> have not (yet) 
> > occurred while testing that portion of the application.
> 
> Ok, are you sure about RMagick? you know when your 
> application crashes? doing what, which kind of request, the 
> exact line of the controller or something?
Well, it''s only crashed twice, with different stacktraces, so searching
for a common proximate cause is likely to be a fruitless endeavor. I''ll
be sure to save all the information if this recurs in the future.

Appreciate the time and advice, and I look forward to helping you get
mongrel for win32 ready for production use.

- donald

> Sure. Actually, I have a problem to report already... 
> sessions are not working when I start mongrel in this 
> fashion. Is there somewhere i should be configuring session 
> behavior that I''m not?
> 
> To be more specific, the browser doesn''t report a session_id 
> cookie in its cookie list. The server-side code happily 
> stores objects in the session, but the session is empty on 
> the next request.
> 
> For the record, both webrick and mongrel started via 
> script/server have working sessions.
The problem turns out to be fairly simple, but it''s beyond my
capability
to fix. The problem is that mongrel is only passing one and only one
cookie on to the user. If that''s _session_id, great, but if
it''s one of
the other cookies that I''m creating, the user''s session is
lost.

To be clear, I''m using mongrel-0.3.18 from Luis. Note that I was
incorrect when I said the problem didn''t occur when mongrel is stared
with script\server. Mongrel has this problem regardless, while webrick
works fine.

- donald

This is something I mentioned on here to Zed, and he said it will be
fixed coming up with the next release.

I do know that 0.3.14 works, which I believe was the last stable
release for ruby (and 0.3.13 which was the windows stable release?)

On 12/19/06, Ball, Donald A Jr (Library) <donald.ball at nashville.gov>
wrote:
> > Sure. Actually, I have a problem to report already...
> > sessions are not working when I start mongrel in this
> > fashion. Is there somewhere i should be configuring session
> > behavior that I''m not?
> >
> > To be more specific, the browser doesn''t report a session_id
> > cookie in its cookie list. The server-side code happily
> > stores objects in the session, but the session is empty on
> > the next request.
> >
> > For the record, both webrick and mongrel started via
> > script/server have working sessions.
>
> The problem turns out to be fairly simple, but it''s beyond my
capability
> to fix. The problem is that mongrel is only passing one and only one
> cookie on to the user. If that''s _session_id, great, but if
it''s one of
> the other cookies that I''m creating, the user''s session
is lost.
>
> To be clear, I''m using mongrel-0.3.18 from Luis. Note that I was
> incorrect when I said the problem didn''t occur when mongrel is
stared
> with script\server. Mongrel has this problem regardless, while webrick
> works fine.
>
> - donald
> _______________________________________________
> Mongrel-users mailing list
> Mongrel-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>

You should upgrade to the newest version: 0.3.20 as it allows multiple
Set-Cookie header statements.

For reference:http://mongrel.rubyforge.org/news.html

To Install:
$ gem install fastthread --source=http://mongrel.rubyforge.org/releases
$ gem install mongrel --source=http://mongrel.rubyforge.org/releases

Then you should be back on track :)

.: Michael :.


On 12/19/06, Ball, Donald A Jr (Library) <donald.ball at nashville.gov>
wrote:
>
> > Sure. Actually, I have a problem to report already...
> > sessions are not working when I start mongrel in this
> > fashion. Is there somewhere i should be configuring session
> > behavior that I''m not?
> >
> > To be more specific, the browser doesn''t report a session_id
> > cookie in its cookie list. The server-side code happily
> > stores objects in the session, but the session is empty on
> > the next request.
> >
> > For the record, both webrick and mongrel started via
> > script/server have working sessions.
>
> The problem turns out to be fairly simple, but it''s beyond my
capability
> to fix. The problem is that mongrel is only passing one and only one
> cookie on to the user. If that''s _session_id, great, but if
it''s one of
> the other cookies that I''m creating, the user''s session
is lost.
>
> To be clear, I''m using mongrel-0.3.18 from Luis. Note that I was
> incorrect when I said the problem didn''t occur when mongrel is
stared
> with script\server. Mongrel has this problem regardless, while webrick
> works fine.
>
> - donald
> _______________________________________________
> Mongrel-users mailing list
> Mongrel-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/mongrel-users/attachments/20061219/a0a9b656/attachment.html

Sadly, I cannot upgrade to 0.3.20 as I''m on win32, there''s no
gem
available for it yet, and I apparently cannot compile the http parser
(nmake launches cl.exe which complains:
 
c:\ruby\lib\ruby\1.8\i386-mswin32\config.h(2) : fatal error C1189:
#error :  MSC version unmatch
 
(In point of fact, this error message was from trying to install 0.3.19,
but the point remains - mswin32 users seem to need precompiled gems.)
 
- donald
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/mongrel-users/attachments/20061219/3f6df518/attachment.html

Gives you 0.3.19
$ gem install mongrel --source=http://mongrel.rubyforge.org/releases

Gives you 0.3.20
$ gem install mongrel --source=http://mongrel.rubyforge.org/releases/

just FYI


On 12/19/06, Michael D''Auria <michael.dauria at gmail.com>
wrote:
> You should upgrade to the newest version: 0.3.20 as it allows multiple
> Set-Cookie header statements.
>
> For reference:http://mongrel.rubyforge.org/news.html
>
> To Install:
> $ gem install fastthread
> --source=http://mongrel.rubyforge.org/releases
> $ gem install mongrel
> --source=http://mongrel.rubyforge.org/releases
>
> Then you should be back on track :)
>
> .: Michael :.
>
>
> On 12/19/06, Ball, Donald A Jr (Library) <donald.ball at
nashville.gov> wrote:
> > > Sure. Actually, I have a problem to report already...
> > > sessions are not working when I start mongrel in this
> > > fashion. Is there somewhere i should be configuring session
> > > behavior that I''m not?
> > >
> > > To be more specific, the browser doesn''t report a
session_id
> > > cookie in its cookie list. The server-side code happily
> > > stores objects in the session, but the session is empty on
> > > the next request.
> > >
> > > For the record, both webrick and mongrel started via
> > > script/server have working sessions.
> >
> > The problem turns out to be fairly simple, but it''s beyond my
capability
> > to fix. The problem is that mongrel is only passing one and only one
> > cookie on to the user. If that''s _session_id, great, but if
it''s one of
> > the other cookies that I''m creating, the user''s
session is lost.
> >
> > To be clear, I''m using mongrel-0.3.18 from Luis. Note that I
was
> > incorrect when I said the problem didn''t occur when mongrel
is stared
> > with script\server. Mongrel has this problem regardless, while webrick
> > works fine.
> >
> > - donald
> > _______________________________________________
> > Mongrel-users mailing list
> > Mongrel-users at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/mongrel-users
> >
>
>
> _______________________________________________
> Mongrel-users mailing list
> Mongrel-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
>

On 12/19/06, Michael D''Auria <michael.dauria at gmail.com>
wrote:
> You should upgrade to the newest version: 0.3.20 as it allows multiple
> Set-Cookie header statements.
>
> For reference:http://mongrel.rubyforge.org/news.html
>
> To Install:
> $ gem install fastthread
> --source=http://mongrel.rubyforge.org/releases
> $ gem install mongrel
> --source=http://mongrel.rubyforge.org/releases
>
> Then you should be back on track :)
>
> .: Michael :.
>
The gems available in the mongrel.rubyforge.org/releases are ONLY
source, which requires a compiler.

The problem in mswin32 is that compilers compatible with ruby are only
VC6, which also requires you purchased it.

I''ll upadte the gem in my webserver tonight and put a mail on the list
(AFAIK, Zed already modified to allow multiple cookies).
>
> On 12/19/06, Ball, Donald A Jr (Library) <donald.ball at
nashville.gov> wrote:
> > > Sure. Actually, I have a problem to report already...
> > > sessions are not working when I start mongrel in this
> > > fashion. Is there somewhere i should be configuring session
> > > behavior that I''m not?
> > >
> > > To be more specific, the browser doesn''t report a
session_id
> > > cookie in its cookie list. The server-side code happily
> > > stores objects in the session, but the session is empty on
> > > the next request.
> > >
> > > For the record, both webrick and mongrel started via
> > > script/server have working sessions.
> >
> > The problem turns out to be fairly simple, but it''s beyond my
capability
> > to fix. The problem is that mongrel is only passing one and only one
> > cookie on to the user. If that''s _session_id, great, but if
it''s one of
> > the other cookies that I''m creating, the user''s
session is lost.
> >
> > To be clear, I''m using mongrel-0.3.18 from Luis. Note that I
was
> > incorrect when I said the problem didn''t occur when mongrel
is stared
> > with script\server. Mongrel has this problem regardless, while webrick
> > works fine.
> >
> > - donald
> > _______________________________________________
> > Mongrel-users mailing list
> > Mongrel-users at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/mongrel-users
> >
>
>
> _______________________________________________
> Mongrel-users mailing list
> Mongrel-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
>

-- 
Luis Lavena
Multimedia systems
-
Leaders are made, they are not born. They are made by hard effort,
which is the price which all of us must pay to achieve any goal that
is worthwhile.
Vince Lombardi

On Tue, 19 Dec 2006 13:37:14 -0600
"Joey Geiger" <jgeiger at gmail.com> wrote:
> Gives you 0.3.19
> $ gem install mongrel --source=http://mongrel.rubyforge.org/releases
> 
> Gives you 0.3.20
> $ gem install mongrel --source=http://mongrel.rubyforge.org/releases/
Man that is SO annoying.  Nobody can tell me why though and I think I messed up
the documentation too.  Thanks for reminding me Joey.

-- 
Zed A. Shaw, MUDCRAP-CE Master Black Belt Sifu
http://www.zedshaw.com/
http://www.awprofessional.com/title/0321483502 -- The Mongrel Book
http://mongrel.rubyforge.org/
http://www.lingr.com/room/3yXhqKbfPy8 -- Come get help.

On Tue, 19 Dec 2006 11:15:58 -0600
"Ball, Donald A Jr (Library)" <donald.ball at nashville.gov>
wrote:
> > Sure. Actually, I have a problem to report already... 
> > sessions are not working when I start mongrel in this 
> > fashion. Is there somewhere i should be configuring session 
> > behavior that I''m not?
> > 
> > To be more specific, the browser doesn''t report a session_id 
> > cookie in its cookie list. The server-side code happily 
> > stores objects in the session, but the session is empty on 
> > the next request.
> > 
> > For the record, both webrick and mongrel started via 
> > script/server have working sessions.
I''ll get you a win32 gem today.

-- 
Zed A. Shaw, MUDCRAP-CE Master Black Belt Sifu
http://www.zedshaw.com/
http://www.awprofessional.com/title/0321483502 -- The Mongrel Book
http://mongrel.rubyforge.org/
http://www.lingr.com/room/3yXhqKbfPy8 -- Come get help.

Luis

I am using your latest build of mongrel service in production with your
latest build of mongrel from your site too.  Everything is running really
well.

Do you have a build of fastthread for windows yet?  Will fastthread even be
available for win32?

Thanks for all the excellent work

Fraz

On 12/19/06, Luis Lavena <luislavena at gmail.com>
wrote:
>
> On 12/19/06, Michael D''Auria <michael.dauria at gmail.com>
wrote:
> > You should upgrade to the newest version: 0.3.20 as it allows multiple
> > Set-Cookie header statements.
> >
> > For reference:http://mongrel.rubyforge.org/news.html
> >
> > To Install:
> > $ gem install fastthread
> > --source=http://mongrel.rubyforge.org/releases
> > $ gem install mongrel
> > --source=http://mongrel.rubyforge.org/releases
> >
> > Then you should be back on track :)
> >
> > .: Michael :.
> >
>
> The gems available in the mongrel.rubyforge.org/releases are ONLY
> source, which requires a compiler.
>
> The problem in mswin32 is that compilers compatible with ruby are only
> VC6, which also requires you purchased it.
>
> I''ll upadte the gem in my webserver tonight and put a mail on the
list
> (AFAIK, Zed already modified to allow multiple cookies).
>
> >
> > On 12/19/06, Ball, Donald A Jr (Library) <donald.ball at
nashville.gov>
> wrote:
> > > > Sure. Actually, I have a problem to report already...
> > > > sessions are not working when I start mongrel in this
> > > > fashion. Is there somewhere i should be configuring session
> > > > behavior that I''m not?
> > > >
> > > > To be more specific, the browser doesn''t report a
session_id
> > > > cookie in its cookie list. The server-side code happily
> > > > stores objects in the session, but the session is empty on
> > > > the next request.
> > > >
> > > > For the record, both webrick and mongrel started via
> > > > script/server have working sessions.
> > >
> > > The problem turns out to be fairly simple, but it''s
beyond my
> capability
> > > to fix. The problem is that mongrel is only passing one and only
one
> > > cookie on to the user. If that''s _session_id, great, but
if it''s one
> of
> > > the other cookies that I''m creating, the user''s
session is lost.
> > >
> > > To be clear, I''m using mongrel-0.3.18 from Luis. Note
that I was
> > > incorrect when I said the problem didn''t occur when
mongrel is stared
> > > with script\server. Mongrel has this problem regardless, while
webrick
> > > works fine.
> > >
> > > - donald
> > > _______________________________________________
> > > Mongrel-users mailing list
> > > Mongrel-users at rubyforge.org
> > > http://rubyforge.org/mailman/listinfo/mongrel-users
> > >
> >
> >
> > _______________________________________________
> > Mongrel-users mailing list
> > Mongrel-users at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/mongrel-users
> >
> >
>
>
> --
> Luis Lavena
> Multimedia systems
> -
> Leaders are made, they are not born. They are made by hard effort,
> which is the price which all of us must pay to achieve any goal that
> is worthwhile.
> Vince Lombardi
> _______________________________________________
> Mongrel-users mailing list
> Mongrel-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/mongrel-users/attachments/20061219/377b327d/attachment-0001.html

> I''ll get you a win32 gem today.
You''re my hero.

- donald

On 12/19/06, frazer horn <frazer.list at gmail.com>
wrote:
> Luis
>
> I am using your latest build of mongrel service in production with your
> latest build of mongrel from your site too.  Everything is running really
> well.
>
I''m glad to heard, I was having  troubles getting rubygem recognize my
yaml definitions for a gem mirror, mostly due line terminations that
differ between platforms.

Until I solve that issue, or Zed made a "official" release for win32,
this will be the only way (manual download).
> Do you have a build of fastthread for windows yet?  Will fastthread even be
> available for win32?
>
I have builds from previous versions, latest svn code is broken for
win32 (a small fix we are trying with mental).

Anyway, doing some performance testing and process information
collecting for the past days and didn''t find any
"improvements" on
mongrel process using or not fastthread.

Guess the Mutex leaking problem is worse in *nix or isn''t noticeable
under win32.
(At least that will be a huge win for mswin32 :-)

Will talk with Zed and mental tonight and get some fixes for these
issues. Maybe we could have win32 fastthread *just in case*

Later,
> Thanks for all the excellent work
>
> Fraz
>
>
> On 12/19/06, Luis Lavena <luislavena at gmail.com> wrote:
> > On 12/19/06, Michael D''Auria <michael.dauria at gmail.com
> wrote:
> > > You should upgrade to the newest version: 0.3.20 as it allows
multiple
> > > Set-Cookie header statements.
> > >
> > > For reference:http://mongrel.rubyforge.org/news.html
> > >
> > > To Install:
> > > $ gem install fastthread
> > > --source=http://mongrel.rubyforge.org/releases
> > > $ gem install mongrel
> > > --source= http://mongrel.rubyforge.org/releases
> > >
> > > Then you should be back on track :)
> > >
> > > .: Michael :.
> > >
> >
> > The gems available in the mongrel.rubyforge.org/releases are ONLY
> > source, which requires a compiler.
> >
> > The problem in mswin32 is that compilers compatible with ruby are only
> > VC6, which also requires you purchased it.
> >
> > I''ll upadte the gem in my webserver tonight and put a mail on
the list
> > (AFAIK, Zed already modified to allow multiple cookies).
> >
> > >
> > > On 12/19/06, Ball, Donald A Jr (Library) <donald.ball at
nashville.gov>
> wrote:
> > > > > Sure. Actually, I have a problem to report already...
> > > > > sessions are not working when I start mongrel in this
> > > > > fashion. Is there somewhere i should be configuring
session
> > > > > behavior that I''m not?
> > > > >
> > > > > To be more specific, the browser doesn''t
report a session_id
> > > > > cookie in its cookie list. The server-side code happily
> > > > > stores objects in the session, but the session is empty
on
> > > > > the next request.
> > > > >
> > > > > For the record, both webrick and mongrel started via
> > > > > script/server have working sessions.
> > > >
> > > > The problem turns out to be fairly simple, but it''s
beyond my
> capability
> > > > to fix. The problem is that mongrel is only passing one and
only one
> > > > cookie on to the user. If that''s _session_id,
great, but if it''s one
> of
> > > > the other cookies that I''m creating, the
user''s session is lost.
> > > >
> > > > To be clear, I''m using mongrel-0.3.18 from Luis.
Note that I was
> > > > incorrect when I said the problem didn''t occur when
mongrel is stared
> > > > with script\server. Mongrel has this problem regardless,
while webrick
> > > > works fine.
> > > >
> > > > - donald
> > > > _______________________________________________
> > > > Mongrel-users mailing list
> > > > Mongrel-users at rubyforge.org
> > > > http://rubyforge.org/mailman/listinfo/mongrel-users
> > > >
> > >
> > >
> > > _______________________________________________
> > > Mongrel-users mailing list
> > > Mongrel-users at rubyforge.org
> > > http://rubyforge.org/mailman/listinfo/mongrel-users
> > >
> > >
> >
> >
> > --
> > Luis Lavena
> > Multimedia systems
> > -
> > Leaders are made, they are not born. They are made by hard effort,
> > which is the price which all of us must pay to achieve any goal that
> > is worthwhile.
> > Vince Lombardi
> > _______________________________________________
> > Mongrel-users mailing list
> > Mongrel-users at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/mongrel-users
> >
>
>
> _______________________________________________
> Mongrel-users mailing list
> Mongrel-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/mongrel-users
>
>

-- 
Luis Lavena
Multimedia systems
-
Leaders are made, they are not born. They are made by hard effort,
which is the price which all of us must pay to achieve any goal that
is worthwhile.
Vince Lombardi