If you decide to have a go with it, we have some scripts we use to
handle the different instances that you might find interesting.
All in all, we have ONE directory where Resin is fully installed and
then we have various "instance directories", where each instance has a
resin.conf file in a conf directory, a temp directory for the instance's
resin.pd file, the applications etc.
That makes it easier to upgrade Resin and have different parameters per
instance, for example.
The script can start and stop resin normally, and backt to your
question, it can show you or "hard kill" all the processes of each
instance. Using show + top you can see which instance is giving you
John Steel escribió:
> Daniel Lopez wrote:
>> Not sure if that would help, but what we do is to have various resin
>> instances with the applications distributed among them, and then use
>> mod_proxy instead of mod_caucho to forward requests. It's easier then to
>> pinpoint the applications having problems, as you can see the process
>> eating all the memory and move web applications between hosts until you
>> find the "bad boy".
>> On the other hand, if you are having problems with mod_caucho, that would
>> simply side step the issue, so it won't help diagnosing it.
> Thanks for your help - I've been thinking of running multiple resin
> instances for a while, this might be the incentive to get on with it...
resin-interest mailing list