I've debugged this for a couple of hours and here's the best that I've come up with. Hopefully someone out there can help me connect the dots. With my limited knowledge of mBeans, I'm going to guess that ( at least on WLS ) that my application's mBeans run in a different context ( class loader ) than does my Web App. It seems that the two don't really talk after the Web App is deployed. When I deploy my Web App the first time and start it the mBean bean is initialized but subsequent deployments the mBean is not re-started. I stop the application and the mBean is still running. When the Web App is re-deployed or re-started it doesn't reset the mBean. Meaning... I can stop my web app but I can still call operations like set and get logger level or effective level. I have the ServletContextListener configured to prevent the memory leak as described in the documentation for a Memory Leak.. http://logback.qos.ch/manual/jmxConfig.html#leak and the contextName. But is there something I could add to the 'contextInitialized' method that would allow my Web Application to re-sync its self with the mBean and share the same LoggerFactory ? -- View this message in context: http://logback.10977.n7.nabble.com/JMX-registration-on-WebLogic-12-1-1-tp115... Sent from the Users mailing list archive at Nabble.com.