Peter,
Could you please check if similar MBeans are there in the JMX
com.sun.appserv domain? These are the "delegate" MBeans to which AMX
delegates. AMX reflects what the underlying system is doing.
I see two possibilities:
1) the com.sun.appserv MBeans exist and so naturally the AMX ones do
also. Then the bug lies deeper in the system.
2) the com.sun.appserv MBeans do not exist, but the AMX ones do. That
would indicate an AMX bug.
If you can just dump all MBeans (ObjectNames) in all domains I can
take a look.
Lloyd
..............................................
Lloyd Chambers
lloyd.chambers_at_sun.com
GlassFish team, LSARC member
On Jan 3, 2009, at 3:07 PM, Peter Williams wrote:
> I discovered that if I have monitoring enabled (LOW on everything),
> undeploying and then deploy an EAR *with a new name* creates new
> monitors with the new name, but the old monitor mbeans ("amx:X-
> ApplicationMonitor") stay in existence until the server is restarted.
>
> This EAR contains web services and the old web service mbeans
> (specifically "amx:WebServiceEndpoint") also stay alive, though they
> can be detected due to their container element being invalid.
>
> Is this a bug or a feature?
>
> To me, it seems like a memory leak, as the entries seem to be
> obsolete (accessing them causes all kinds of trouble) but I was
> unable to get them to be GC'd.
>
> This is with GlassFish V21 B60e (also B60c), cluster profile (though
> no cluster or standalone instances were configured -- just "server").
>
> -Peter
>