-
Bug
-
Resolution: Low Engagement
-
Low (View bug fix roadmap)
-
None
-
6.4.3, 6.7.12
-
6.04
-
2
-
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
-
-
- Closed
-
-
-
- Closed
-
-
![[JIRA Server (Bulldog)]](/images/icons/generic_link_16.png "[JIRA Server (Bulldog)]")
JSB-106
You do not have permission to view this issue
-
RUN-635
You do not have permission to view this issue
-
SIN-357
You do not have permission to view this issue
- mentioned in
-
Page Loading...
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-11040] JIRA Agile install is not well logged (and took 78 minutes!)
We encountered this issue too and waited 15 minutes...
- JIRA 6.4.14 (upgraded from 6.1)
- JIRA Agile 6.7.12 (upgraded from 6.6.80)
- Issues: 300,000
- Agile boards: 20
I have attached a thread dump taken about 10 minutes into the install. If I read it correctly, the "UpmAsynchronousTaskManager:thread-3" thread has executed some SQL statement and is waiting.
Hi,
At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.
This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.
Please note the comments on this thread are not being monitored.
You can read more about our bug fix policy here and how we prioritize bugs.
To learn more about our recent investments in Jira Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.
Kind regards,
Jira Data Center