Yes. The exception being when the behavior implemented in
takes precedence. But if you have a server
that isn’t in reload required and then what you described happens, it’s a bug.
On Nov 7, 2016, at 9:28 AM, Ondrej Kotek <okotek(a)redhat.com>
wrote:
Thanks a lot, Brian. I understand the referenced documentation as following:
In case an attribute has "restart-required" => "resource-services"
descriptor, when I change/write the attribute using
"allow-resource-service-restart" => true request header, then the handler for
the operation (write attribute) HAVE TO go ahead and restart the runtime service. In case
the handler do not restart the service, it is a bug.
Do I understand it well please?
----- Original Message -----
From: "Brian Stansberry" <brian.stansberry(a)redhat.com>
To: "Ondrej Kotek" <okotek(a)redhat.com>
Cc: "Kabir Khan" <kabir.khan(a)jboss.com>, wildfly-dev(a)lists.jboss.org
Sent: Monday, November 7, 2016 3:43:22 PM
Subject: Re: [wildfly-dev] allow-resource-service-restart=true
See “restart-required” in the “Description of an Operation” section of
https://docs.jboss.org/author/display/WFLY/Description+of+the+Management+...
> On Nov 7, 2016, at 1:20 AM, Ondrej Kotek <okotek(a)redhat.com> wrote:
>
> Is there any way how to recognize whether an operation handles the
allow-service-restart header please? (Other way than trying it.)
>
> Ondra
>
>
> ----- Original Message -----
> From: "Kabir Khan" <kabir.khan(a)jboss.com>
> To: "Martin Stefanko" <mstefank(a)redhat.com>
> Cc: wildfly-dev(a)lists.jboss.org
> Sent: Friday, November 4, 2016 4:38:27 PM
> Subject: Re: [wildfly-dev] allow-resource-service-restart=true
>
> Not all operations handle the allow-service-restart header
>> On 4 Nov 2016, at 15:09, Martin Stefanko <mstefank(a)redhat.com> wrote:
>>
>>
>> Hi,
>>
>> I am looking for help with the usage of the allow-resource-service-restart
header. For the following examples each attribute is a boolean with
"restart-required" set to "no-services".
>>
>> When I run
>>
>>
/subsystem=jmx:write-attribute(name=non-core-mbean-sensitivity,value=true){allow-resource-service-restart=true}
>>
>> it works as expected, but
>>
>>
/subsystem=undertow:write-attribute(name=statistics-enabled,value=true){allow-resource-service-restart=true}
>>
>> for instance, puts the server into the reload-required state.
>>
>> This is happening on several other places so I want to ask if it is a desired
behavior.
>>
>>
>> Martin Stefanko
>>
>> Associate Software Engineer
>> JBoss Sustaining Engineering Team
>> Red Hat Czech s.r.o.
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/wildfly-dev
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
Brian Stansberry
Manager, Senior Principal Software Engineer
JBoss by Red Hat
--
Brian Stansberry
Manager, Senior Principal Software Engineer
JBoss by Red Hat