Hi, Irfan
>
> The bug does seem to be pretty close to what we are seeing in Sailfin.
>
> By the way (BTW) which takes priority in such a case. The property
> configured at the cluster level or the one at the instance level.
>
I think the cluster level should take precedence. However, from what you
observed earlier, this is not consistent in the current implementation.
- Hong
>
> Hong Zhang wrote:
>
>> Hi, Irfan
>> I believe the deploy/enable/disable commands in v2 are only
>> applicable to the whole cluster and not to individual cluster
>> instances. The enable attribute of individual cluster instances
>> should probably not be exposed in that case, but as they are exposed,
>> they should have consistent values with the cluster. I assume you
>> were using admin console when you see the inconsistency of setting
>> the enable attributes? The admin console should have the same
>> behavior as the admin cli in this case.
>> There is actually a similar issue here:
>> https://glassfish.dev.java.net/issues/show_bug.cgi?id=4096
>>
>> Thanks,
>>
>> - Hong
>>
>>
>> Irfan Ahmed wrote:
>>
>>> I mean enabled attribute and not availability-enabled. Sorry for the
>>> typo.
>>>
>>> Irfan Ahmed wrote:
>>>
>>>> Hi All,
>>>>
>>>> I have a query regarding the availability enabled field for a web
>>>> application in a cluster environment.
>>>>
>>>> Setup :
>>>>
>>>> Config : default-cluster-config
>>>> Cluster : default-cluster (config-> default-cluster-config)
>>>> Instance : instance-1 on default-cluster
>>>>
>>>> What is the relation between the application-ref enabled attribute
>>>> in an instance and the application-ref enabled in a cluster
>>>> element. The scenario is as follows :
>>>>
>>>> I deploy a web app in default-cluster with availability enabled as
>>>> true. This sets the enabled in application-ref under the instance
>>>> and the cluster as true for the application. When I select the web
>>>> application in the web-apps table and click Disable, this sets the
>>>> enabled attribute to false in application-ref under cluster
>>>> definition in domain.xml. The attribute enabled under instance is
>>>> true. Also the application does not serve any requests.
>>>>
>>>> However the same scenario does not work for a deployed SIP
>>>> application. When a deployed SIP application is disabled, the GUI
>>>> sets the enabled attribute for application-ref to false in the
>>>> clusters element. However the SIP application still serves
>>>> requests. It is only when the enabled is set to false under the
>>>> instance then only SIP application is disabled.
>>>>
>>>> However on the CLI, if one issues the command asadmin disable
>>>> --target default-cluster hello , both the attributes for the
>>>> application-ref under clusters as well as instance are set to false.
>>>>
>>>> For more details on the bug please refer the URL
>>>> https://sailfin.dev.java.net/issues/show_bug.cgi?id=429
>>>>
>>>> Rgds
>>>> Irfan
>>>>
>>>> --
>>>> Irfan Ahmed
>>>> 9180-66927726, Sun Microsystems Inc., Bangalore, India.
>>>
>>>
>>> --
>>> Irfan Ahmed
>>> 9180-66927726, Sun Microsystems Inc., Bangalore, India.
>>
>>
>
> --
> Irfan Ahmed
> 9180-66927726, Sun Microsystems Inc., Bangalore, India.