All of ours are. We don't use clusters that span machines (yet), and we
don't (or hardly) use the DAS to run applications on.
So all production as well as tests run on a cluster with its one or
multiple instances on the same machine.
I'm planning to confirm what issues could arise on GFv2.x (because I
don't think there are any) with having the instances point to the DAS's
application folder directly instead of each having its own copy. If we
can do that in GFv3.1 by default, that should reduce sychronization time
during deployment and start-up for this case. And required disk space.
On 11/03/2010 03:38, Tim Quinn wrote:
> Does anyone have a sense for how many GlassFish environments are
> "cluster development" or "cluster testing" environments in which all of
> these activities - adding instances, deploying and redeploying apps -
> are more frequent than in truly production settings? And to the extent
> that we want to offer a compelling (that is, fast!) development
> experience with clusters as well, we'll want to keep those environments
> in mind.
<snip>