verified it is fixed now.
On 7/26/2010 1:05 PM, Jennifer Chou wrote:
> Hi Kshitiz,
>
> Yes this is a bug we saw late last week. It should be fixed now. I
> will verify on today's build.
>
> Thanks,
> Jennifer
>
> On 7/26/2010 11:53 AM, Kshitiz Saxena wrote:
>> Hi,
>>
>> I am trying to create standalone instance using command provided. Please
>> /ejp-152x-233:/space/kshitiz/GFv3.1/glassfishv3 # *asadmin
>> create-instance --node ejp-152x-231-node --cluster cluster1 instance3*
>>
>> Command create-instance executed successfully.
>> ejp-152x-233:/space/kshitiz/GFv3.1/glassfishv3 # *asadmin
>> create-instance --node ejp-152x-231-node st-instance2*
>> remote failure: Exception while adding the new configuration
>> org.jvnet.hk2.config.TransactionFailure: There is no node-agent-ref
>> specified for the instance st-instance2. :
>> org.jvnet.hk2.config.TransactionFailure: There is no node-agent-ref
>> specified for the instance st-instance2.
>>
>> Command create-instance failed.
>> ejp-152x-233:/space/kshitiz/GFv3.1/glassfishv3 # *asadmin
>> create-local-instance --node ejp-152x-231-node st-instance2*
>> Using DAS host localhost and port 4848 from existing das.properties
>> for node
>> ejp-152x-231-node. To use a different DAS, create a new node using
>> create-node-ssh or
>> create-node-config. Then 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.
>> Attempting to rendezvous with DAS on host localhost port 4848
>> Uptime: 2 hours, 24 minutes, 19 seconds
>>
>> The instance has rendezvoused with the DAS and will be using host
>> localhost port 4848 for future communication.
>> remote failure: Exception while adding the new configuration
>> org.jvnet.hk2.config.TransactionFailure: There is no node-agent-ref
>> specified for the instance st-instance2. :
>> org.jvnet.hk2.config.TransactionFailure: There is no node-agent-ref
>> specified for the instance st-instance2.
>>
>> Command create-local-instance failed./
>>
>> Standalone instance creation is failing, however instance is created
>> successfully within a cluster.
>>
>> Thanks,
>> Kshitiz
>