On 4/15/2010 12:35 AM, Bill Shannon wrote:
> Byron Nevins wrote on 4/14/10 10:55 PM:
>
>> Will 3.1 turn off all normal admin command processing for instances?
>>
> I don't think so. asadmin commands sent to the DAS will be cascaded
> to the instances for execution there, using the same admin command
> mechanism.
>
Command replication happens depending on the RuntimeType attribute set
in the @Cluster annotation in the class that implements AdminCommand. If
RuntimeType is DAS only, the command replication on instances does not
happen. If it is INSTANCE only, then the command is not executed on DAS
but only on instances. If it DAS and INSTANCE, them the command is
executed on DAS and, if successful, then it is replicated on instances.
To avoid changing the 3.0 code, if the AdminCommand implementation for a
command does NOT contain @Cluster annotation at all, we assume the
default to be @Cluster(RuntimeType.DAS, RuntimeType.INSTANCE) - meaning
all the 3.0 'remote command' will be replicated on all applicable instances.
>> There are a LOT of commands that assume the server is "server".
>>
> As a default for "target"? If so, yes, there's a lot that needs to be
> fixed to support a different target. Perhaps we can do it in a generic
> way that reduces the amount of code needed for each command?
>
If I remember correctly, 'server' is a reserved keyword, right ? Then,
when the decision is being taken whether to replicate command or not,
(and if so, where all to replicate), we can stop replication if the only
target specified is the string 'server'. Will that work ?
Vijay
> If they're using it for something else, what?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>
>