I'm going to say that you'll need two services.  Isn't there a 1-1
mapping between services and processes?  As such, two processes, two
services?

Anyone else want to weigh-in?

I haven't used windows in sooo long!

John


On 2/22/19, Jerry Malcolm <techst...@malcolms.com> wrote:
> Thanks Johann,
>
> One physical installation would be cleaner.  But this would have to run
> as one Windows service for both instances, correct?  So I wouldn't be
> able to stop one instance separately?
>
> On 2/22/2019 2:18 AM, aon.913111...@aon.at wrote:
>> Brainstorming is not really required for this basic task.
>>
>> Approach 1: Make a copy of your Tomcat installation, alter bootstrap, http
>> and ajp connector ports, and use it as 2nd instance.
>> Approach 2, using one physical Tomcat installation: You can configure n
>> instances using CATALINA_BASE setup, each running separate JVM process.
>>
>> Johann
>>
>>
>> Von: Jerry Malcolm
>> Gesendet: Freitag, 22. Februar 2019 07:27
>> An: users@tomcat.apache.org
>> Betreff: Parallel Tomcat Instances On Same Server
>>
>> I need a bit of brainstorming.  I have a production Tomcat server that
>> hosts several web sites.  A couple of these websites are
>> high-availability sensitive.  Any downtime will cost the customer.  So
>> obviously I want to minimize downtime.  On the other hand, I am always
>> adding/removing/testing other virtual hosts which requires configuration
>> changes and periodic reboots of Tomcat.  I'm not at CPU capacity or
>> memory capacity on the box. So that is not the problem.  What I'd really
>> like to do is run both a production TC instance AND a 'development/test'
>> TC instance on the same box with the luxury of bouncing or taking the
>> dev TC down any time necessary without affecting the production TC.  I'm
>> using Apache httpd as the front end and routing via mod_jk to TC. The
>> separation of function on the two instances would be at domain level.
>> Domain A runs on production, Domain B runs on dev.  I am using the basic
>> mod_jk worker config currently.  If I change the dev instance to run a
>> different port, is it simply a matter of having worker1 and worker2 that
>> route to the different TC instances, and assign either worker1 or
>> worker2 to each virtual host in httpd?  I figure some people have done
>> this in the past. Is this the easiest way to do this?  Is there a better
>> way?
>>
>> Thx as always.
>>
>> Jerry
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to