If you are using GlassFish 3.1, and there is no other cluster or
instances created, you maybe seeing this bug which is release noted and
fixed in 3.1.1.
http://docs.oracle.com/cd/E18930_01/html/821-2434/ggrvi.html#gkyys
If you want to confirm the status of the application, you can verify
that using CLI.
eg.
%asadmin list-applications --long
NAME TYPE STATUS
hello <web> enabled
Command list-applications executed successfully.
Hope this help.
Anissa.
On 1/3/12 12:25 PM, Cyril DANGERVILLE wrote:
> Hello,
> I am trying to disable an application via Glassfish 3.1's admin REST
> interface. I am using URL:
> http://localhost:4848/management/domain/applications/application/HelloWorld
> where HelloWorld is the name of my webapp (I got the URL via the
> "Child Resources" entry in the parent URL:
> http://localhost:4848/management/domain/applications/application/).
>
> When I changed the 'enabled' attribute to false/true, this has no
> effect on the application status: when I checked via the Admin Console
> GUI, the application status is unchanged. Vice versa, if I
> enable/disble the application via the admin console GUI, the "enabled"
> attribute is unchanged in the response from the REST interface.
>
> Is this a known issue or am I doing this wrong ?
>
> Thanks for your help.
>
> Regards,
> CD