----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
Can you explain this in more detail? Are you talking about zones?
How are you using it now to break up development environments?
---8<---
Sure. We are using zones, however, depending on your needs, its not
required.
Load balancing can be used to set up multiple instances of jserv. Each
instance of jserv has its own properties file used to configure each
instance. Each jserv instance has its own jvm, which is the used to execute
servlets. Each jserv instance then becomes a seperate execution
environment.
If you are running a site with high performance requirements, then the idea
is you set up multiple machines, each running a couple of jserv instances.
The apache mod_serv then balances between each of these, ensuring that each
new request is randomly distributed between jserv instances and each
subsequent request from the same source is redirected back to the same jserv
instance the first request was sent to, preserving session state. Note that
is it is not required to set up each jserv instance on a seperate machine.
We have one sun machine running 26 instances of jserv to provide a number of
different services to a number of different applications. We are in the
planning stages at the moment of possibly using 10 linux pcs to run a number
of jserv instances in order to acheive scalibility for the app and to
control cost.
In the case outlined above, multiple jserv instances are defined for a
single zone. However, using zones, you can also set up groups of jserv
instances and tie them to a single zone. So for intance you could set up
jserv instances 1-4 for zone1, 5-14 to zone2 and 15-16 to zone3 etc.,
depending on your particular application needs. Requests to each zone will
only be balanced between jserv instances configured for that zone.
Partitioning your execution environment for development purposes involves
assigning a zone to each developer. Each zone is then configured with a
single jserv instance, creating a partitioned execution environment.
Assuming each jserv is configured with a developers individual class path
;-), this then provides a development environment where changes made by one
developer do not have an effect on other developers on a project.
Using appropriate RCS like CVS its then possible to develop without fear
that the code you are executing is not in a stage of flux.
An excellent explanation (we read it often) was available at
java.apache.org, but now I can't find. A link was listed in the
faq-o-matic. :-(
Please don't hesitate to query more.
Brian Claus
Application Development Specialist
Corelan Communications
.
> Partitioning Execution Environments. The fact that we were able to
> partition execution environments was invaluable. This would have been
> particularly useful during development, if we'd realized this was possible
> (in all future development, we are making use of this). As it is,
> partitioning the execution environments has allowed us to redistribute the
> site for additional clients on the same box without fear of bugs caused by
> overlapping state. It has made it very easy for us to "white label" it.
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
