Hi RonRoskens
This issue is being investigated at the moment. Once we have a solution
to this issue, it will make its way to the commercial patch release as
it is occurring on a release product. As there is no specific GlassFish
v2.x.x public release planned, I am not sure if and how a fix will be
available in the open source user community for this issue. We
typically provide patches to commercial customers post public release.
If you are already a support customer, I would recommend you come
through our support channels so that you can be kept in the loop into
the patch train it will get into.
hth
Shreedhar
On 5/13/10 7:43 AM, glassfish_at_javadesktop.org wrote:
> Following up on my original message,
>
> All these threads seem to be tied to running multiple clusters in a domain, which seem to be tied to the node-agents now being Watchdog members of the GMS groups used by the clusters. (http://wiki.glassfish.java.net/Wiki.jsp?page=FaqShoalGMSAttributesInDomainXML for the differences between 2.1 and 2.1.1)
>
> Is there a way to limit which GMS groups a node-agent will join as Watchdog member?
>
> In our environment, node-agent agents are setup to run a single cluster instance, so being a Watchdog member for the other clusters is less than desirable, and has had a negative impact on our system performance.
> [Message sent by forum member 'ronroskens']
>
> http://forums.java.net/jive/thread.jspa?messageID=469697
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>