Poor Dashboard Performance due to IBM JDK 1.6

Symptoms

  • The dashboard renders slowly
  • Startup time is poor

Thread dumps contain threads like:

      "TP-Processor2" TID:0x0000000115176200, j9thread_t:0x00000001113A2A40, state:CW, prio=5
            (native thread ID:0x26A01B, native priority:0x5, native policy:UNKNOWN)
          at java/util/Hashtable.containsKey(Bytecode PC:13(Compiled Code))
          at java/util/PropertyResourceBundle$1.findNext(Bytecode PC:42(Compiled Code))
          at java/util/PropertyResourceBundle$1.hasMoreElements(Bytecode PC:42(Compiled Code))
          at java/util/ResourceBundle.keySet(Bytecode PC:42(Compiled Code))
          at java/util/ResourceBundle.containsKey(Bytecode PC:14(Compiled Code))
          at sun/reflect/GeneratedMethodAccessor69.invoke(Bytecode PC:44(Compiled Code))
          at sun/reflect/DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:39(Compiled Code))
          at java/lang/reflect/Method.invoke(Method.java:590(Compiled Code))
          at com/atlassian/jira/web/bean/I18nBean$Java6ResourceBundleAccessor.getUnescapedText(I18nBean.java:540(Compiled Code))
          at com/atlassian/jira/web/bean/I18nBean._getUnescapedText(I18nBean.java:345(Compiled Code))

Cause

The thread is performing some operations, because the stack traces are not identical, but the ResourceBundle.keySet call has not finished. java.util.ResourceBundle and java.util.Hashtable classes are provided by the JVM, and at least ResourceBundle has changed its API in 1.6.

Resolution

Switch to Sun's JDK.

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport