Jira crashed with GC Overhead error and Atlassian is pointing to the "Project Pivot Gadget" in the PlugIn
Hi Andriy
We have faced problem with the PlugIn once more and initial analysis by Atlassian suggested that there could be a problem with the TimeSheet PlugIn one of the modules - "Project Pivot Gadget".
They suggested to provide the heapdump.hprof file to you for analysis but it is quite big - 900Mb gzipped and I am not sure how I can pass it to you.
Also I would like to give you access to the issue on Atlassian Support so could you please let me know you ID there if so?
Regards, Areg
Comments (16)
-
-
Account Deleted Hi Andriy
I have shared the file via the Google Drive - https://drive.google.com/file/d/0BzgDxH-iXHygU3hkc1ZHanNiSWs/edit?usp=sharing
Please let me know if you need any more details.
Regards, Areg
-
- changed status to resolved
resolve issue
#452: paginate search to prevent underlying lucene crash→ <<cset f3753fb5c6f1>>
-
Hi Areg,
I've downloaded file, so you might want to remove it, though I did not investigate it, reading JSP-178483 was enough - Dave made great job identifying problematic stack traces, so I went ahead and improved corresponding piece of code in Timesheet Plugin. You may want to share details with him, commit #f3753fb5c6f1.
Fix will be available in next 2.7.3, which I would like to make in week of 9th of December, but if customer needs it sooner please let me know (in JSP-178483 should be enough).
Note, this does not mean that problematic place in the plugin was definitively the cause.
Thank you.
-
Account Deleted Hi Andriy
Thank you very much for your quick response.
I would like to check if there is an easy solution for the
#410too or you need to rebuild the JAR file each time?Is there a possibility to allow to extract the configuration file from JAR file and place it to the file system so there will be no needs to rebuild the plugin file each time or repack it.
In conclusion I would like to have some pre-release so I can test it on QA instance before installing on production.
Regards, Areg
-
Hi Areg,
I could not find solution for
#410beside updating JIRA to 6.0.1, so, yes, I have to rebuild plugin jar every time. Unfortunately it's not possible to keep atlassian-plugin.xml separetly.Regarding pre-release, please see 2.7.3 in Downloads tab. Note, actual 2.7.3 may have more changes later.
Thank you.
-
- changed version to 2.7
-
Account Deleted -
-
Hi Areg,
Let me check, is it working well? Can you see any improvement?
Thank you.
-
Version 2.7.3 with the fix is released.
-
Account Deleted Hi Andriy
I am on trainig all this week and was not able to test anything. I have installed plugin on Dev system and initially it looks Ok.
I see that there is a new generated jar file with patch and I will try it too.
Will keep you informed.
Many thanks, Areg
-
Account Deleted Hi Andriy
Sorry for bothering you again but could you please build the patched version for the latest version?
Seems we faced issues in Jira again and I am going to push management to allow me to install the latest version on Production system as the previous release was working fine on Dev system.
Regards, Areg
-
Hi Areg,
Patch in comment# 2013-11-28 is in main stream, so in every version since 2.7.3. Patch for JRA-32510 workaround should not relate to crash, but anyway, please see patched update 2.7.5
Thank you.
-
Account Deleted Hi Andriy
Thanks for quick response and new file.
The problem is that we faced the problem again and Atlassian support again stated the "Project Pivot" - https://support.atlassian.com/browse/JSP-181854 (https://support.atlassian.com/browse/JSP-181854?focusedCommentId=4202258&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-4202258).
Regards, Areg
-
- removed version
Removing version: 2.7 (automated comment)
- Log in to comment
Hi Areg,
You may upload it to any cloud storage, e.g. http://www.justcloud.com offers 1 GB for free, but I'm not sure if there is file size limit, or http://disk.yandex.com/ it offers even more. Also I believe Atlassian has aws s3.
My ID is azhdanov@gmail.com.
Thank you.