2 Replies Latest reply on May 28, 2009 11:32 AM by jorge.mota

    Memory Profiler does not work

    jorge.mota
    jorge.mota May 27, 2009 12:16 PM

      Hello all,

      I cannot get the Memory Profiler to work.

      I can generate the log files in the JVMTIClass MBean.
      But when I try to analyse the generated logs in the jboss-profiler application it keep loading forever and does not return anything.

      Can anyone help me?

      Regards,

      • 2517 Views
      • Tags:
        • 1. Re: Memory Profiler does not work
          clebert.suconic
          clebert.suconic May 27, 2009 12:27 PM (in response to jorge.mota)

          The memory profiler needs some work :-(


          I'm preparing something to put back on 2.0, that will analyze directly on the memory without having to create intermediate files.


          JVMTIInterface still useful for analyzing the memory directly.. and that's what I'll be porting on the new branch.

            • Actions
          • 2. Re: Memory Profiler does not work
            jorge.mota
            jorge.mota May 28, 2009 11:32 AM (in response to jorge.mota)

            Hi,

            thank you for your response.

            I tried the Class Loader Analysis (Current JVM only) link and got the following error:

            org.apache.jasper.JasperException: Exception in JSP: /classLeakage/clean.jsp:6

            3: <%
            4: session.removeAttribute("list");
            5: JVMTIInterface jvmti = new JVMTIInterface();
            6: jvmti.releaseTags();
            7: %>


            Stacktrace:
            org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:506)
            org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:377)
            org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
            org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
            javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
            org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)

            root cause

            javax.servlet.ServletException: releaseTags
            org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:843)
            org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:776)
            org.apache.jsp.classLeakage.clean_jsp._jspService(clean_jsp.java:113)
            org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
            javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
            org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:334)
            org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
            org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
            javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
            org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)

            root cause

            java.lang.UnsatisfiedLinkError: releaseTags
            org.jboss.profiler.jvmti.JVMTIInterface.releaseTags(Native Method)
            org.apache.jsp.classLeakage.clean_jsp._jspService(clean_jsp.java:106)
            org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
            javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
            org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:334)
            org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
            org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
            javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
            org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)


            An other question: Is the 2.0 beta version more stable for this purpose (Memory Profiling)?

            Regards

              • Actions