./asadmin list-instances --verbose
Instance Name Host Name Admin Port Cluster Current State
---------------|-----------|------------|---------|---------------|
inst1 bear 14848 clust1 Not Running
inst2 bear 24848 clust1 Not Running
inst3 bear 34848 clust1 Not Running
However all the 3 instances are in fact running and as shown below the
ports are occupied and when I kill the java processes corresponding to
the instances these ports are free.
Command list-instances executed successfully.
[~/Software/glassfish-v3-latest/glassfishv3/glassfish/bin_at_bear]
% netstat -a | grep 14848
tcp6 0 0 [::]:14848 [::]:* LISTEN
[~/Software/glassfish-v3-latest/glassfishv3/glassfish/bin_at_bear]
% netstat -a | grep 24848
tcp6 0 0 [::]:24848 [::]:* LISTEN
[~/Software/glassfish-v3-latest/glassfishv3/glassfish/bin_at_bear]
% netstat -a | grep 34848
tcp6 0 0 [::]:34848 [::]:* LISTEN
- Rajiv
On 07/17/2010 01:03 PM, Byron Nevins wrote:
> Note to all: use the "--verbose" option for list-instances the moment
> you see anything unexpected.
>
>
> what does list-instances --verbose say?
>
>
> 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
>>
>