RE: Exception handling Container property change
Hello. This exception stack trace is very distracting to the folks who watch for problems in the log. Could you pl tell me if writing my own Custom VirtualWebappClassLoader requires me to intrument the classloader woth a specific MBean? Thanks, /U /U wrote: Thanks! It looks like this is related to the long conversation we had about using VirtualWebappClassLoader a couple of months ago. I needed to use VirtualWebappLoader and hence chose to extend WebappLoader (CustomWebappClassLoader) and install the class in ${CATALINA_BASE}/lib. This classloader is used with multiple contexts but in loading a specific context alone, Tomcat yields this error: Caused by: java.lang.Exception: ManagedBean is not found with CustomWebappClassLoader at org.apache.catalina.mbeans.MBeanUtils.createMBean(MBeanUtils.java:397) ... 46 more Is my custom WebappLoader supposed to provide an MBean? If I choose not to, would it be a fatal error (as in one which would abort the context)? Regards, /U -- Original message -- From: Caldarale, Charles R [EMAIL PROTECTED] From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Subject: Exception handling Container property change Everytime I load my app context, the log yields the following MBean exception. Mar 3, 2008 9:12:30 PM org.apache.catalina.mbeans.ServerLifecycleListener propertyChange SEVERE: Exception handling Container property change javax.management.MBeanException at org.apache.catalina.mbeans.MBeanUtils.createMBean(MBeanUtils.java:398) Look further in the logs - there should be a nested exception related to the one above with this text: ManagedBean is not found with mname The actual mname will tell you what MBean can't be created. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/%22Exception-handling-Container-property-change%22-tp15820562p17590598.html Sent from the Tomcat - User mailing list archive at Nabble.com. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Exception handling Container property change
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Subject: Exception handling Container property change Everytime I load my app context, the log yields the following MBean exception. Mar 3, 2008 9:12:30 PM org.apache.catalina.mbeans.ServerLifecycleListener propertyChange SEVERE: Exception handling Container property change javax.management.MBeanException at org.apache.catalina.mbeans.MBeanUtils.createMBean(MBeanUtils.java:398) Look further in the logs - there should be a nested exception related to the one above with this text: ManagedBean is not found with mname The actual mname will tell you what MBean can't be created. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Exception handling Container property change
Thanks! It looks like this is related to the long conversation we had about using VirtualWebappClassLoader a couple of months ago. I needed to use VirtualWebappLoader and hence chose to extend WebappLoader (CustomWebappClassLoader) and install the class in ${CATALINA_BASE}/lib. This classloader is used with multiple contexts but in loading a specific context alone, Tomcat yields this error: Caused by: java.lang.Exception: ManagedBean is not found with CustomWebappClassLoader at org.apache.catalina.mbeans.MBeanUtils.createMBean(MBeanUtils.java:397) ... 46 more Is my custom WebappLoader supposed to provide an MBean? If I choose not to, would it be a fatal error (as in one which would abort the context)? Regards, /U -- Original message -- From: Caldarale, Charles R [EMAIL PROTECTED] From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Subject: Exception handling Container property change Everytime I load my app context, the log yields the following MBean exception. Mar 3, 2008 9:12:30 PM org.apache.catalina.mbeans.ServerLifecycleListener propertyChange SEVERE: Exception handling Container property change javax.management.MBeanException at org.apache.catalina.mbeans.MBeanUtils.createMBean(MBeanUtils.java:398) Look further in the logs - there should be a nested exception related to the one above with this text: ManagedBean is not found with mname The actual mname will tell you what MBean can't be created. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]