> 1) Try out mongrel_cluster as a way to easily manage a bunch of
> mongrels.  With more than one Mongrel running you'll be able to do this
> no problems.  Well, see below.

I will look into this, thanks.

> 2) This guy walks into the doctor's office and says, "Doc, it hurts when
> I do this."  Doctor says, "Well, don't do that."  Seriously, if you have
> a situation where you're doing SOAP calls back to the same process I
> think you've got to rethink your SOAP usage.  It's horribly inefficient
> and leads to all sorts of other problems.  If you're just doing this
> during development then run two mongrel servers.  But in production this
> is a sign that you've got the design wrong.

I simplified the use case for my posting but the real use-case is somewhat
different. The SOAP method in question tries to synchronize with a certain
RSS/Atom feed. This feed can be specified by the caller. However there is
also another SOAP call that is used for an RSS feed. It's possible to
specify this feed when you call the first method. I can't detect this
particual case and do it locally because the feed in question is handled
by a PHP script which does the SOAP calls. Come to think of it, it even
sounds more complex now which doesn't seem to help my case. ;)

But I hoped one Mongrel instance could handle multiple Rails requests in
parallel out of the box. Unfortunately it doesn't, but that's no problem I
will work around it.

Thanks for the help all.

Regards,

Peter