The rationale behind separate conf files is that the different
applications could potentially, but not necessarily, run on different
I found the key thing was that in order to have separate instances on
the same machine you must have different watchdog ports. E.g.
Server-default is a child of "cluster", so Scott's way will work like
this as well (of course.)
Scott Ferguson wrote:
> On Feb 2, 2007, at 12:39 AM, Daniel López wrote:
>> Jose Quinteiro escribió:
>> As Jose, I would recommend having different instances for development
>> and deployment. Even though Resin does a good job on separating
>> and detecting changes and restarting just the appropriate web app. You
>> will still affect your deployment applications with the common
>> restarts during development.
>> And as Jose said, you don't need two copies of the whole Resin
>> just two config files so you don't have to worry about
>> maintaing/upgrading two full instances.
> FYI, in Resin 3.1 you could just use one config file and have two
> separate <cluster> blocks. The -server foo will select which
> <cluster> will be active for that JVM.
> -- Scott
>> In fact, we use more than one instance even in deployment, as that
>> allows us to handle upgrades/problems more gracefully as applications
>> affected by what happens to others is minimised.
>>> The way I've accomplished this is by having two different
>>> instances of
>>> Resin, with different conf files. It's easy to do with 3.0.x, a
>>> harder with 3.1.0.
>>> Vinny wrote:
>>>> I am trying figure out a way to do a kind of virtual hosting
>>>> based on
>>>> port number.
>>>> I want my production apps running under port 443
>>>> docroot : (/web/production/webapps)
>>>> and my dev apps running under 8080.
>>>> docroot : (/web/dev/webapps)
>>>> both production and dev apps will have the same context
>>>> names (like ROOT.war for example) I just need resin to
>>>> on port number basically.
>>>> I was thinking perhaps I could nest <host/> under <http/> but it
>>>> I will have to make a completely seperate <server/> block?
>>>> Is that really the case?
>>>> Thanks in advance
>>>> Ghetto Java: http://www.ghettojava.com <http://www.ghettojava.com>
>> resin-interest mailing list
> resin-interest mailing list
resin-interest mailing list