dev@glassfish.java.net

Re: flooding by MNTG0201/MNTG0204 messages in server.log during QL tests (3.2 workspace)

From: Jennifer Chou <jennifer.chou_at_oracle.com>
Date: Wed, 15 Jun 2011 10:50:08 -0400

The MNTG0201 msg may be ok
The MNTG0204 msg means the monitoring AMX MBean are not getting
created. I ran ql on windows and see these messages also. And the
mbeans don't appear in jconsole.
Definitely a bug. Maybe it should be logged as SEVERE or WARNING.

On 6/14/2011 10:43 PM, Koper, Dies wrote:
> And the last issue for now:
>
> I see 404 messages with IDs MNTG0201 and MNTG0204 in my server.log after
> a QL run on the latest 3.2 workspace but they do not show up in Hudson's
> logs. Maybe a Windows only issue?
>
> [#|2011-06-15T11:19:51.123+1000|WARNING|glassfish3.2|javax.enterprise.sy
> stem.tools.monitor.org.glassfish.admin.monitor|_ThreadID=29;_ThreadName=
> Thread-1;|MNTG0201:Flashlight listener registration failed for listener
> class : com.sun.ejb.monitoring.stats.StatefulSessionBeanStatsProvider ,
> will retry later |#]
>
> [#|2011-06-15T11:19:51.170+1000|INFO|glassfish3.2|javax.enterprise.syste
> m.tools.monitor.org.glassfish.admin.monitor|_ThreadID=29;_ThreadName=Thr
> ead-1;|MNTG0204:com.sun.ejb.monitoring.stats.EjbMethodStatsProvider is
> not a ManagedObject and will not be registered with Gmbal to create an
> MBean|#]
>
> Especially the latter is not particularly informative to users like me.
> Can't it be logged with level FINE?
>
> Thanks,
> Dies
>
>