admin@glassfish.java.net

Re: can we reference default-config when creating instance ?

From: Anissa Lam <anissa.lam_at_oracle.com>
Date: Wed, 15 Dec 2010 16:54:03 -0800

DONE. http://java.net/jira/browse/GLASSFISH-15218

Anissa.
On 12/15/10 4:27 PM, Jennifer Chou wrote:
> Can you file a bug and assign to me?
>
> On 12/15/2010 7:16 PM, Anissa Lam wrote:
>>
>> On 12/15/10 4:08 PM, Byron Nevins wrote:
>>> Those are special configs. You can't use a cluster config either.
>>
>> ok, thats what i though. That means there is a bug in the system then.
>> Because I can successfully use 'default-config' to create the
>> instance and start it.
>>
>> *~ 230) asadmin create-instance --config default-config --node
>> localhost-domain1 TEST*
>> Using DAS host localhost and port 4848 from existing das.properties
>> for node
>> localhost-domain1. To use a different DAS, create a new node using
>> create-node-ssh or
>> create-node-config. Create the instance with the new node and correct
>> host and port:
>> asadmin --host das_host --port das_port create-local-instance --node
>> node_name instance_name.
>> Command _create-instance-filesystem executed successfully.
>> Port Assignments for server instance TEST:
>> JMX_SYSTEM_CONNECTOR_PORT=28689
>> JMS_PROVIDER_PORT=27679
>> HTTP_LISTENER_PORT=28083
>> ASADMIN_LISTENER_PORT=24851
>> JAVA_DEBUGGER_PORT=29012
>> IIOP_SSL_LISTENER_PORT=23823
>> IIOP_LISTENER_PORT=23703
>> OSGI_SHELL_TELNET_PORT=26669
>> HTTP_SSL_LISTENER_PORT=28184
>> IIOP_SSL_MUTUALAUTH_PORT=23923
>> The instance, TEST, was created on host localhost
>> Command create-instance executed successfully.
>> *~ 231) asadmin start-instance TEST*
>> Waiting for TEST to start ................
>> Successfully started the instance: TEST
>> instance Location:
>> /Users/anilam/Awork/V3/v3/dist-gf/glassfish/nodes/localhost-domain1/TEST
>> Log File:
>> /Users/anilam/Awork/V3/v3/dist-gf/glassfish/nodes/localhost-domain1/TEST/logs/server.log
>> Admin Port: 24851
>> Command start-local-instance executed successfully.
>> The instance, TEST, was started on host localhost
>> Command start-instance executed successfully.
>> *~ 232) asadmin list-instances*
>> TEST running
>> Command list-instances executed successfully.
>>
>> thanks
>> Anissa.
>>
>>
>>>
>>> You can; however, make a snapshot copy of the config "copy-config"
>>> and use that.
>>>
>>>
>>> On 12/15/2010 3:57 PM, Anissa Lam wrote:
>>>>
>>>> I can create the instance successfully and start it.
>>>> %asadmin create-instance --node localhost-domain1 --config
>>>> default-config TEST
>>>>
>>>> But in the documentation, it says:
>>>> --config
>>>> Specifies the named configuration that the instance
>>>> references. The configuration must exist and must not be
>>>> named default-config or server-config.
>>>>
>>>> At first, i thought maybe the doc is wrong, but then, I also
>>>> remember seeing email that said default-config and server-config
>>>> cannot be referenced.
>>>> Can someone tell me what is the expected behavior ?
>>>>
>>>> thanks
>>>> Anissa.
>