Continuing with my investigation I found that glassfish creates two
classloader instances for a web application as I mention above. The first one
named as 'shareableTemp' is destroyed after the PREPARE phase. Before
destroying it clears the all the classed loaded by that classloader.
The above error appears because the logback jmx bean which was loaded by this
'shareableTemp' classloader is registered with the MBeanServer and this is
not unregistered when the classloader is destroyed. Hence the error.
Is there some custom code or a workaround or a fix needed for unregistering
the jmx beans which got registered with the 'shareableTemp' classloader?
--
[Message sent by forum member 'table1']
View Post: http://forums.java.net/node/795429