There are certain concepts here :
1. When a management rule is configured on the domain administration
server (DAS), after the server is started, whenever there is a change in
the observed attribute, a notification is triggered and is handled. No
actions are taken when the server shuts down as the rule is not
configured as a lifecycle rule.
This is a monitor type of event that checks for a string value (which
will be done only after the server start) and performs some action if it
differs from the value specified.
2. When the management rule is configured on the cluster, again please
note that this is a monitor type of event and not a lifecycle event and
hence after an instance is started, a difference in the string value is
handled (as it would be apparent from the action taken).
Could you please check (after cluster startup) if you get any
notifications in the server.log while you change the value of
"stateValue" from jconsole?
Ideally, with the change : "Add server=* at the end of the object-name
of the mbeans instead of the earlier suggested server=server. " you
should not see the error message. But during an instance stop, you would
not see this message as this is not a lifecycle event.
HTH,
Shalini.
glassfish_at_javadesktop.org wrote:
> The target is a cluster.
> [Message sent by forum member 'lazania' ]
>
> http://forums.java.net/jive/thread.jspa?messageID=376606
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>