From today early in the morning we are experiencing problems accesing the Planning Board of one of our Agile GreenHopper projects. The other projects work; with slowness but they work. We've tried re-indexing, optimizing indexes, we've look at our database and it's running fine. The Worklog Cache Limit option seems to be fine, since our projects only hosts about 800 issues. We've rebooted jira service, even the server but it's still not working. We've also tried running the integrity checker utility and fixing the problems.
Our Jira v4.3.3 (v4.3.3#617-r149616 Installation is running on a Linux ubuntu 11.10. The database is running on MSSQL SERVER 2008. The GreenHopper version is 5.6.8 (Build: #9b559fa899d0).
Custom Fields 96
Java VM Memory Statistics
Total Memory 1820 MB
Free Memory 1214 MB
Used Memory 606 MB
Total PermGen Memory 512 MB
Free PermGen Memory 361 MB
Used PermGen Memory 150 MB
67 % Free (Total: 1820 MB)
PermGen Memory Graph
71 % Free (Total: 512 MB)
Non-Heap Memory Graph (includes PermGen)
69 % Free (Total: 560 MB)
I have run and participated in hundreds of planning meetings over the years, and have seen the gambit of good to bad to terrible. With a little bit of prep, you can run really effective planning meet...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs