Just today I had the following issue: JIRA started working slow until at a moment it didn't respond at all. Having had this before I tried to stop the "Atlassian JIRA" service. This usually takes about 15 minutes in my environment. I usually check the existence of the "tomcat7w.exe" process in the list of active processes and after a 25 minutes wait I decided to restart the entire server as I wasn't sure that the process was actually doing something (server activity was at 0%-2%).
After the server restart some people mentioned me that issues, they had closed at least 15 days ago had returned to the "in progress" status and the issue activity log doesn't show any inconsistent activity with the issue's status.
Here's my question: how does JIRA handle crashes and database transactions? Is it possible that transactions are held in a temporary db for such a long period of time? And that they can get lost if JIRA abruptly crashes?
Is there any way I can trace back what might have happened?
Any guidance is welcome.
I've restored the database before the crash and have discovered (only mentioning one issue here, but goes for various):
Isn't this strange? Shouldn't both date/time values be the same? Or are there changes to a ticket that aren't registered in the [changeitem] table which make the "UPDATED" field?
Since JIRA seems to handle SQL updates through transactions I'm thinking that some of them might have been stored in memory (or tempdb) and when rebooting the server the SQL service didn't have the time to write all these transactions to disk.
Nevertheless: I'm not a SQL guru and it seems very strange that this would have happened.
Any other suggestion you might think of?
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot