The instances are running. That isn't the problem. Even when I do a
start-local-instance I have the same problem
./asadmin start-local-instance inst1
Waiting for the server to start .......
Successfully started the instance: inst1
instancelocation:
/home/rajiv/Software/glassfish-v3-latest/glassfishv3/glassfish/nodeagents/bear/inst1
Log File:
/home/rajiv/Software/glassfish-v3-latest/glassfishv3/glassfish/nodeagents/bear/inst1/logs/server.log
Admin Port: 14848
Command start-local-instance executed successfully.
[~/Software/glassfish-v3-latest/glassfishv3/glassfish/bin_at_bear]
% ./asadmin start-local-instance inst2
Waiting for the server to start .......
Successfully started the instance: inst2
instancelocation:
/home/rajiv/Software/glassfish-v3-latest/glassfishv3/glassfish/nodeagents/bear/inst2
Log File:
/home/rajiv/Software/glassfish-v3-latest/glassfishv3/glassfish/nodeagents/bear/inst2/logs/server.log
Admin Port: 24848
Command start-local-instance executed successfully.
[~/Software/glassfish-v3-latest/glassfishv3/glassfish/bin_at_bear]
% ./asadmin start-local-instance inst3
Waiting for the server to start .......
Successfully started the instance: inst3
instancelocation:
/home/rajiv/Software/glassfish-v3-latest/glassfishv3/glassfish/nodeagents/bear/inst3
Log File:
/home/rajiv/Software/glassfish-v3-latest/glassfishv3/glassfish/nodeagents/bear/inst3/logs/server.log
Admin Port: 34848
Command start-local-instance executed successfully.
[~/Software/glassfish-v3-latest/glassfishv3/glassfish/bin_at_bear]
% ./asadmin start-cluster clust1
Command start-cluster executed successfully.
[~/Software/glassfish-v3-latest/glassfishv3/glassfish/bin_at_bear]
% ./asadmin list-instances
inst1 not running
inst2 not running
inst3 not running
Command list-instances executed successfully.
and svn stat shows that I have only changes in teh web module and that
too most are just adding logging. The pom changes is to
add the HA module to the build - but again that should not affect
starting the instance AFAIK.
svn stat
M web/pom.xml
M web/gf-web-connector
M
web/web-ha/src/main/java/org/glassfish/web/ha/strategy/builder/ReplicatedWebMethodSessionStrategyBuilder.java
M
web/web-ha/src/main/java/org/glassfish/web/ha/session/management/ReplicationWebEventPersistentManager.java
M web/war-util
M
web/web-glue/src/main/java/com/sun/enterprise/web/PersistenceStrategyBuilderFactory.java
M
web/web-glue/src/main/java/com/sun/enterprise/web/ServerConfigLookup.java
M web/webtier-all
M web/webtier-all/pom.xml
M web/jsf-connector
? packager/external/build.log
- Rajiv
On 07/17/2010 01:43 PM, Byron Nevins wrote:
> the workaround for a similar (same?) issue [0] is to use
> start-local-instance for each instance instead of start-cluster
>
> [0] https://glassfish.dev.java.net/issues/show_bug.cgi?id=12706
>
>
> On 7/17/2010 12:19 PM, Rajiv Mordani wrote:
>> All,
>> I did an update of the workspace and built the latest workspace.
>> When I execute create-cluster followed by create-instance to create 3
>> instances that are tied to the cluster that I just created the
>> start-cluster commands returns that it failed to start the 3
>> instances that are part of the cluster but the 3 instances are infact
>> running. When I do a asadmin list-instances that also returns that
>> the instances are not running. Is anyone else seeing this behaviour?
>> I am creating all the instances on the same host as the DAS btw.
>>
>> - Rajiv
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>