admin@glassfish.java.net

Behavior of creating an instance with a cluster's config

From: Tom Mueller <tom.mueller_at_oracle.com>
Date: Mon, 01 Nov 2010 10:26:44 -0500

  Bill,
I'm looking at fixing issue 12853:
https://glassfish.dev.java.net/issues/show_bug.cgi?id=12853

This is about what happens with the following:

create-instance --config c1-config i1

where "c1" is an existing cluster with an application deployed to it and
c1-config is the cluster's config.

Back in August, I was ready to close this issue, but then based on your
recommendation, I left it open with this statement:

    application-ref's should be created for an instance that refers to a
    cluster's config, whether the instance is part of the config or not.
    Maybe another way of looking at this is that using --target c1 and
    --config c1-config are the same thing, i.e., the instance becomes
    part of the cluster.

After considering this some more, creating the application-refs is just
the first part of the issue. Even if the application-refs are created,
the instance isn't necessarily part of the cluster. My question is, should:

    create-instance --config c1-config i1

and

    create-instance --cluster c1 i1

have identical behavior in all respects?

For example, after doing this, a start-cluster c1 would start i1, doing
a deploy to target c1 would deploy the application to i1, etc.

Thanks.
Tom