2 Replies Latest reply: Apr 7, 2014 2:21 PM by Puneeth-Oracle RSS

    Performance issues after upgrading Java 7 from update 7 to update 25

    User440927
      Hi All,

      Recently we updated our Java 7 update 7 to update 25, on SunOS 5.10 Generic_144488-17 sun4v sparc SUNW,Sun-Blade-T6340 machine. Right after the update we got serious performance issues from our application that deployed on WebLogic 11g.

      During thread dumps analytic we discovered that the following code cause to thread dump that halts the application.
      This code is executed every 30 seconds:

      ThreadMXBean threadBean = ManagementFactory.getThreadMXBean();
      ThreadInfo[] allThreadsList = threadBean.getThreadInfo(threadBean.getAllThreadIds(), isObjectMonitorUsageSupported, isSynchronizerUsageSupported);

      Thread Dump:
       
              at sun.management.ThreadImpl.dumpThreads0(Native Method)
              at sun.management.ThreadImpl.getThreadInfo(ThreadImpl.java:440)

              at sun.reflect.GeneratedMethodAccessor620.invoke(Unknown Source)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
              at java.lang.reflect.Method.invoke(Method.java:606)
              at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:75)
              at sun.reflect.GeneratedMethodAccessor265.invoke(Unknown Source)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
              at java.lang.reflect.Method.invoke(Method.java:606)
              at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:279)
              at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112)
              at com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46)
              at com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237)
              at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138)
              at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252)
              at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
              at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
              at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:449)
              at java.security.AccessController.doPrivileged(Native Method)
              at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:447)
              at weblogic.management.mbeanservers.internal.JMXContextInterceptor.invoke(JMXContextInterceptor.java:263)
              at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase$16.run(WLSMBeanServerInterceptorBase.java:449)
              at java.security.AccessController.doPrivileged(Native Method)
              at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:447)
              at weblogic.management.mbeanservers.internal.SecurityInterceptor.invoke(SecurityInterceptor.java:444)
              at weblogic.management.jmx.mbeanserver.WLSMBeanServer.invoke(WLSMBeanServer.java:323)
              at javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:292)


      Anybody knows why this happens only after upgrade to update 25?

      Thanks All.