I uploaded and installed JIRA on my Linux web server successfully.
After I open it using URL:8080, it works fine for avout one/two minutes * may differ) then suddenly stop working showing the message "
Then I stop jira, start JIRA again , still not working!
After some time , it return to work normally!
Where may be the problem?
Note: I'm connecting using Google chrome on windows 7, in a network guarded by TMG.
Note: The server is working fine at time of JIRA down
Thank you for your help
But I don't understand the JIRA log, I'm new to JIRA and just installing it for the first time, So Could you plz help me more ?
This is the URL for the JIRA log file :
That file seems to show that you're killing JIRA without warning while it is running. That would neatly explain why you're getting a 500 error - it's stopped. Are you running a development copy? Also, could you check another log (sorry!) - catalina.out in the log directory of the installation. I notice that you're using HSQL as the database
Ok. There's a reason buried in the catalina.out. It's stopping dead because it runs out of memory # There is insufficient memory for the Java Runtime Environment to continue. # Native memory allocation (mmap) failed to map 110100480 bytes for committing reserved memory. # An error report file with more information is saved as: Unfortunately, there's no way of knowing what that is. You may genuinely have too little resource for the volume of data. But you may have an addon leaking memory. I don't actually know exactly how HSQL works, but it is an in-memory database, and if that is eating up JVM resource, JIRA may be left with too little to run properly. There are two things I would do here: 1. Stop using HSQL. You need to do that anyway - it is only suitable for short-term test use, it's not usable for a system where you can't afford to lose the whole system. It's great for dev and test, running something quickly for a couple of hours, but it can, and will, fail catastrophically at some point, and you could lose everything. So not for production! 2. You could try increasing the heap memory - I'd recommend increasing it gradually in most cases (add 256Mb at a time, don't just give it a huge volume from nowhere - it's not a simple "more memory helps", you can actually cause more problems by just increasing it in one huge step). But your settings are below 1Gb at the moment, and I've never seen any issue with increasing memory up to 1Gb.
From the attached log itself there isn't anything pointing to the reason of the instance being brought down. Could you confirm how you start the application? Also, do you have any scripts whatsoever running in this machine that could be stopping services / messing with ports?
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