-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
6.4.3, 6.7.12
-
6.04
-
3
-
Severity 3 - Minor
-
1
-
Action:
Take a large JIRA (1.1M issues) with hundreds of Agile boards
Upgrade JIRA from 5.2.4 to 6.2.7 using a database, not XML.
Do the upgrade with no add-ons
Then install JIRA Agile 6.4.3 by uploading the jar into the UPM, not via m.a.c
Observed:
The install in UPM hangs about 80% of the way through until it completes 70 minutes later.
See the atlassian-greenhopper.log snippet below.
There are no messages after 17:30 about what is happening
There are no errors in the atlassian-jira.log since there are no errors.
Expected:
If an operation is going to take 70 minutes to complete on a large instance of JIRA some message should indicate this in the logfile.
This issue was created as a bug because I think that the JIRA Agile installation process has missing log messages.
2014-08-12 17:29:58,367 ThreadPoolAsyncTaskExecutor::Thread 21 INFO mdoar 1049x5637x1 1pdp3w2 172.21.10 2.217 /rest/plugins/1.0/ [greenhopper.plugin.sampledata.JiraImportersPluginInstallerImpl] Checking if j ira-importers-plugin is present and at version 4.4 or higher 2014-08-12 17:29:58,370 ThreadPoolAsyncTaskExecutor::Thread 21 INFO mdoar 1049x5637x1 1pdp3w2 172.21.10 2.217 /rest/plugins/1.0/ [greenhopper.plugin.sampledata.JiraImportersPluginInstallerImpl] jira-importer s-plugin already at 6.1.7. 2014-08-12 17:30:00,621 UpmAsynchronousTaskManager:thread-3 INFO mdoar 1049x5637x1 1pdp3w2 172.21.102.2 17 /rest/plugins/1.0/ [greenhopper.service.logging.LogSupport] ********************************************************************************* Atlassian GreenHopper v6.4.3 #8b64c9843d011df8 built 2014-07-22T07:03:48.436Z - plugin started. Get Ag ile! ********************************************************************************* 2014-08-12 18:38:50,258 UpmAsynchronousTaskManager:thread-3 INFO mdoar 1049x5637x1 1pdp3w2 172.21.102.2 17 /rest/plugins/1.0/ [greenhopper.service.logging.LogSupport] Managed Issue Types Epic id=41 name=Epic Story id=42 name=Story Managed Custom Fields Epic Colour id=customfield_13796 name=Epic Colour type=com.pyxis.greenhopper.jira:gh-epic-color Epic Link id=customfield_13793 name=Epic Link type=com.pyxis.greenhopper.jira:gh-epic-link Epic Name id=customfield_13794 name=Epic Name type=com.pyxis.greenhopper.jira:gh-epic-label Epic Status id=customfield_13795 name=Epic Status type=com.pyxis.greenhopper.jira:gh-epic-status Default Global Rank id=customfield_15790 name=Rank type=com.pyxis.greenhopper.jira:gh-lexo-rank Sprint id=customfield_13792 name=Sprint type=com.pyxis.greenhopper.jira:gh-sprint Story Points id=customfield_10343 name=Story Points type=com.atlassian.jira.plugin.system.customfieldtypes:float Managed Issue Link Types Epic Link Issue Link Type id=10160 name=Epic-Story Link
- relates to
-
JRASERVER-61383 JIRA Software can become unresponsive on upgrade or install when there are many custom fields due to restoring and locking all fields
- Closed
-
JSWSERVER-9991 JIRA Agile hangs on installation
- Closed
-
JSB-106 Loading...
-
RUN-635 Loading...
-
SIN-357 Loading...
- mentioned in
-
Page Loading...