My *guess* is that you have a typo in the instance name. See here for more:
https://glassfish.dev.java.net/issues/show_bug.cgi?id=14719
I've tried again this morning and everything worked, so either "in2" isn't really the name you mean or something new is going on.
Cheers,
Bobby
On Nov 19, 2010, at 2:55 PM, Cheng Fang wrote:
> I tried cluster upgrade again, and this time it failed at step 6, when manually creating the second instance. It complains about an existing jdbc/__CallFlowPool. Any idea?
>
> /Users/cf126330/v3/glassfish/bin > ./asadmin create-local-instance --node na1 --cluster cl1 in2
> Using DAS host localhost and port 4848 from existing das.properties for node
> na1. 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.
> Rendezvoused with DAS on localhost:4848.
> org.glassfish.api.admin.CommandException: remote failure: Exception while adding the new configuration A ResourceRef with the same key "jdbc/__CallFlowPool" already exists in Server null : org.jvnet.hk2.config.TransactionFailure: A ResourceRef with the same key "jdbc/__CallFlowPool" already exists in Server null
> A ResourceRef with the same key "jdbc/__CallFlowPool" already exists in Server null
> Command create-local-instance failed.
>
> Cluster upgrade with 1 instance works fine, though.
>
> -cheng
> [...]