Hi,
Yes, I am currently on v2ur2.
Any idea which components I might increase the logging for?
Sadly, this problem appears to be sporadic. Some times when I stop and
start the node-agent controlled server-instance, the mbean cascades with the
DAS no problem...other times, it doesn't cascade. The last time this
happened (ie, today), when I attempted to connect with the DAS JMXServer
(via JConsole) to see what was happening, it blocked indefinitely and I had
to restart the DAS to get everything synched up.
I'll provide specific details an example custom mbean when I've done a bit
more digging.
Thanks,
John
On Thu, Nov 20, 2008 at 3:34 PM, <glassfish_at_javadesktop.org> wrote:
> I guess you are working with GlassFish v2.
>
> I have deployed a custom mBean to a non-das-instance using --target option
> and I am able to see the custom mBean cascaded on to DAS (Domain Admin
> Server). I couldn't see the custom mBean when I stopped the
> non-das-instance. Restarted non-das-instance and again I am able to see the
> cascaded mBean in DAS.
>
> I have looked at the code and it is the same code/filters which are used,
> no matter how the cascading is initiated.
>
> If it is still an issue for you, pl. provide specific details which help in
> reproducing the issue.
>
> - sreeni
> [Message sent by forum member 'msreddy' (msreddy)]
>
> http://forums.java.net/jive/thread.jspa?messageID=317945
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
>