GMS will handle updating the state of stand-alone instances? Perfectly?
On 7/7/2010 2:44 PM, Vijay Ramachandran wrote:
> On 7/7/10 2:27 PM, Byron Nevins wrote:
>> How are you guaranteeing that the cached state in InstanceStateImpl
>> reflects reality? E.g. what if I "kill -9" an instance -- how does
>> the cached state change to not-running?
>
> I will depend on GMS for that.
>
> Vijay
>
>>
>>
>> On 7/7/2010 10:02 AM, Vijay Ramachandran wrote:
>>> For those CLI/module owners who want a way to get the state of an
>>> instance at any time :
>>>
>>> A new service, InstanceState, has been introduced. You can use this
>>> by doing the following in your code :
>>>
>>> @Inject InstanceState state;
>>>
>>> As of now, this service interacts with the command replication
>>> framework and, hence, the state of an instance changes from RUNNING
>>> to RESTART_REQUIRED only. Soon this service will interact with GMS
>>> subsystem and every other instance state change will be reflected.
>>>
>>> You may want to consider using this instead doing other forms of
>>> pinging an instance (like doing uptime / version / locations
>>> command) to see if an instance is alive.
>>>
>>> Let me know if you have any feedback / comments / issues with this.
>>>
>>> Vijay
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>
--
Byron Nevins - Oracle Corporation
Home: 650-359-1290
Cell: 650-784-4123
Sierra: 209-295-2188