A'ight, if I do this then the proper directory is created:
asadmin import-sync-bundle --file ../domains/domain1/config/mybundle --node na1 instance1
I'm therefore unclear on the node concept. I only ever created/used/imagined one node in the v2 cluster before the upgrade, so why is this needed here? Is this a bug or the expected way that instances need to be recreated?
Still can't start the cluster though (at least not yet). I get these in the DAS log file and then it just waits (I expect it will timeout in another few minutes):
[#|2010-09-14T16:19:49.763-0400|INFO|glassfish3.1|javax.enterprise.system.tools.admin.com.sun.enterprise.v3.admin.cluster|_ThreadID=19;_ThreadName=Thread-2;|Starting cluster cluster1|#]
[#|2010-09-14T16:19:49.784-0400|INFO|glassfish3.1|javax.enterprise.system.tools.admin.com.sun.enterprise.v3.admin.cluster|_ThreadID=19;_ThreadName=Thread-2;|Executing start-instance on 2 instances using a thread pool of size 2: na1-instance1 na1-instance2 |#]
[#|2010-09-14T16:19:49.786-0400|INFO|glassfish3.1|javax.enterprise.system.tools.admin.com.sun.enterprise.v3.admin.cluster|_ThreadID=19;_ThreadName=Thread-2;|start-instance instance1|#]
[#|2010-09-14T16:19:49.806-0400|INFO|glassfish3.1|javax.enterprise.system.tools.admin.com.sun.enterprise.v3.admin.cluster|_ThreadID=19;_ThreadName=Thread-2;|start-instance instance2|#]
[#|2010-09-14T16:19:53.215-0400|INFO|glassfish3.1|null|_ThreadID=19;_ThreadName=Thread-2;|Cannot read logging.properties file. |#]
[#|2010-09-14T16:19:53.473-0400|INFO|glassfish3.1|null|_ThreadID=19;_ThreadName=Thread-2;|Cannot read logging.properties file. |#]
Instance1 log is just:
[params]
Sep 14, 2010 4:19:53 PM com.sun.enterprise.admin.launcher.GFLauncherLogger info
INFO: Successfully launched in 54 msec.
hostname%
Thanks,
Bobby