I suppose that seems fine, but...
How about if it were a command that talked to the DAS and asked it to listen,
then sent data, and got the results from the DAS? Would that make it easier
to use if it required the DAS to be running?
Bobby Bissett wrote on 08/11/2010 09:30 AM:
> Just to close on this....
>
> We've written a tool in the shoal-gms jar that tests that multicast is
> available on the nodes where instances will be running. I can integrate
> it into GF either with a script in the bin directory or as an asadmin
> command. Any objections to it being an asadmin command? "asadmin
> validate-multicast"?
>
> Before you answer, here's how it works: you run it on one machine and
> leave it running, then run it again on another node/machine/etc (or even
> another instance on the same machine). It sends out messages and listens
> for messages and tells you from what hosts it has received a message. It
> runs for 20 seconds by default, but there's an option to change that. So
> you generally run it here, run it there, look for the output, and ctrl-c
> out of it (or just wait).
>
> That still seem like a good fit for asadmin?
>
> Thanks,
> Bobby
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>