|
We are starting JIRA with 1 GB of memory :
Java VM Memory Statistics There are 16300 issues in our database. If we try to export more than 2000 issues, JIRA is getting out of memory. We cannot upgrade our server memory at that time and I'm not sure it would be sufficient since the memory used depends on the number of exported issues. For your information, our database is growing a lot : 2000 issues are created every month.
We are anxious about the capability of JIRA to support such volumes when we see that some processes are running out of memory with a 1 GB tomcat instance. We have the same problem with 13000 issues. We have problem with filters too. After running few filters, memory spikes up and never gets garbage collected, eventually causing the instance to freeze. We are rebooting our instance twice a day. Can you please fix this in 3.4.2 as our production instance is affected.
Akshaya,
What JIRA version are you using? In 3.3, you should turn off issue caching. If that happens, just executing filters should not cause major spikes in the memory (as all issues are not added to memory) Cheers Mark C Sorry about the delay in resonding. Our issue was caused by a leak in IBM type 2 jdbc driver. We are using BEA Type 4 JDBC driver for db2 now. It's working fine.
Hi Akshay,
Thanks for the update. Great to hear that you have resolved the issue. If you have any further questions do not hesitate to contact us. Thanks, I just tried to export all issues into Excel from jira.atlassian.com. I got "502 Proxy Error" and jira instance seemed to be unavailable for some time.
I also have tried to download all bugs via RSS format, and got the same error. This seems critical! Please advise. Here's the exact response from your proxy: The proxy server received an invalid response from an upstream server. Reason: Error reading from remote server Apache/2.0.46 (Red Hat) Server at jira.atlassian.com Port 80 Igor,
Why do you want all 15k issues from our system in Excel? Or is this just to illustrate the problem? Cheers, Hi Jeff,
Of course it was a demonstration of the problem, I don't need your issues, I have a lot of my own As for my personal concern, I'm working on a desktop client for JIRA (similar to what we already have for Bugzilla, you can take a look at http://deskzilla.com Best regards, As of JIRA 3.7, the excel export exports all issues, and the memory usage is constant for the export.
Export away! |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Resolved
Critical
Excel Export memory usage is not constant
But don't you think it's possible that someone who has 15k issues in JIRA would want them exported for, say, graphical analysis?
How much memory are you starting JIRA with? After extended use this can be seen in Admin -> System -> System Info.
Cheers,
Jeff