[ https://jira.jboss.org/jira/browse/JBWEB-150?page=com.atlassian.jira.plug... ] Mike Millson updated JBWEB-150: ------------------------------- Summary: Provide an identifier to relate web application to classloader in a heap dump (was: Facilitate identifying web app classloader in heap dump) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBWEB-150?page=com.atlassian.jira.plug... ] Mike Millson reassigned JBWEB-150: ---------------------------------- Assignee: (was: Mike Millson) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBWEB-150?page=com.atlassian.jira.plug... ] Mike Millson commented on JBWEB-150: ------------------------------------ Test case: 1) Create war with <display-name>Testbox</display-name> in web application deployment descriptor (WEB-INF/web.xml). 2) Deploy war to JBoss 3) Manually create a heap dump (e.g. jmap -heap:format=b <jboss_pid) on JDK 1.5) 4) Parse the heap dump with the Eclipse Memory Analyzer Tool (MAT). 5) List all org.jboss.web.tomcat.service.WebAppLoader objects and inspect the displayName property. One should be populated with "Testbox". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBWEB-150?page=com.atlassian.jira.plug... ] Mike Millson updated JBWEB-150: ------------------------------- Description: When troubleshooting OutOfMemoryError issues in situations where the JVM is running multiple applications, it would be very helpful for troubleshooting to be able to relate a web application to the web app classloader. It is proposed to sets the display-name of the war as a property on the web app classloader so that it can be easily accessed when viewing a heap dump (e.g. with a tool such as the Eclipse Memory Analyzer Tool). For example, given the following web application deployment descriptor (web.xml): <web-app> <display-name>Testbox</display-name> </web-app> Inspection of the corresponding org.jboss.web.tomcat.service.WebAppLoader and org.jboss.web.tomcat.service.WebAppClassLoader objects in the heap dump will show "Testbox" in the displayName field. was: When troubleshooting OutOfMemoryError issues in situations where the JVM is running multiple applications, it would be very helpful for troubleshooting to be able to relate a web application to the web app classloader. It is proposed to sets the display-name of the war as a property on the web app classloader so that it can be easily accessed when viewing a heap dump (e.g. with a tool such as the Eclipse Memory Analyzer Tool). For example, given the following web application deployment descriptor (web.xml): <web-app> <display-name>Testbox</display-name> </web-app> Inspection of the corresponding org.jboss.web.tomcat.service.WebAppLoader object in the heap dump will show "Testbox" in the WebAppLoader displayName field. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBWEB-150?page=com.atlassian.jira.plug... ] Mike Millson updated JBWEB-150: ------------------------------- Comment: was deleted -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBWEB-150?page=com.atlassian.jira.plug... ] Mike Millson updated JBWEB-150: ------------------------------- Attachment: JBWEB-150-patch.txt Proposed patch for EAP 4.x CP branch:. https://svn.jboss.org/repos/jbossweb/branches/JBOSSWEB_2_0_0_GA_CP/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBWEB-150?page=com.atlassian.jira.plug... ] Mike Millson resolved JBWEB-150. -------------------------------- Resolution: Rejected The WebappLoader has a reference to an ObjectName that has a _canonicalName String that can be used to identify web app classloaders. For example, to see all _canonicalName values: SELECT toString(oname._canonicalName) FROM org.jboss.web.tomcat.service.WebAppLoader Then a specific WebAppLoader could be selected as follows: SELECT * FROM org.jboss.web.tomcat.service.WebAppLoader WHERE toString(oname._canonicalName) = "jboss.web:host=localhost,path=/jmx-console,type=Loader" Or the WebAppClassLoader selected as follows: SELECT OBJECTS classLoader FROM org.jboss.web.tomcat.service.WebAppLoader WHERE toString(oname._canonicalName) = "jboss.web:host=localhost,path=/jmx-console,type=Loader" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira