[JIRA 5.2.5] JIRA inaccessible unexpectedly

[atlassian member]

Hello,

I have a very urgent issue with JIRA, I need help ASAP
After merging two JIRA instances into one and moving to a virtual server, we started having issues with the final JIRA instance, it keeps crashing for a second then becomes accessible once again.

The characteritics of our server is:
OS: windows server 2008
RAM: 32 Go
JVM: 24 Go
CPU: 8

the characteristics of jira:
number of issues: 666188
number of projets:14
number of users:2160

Best regards,

[atlassian member]

Hello,

Everything went back to normal afterwards, it seems like the problem wasn't related to JIRA but to the network.

Thanks a lot for your help guys.

[Lars Olav Velle]

How much memory are java using?

Are you using a 64 bit version of java?

What version of java are you using? 

A memory dump of the java process will show you why JIRA is inresponsice. In linux this is done by: kill -QUIT PID Not sure the windows equivalent though. 

[atlassian member]

Java is using almost all of 24G that's allocated to the JVM

Yes

Java 1.7

We haven't accountered any other issue with JIRA so far, we're monitoring the instance.

[Nic Brough -Adaptavist-]

What do the logs say the error is when it crashes?

[atlassian member]

That's the weird part, we didn't find anything about this issue in the logs

[Nic Brough -Adaptavist-]

Hmm.  Do the logs just stop dead then?  You have normal lines in them and then they just end?

What are the last 10 lines in atlassian-jira.log and catalina.out ?

[atlassian member]

Yes, they stopped dead, nothing related to this issue is on the logs

[Nic Brough -Adaptavist-]

So what are the last lines in the logs?

If they really do just end with nothing, then it's the operating system killing the Tomcat container in the hardest way it can, not even a clean shutdown. 

That suggests poorly configured memory settings or a process that is killing off others.