Significant Performance issue with JIRA 4.4.x on AIX 6.1

[angel]

We are trying to upgrade our customer running on AIX 6.1 JDK 6_64JRE 1.6.0 IBM AIX build pap6460sr8fp1-20100624_01 (SR8 FP1) and we are experiencing a huge performance issue. To give you an example during startup we get a 20 minutes delay before we can logon to JIRA:

{noformat}

2011-10-27 14:21:09,991 main INFO atlassian.jira.startup.JiraStartupLogger

********************************************************************************

JIRA 4.4.3 build: 663 started. You can now access JIRA through your web browser.

********************************************************************************

2011-10-27 14:21:15,145 Modification Check:thread-1 INFO atlassian.jira.startup.JiraStartupLogger

___ Modifications ___________________________

Modified Files : jira-application.properties

Removed Files : None

2011-10-27 14:44:07,485 main INFO atlassian.jira.scheduler.JiraSchedulerLauncher Starting the JIRA Scheduler....

2011-10-27 14:44:07,919 main INFO atlassian.jira.scheduler.JiraSchedulerLauncher JIRA Scheduler started.

{noformat}

Any ideas what to look for?

Cheers,

A.

[Norman Abramovitz]

Did you turn on logging to see what is going on?

http://confluence.atlassian.com/display/JIRA044/Logging+and+Profiling

[angel]

First time I've tried that I didn't see anything of interest. So I'm going to run a thread dump to see if I can get anything from there.

[Nic Brough -Adaptavist-]

Do you have the subversion plugin installed? That can add a looooong hang to startup, without bothering to tell you why.

[angel]

I'm going to give it a try, thanks Nic.

[angel]

It seems we run into this problem. http://confluence.atlassian.com/display/JIRAKB/Poor+Dashboard+Performance+due+to+IBM+JDK+1.6

Our thread dumps indicate the same behavior around ResourceBundle processing.

3XMTHREADINFO      "main" J9VMThread:0x0000000112622D00, j9thread_t:0x00000001101507A0, java/lang/Thread:0x0700000000002330, state:CW, prio=5
3XMTHREADINFO1            (native thread ID:0x3030159, native priority:0x5, native policy:UNKNOWN)
3XMTHREADINFO3           Java callstack:
4XESTACKTRACE                at java/util/Hashtable.put(Hashtable.java:769(Compiled Code))
4XESTACKTRACE                at java/util/Properties.selectProperties(Properties.java:529(Compiled Code))
4XESTACKTRACE                at java/util/Properties.propertyNames(Properties.java(Compiled Code))
4XESTACKTRACE                at java/util/PropertyResourceBundle.getLocalKeys(PropertyResourceBundle.java(Compiled Code))
4XESTACKTRACE                at java/util/PropertyResourceBundle.access$000(PropertyResourceBundle.java(Compiled Code))
4XESTACKTRACE                at java/util/PropertyResourceBundle$1.<init>(PropertyResourceBundle.java(Compiled Code))
4XESTACKTRACE                at java/util/PropertyResourceBundle.getKeys(PropertyResourceBundle.java(Compiled Code))
4XESTACKTRACE                at java/util/ResourceBundle.keySet(ResourceBundle.java(Compiled Code))
4XESTACKTRACE                at java/util/ResourceBundle.containsKey(ResourceBundle.java:604(Compiled Code))

We'll try an upgrade to the latest JVM Service Refresh and see how it goes.