JIRA shuts down abruptly

Hi All

I am on jira 5.0 (upgraded recently)

I am observing that jira is going down abruptly (happened twice in four days)

I have windows 2003 server and installed jira standalone (as a service) connecting to MYSQL

4GB RAM allocated to host with 1GB exclusively given to jira. No other applications are running on it.

Unfortunately in the logs i am not getting any significant help. however , the last line of the error message on logs are

2013-08-08 04:08:14,587 http-443-57 ERROR mmanimaran 248x153363x1 zbrf82 27.61.161.126 /charts [jira.charts.jfreechart.DisplayChartServlet] Error checking path, returning 404 (filename='jfreechart-onetime-7951004111531513670.png').

ug 8, 2013 4:08:14 AM org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet DisplayChart threw exception
java.lang.IllegalStateException
at org.apache.catalina.connector.ResponseFacade.sendError(ResponseFacade.java:421)
at javax.servlet.http.HttpServletResponseWrapper.sendError(HttpServletResponseWrapper.java:118)
at javax.servlet.http.HttpServletResponseWrapper.sendError(HttpServletResponseWrapper.java:118)
at javax.servlet.http.HttpServletResponseWrapper.sendError(HttpServletResponseWrapper.java:118)
at javax.servlet.http.HttpServletResponseWrapper.sendError(HttpServletResponseWrapper.java:118)
at javax.servlet.http.HttpServletResponseWrapper.sendError(HttpServletResponseWrapper.java:118)
at com.atlassian.oauth.serviceprovider.internal.servlet.OAuthFilter$OAuthWWWAuthenticateAddingResponse.sendError(OAuthFilter.java:180)

2 answers

1 accepted

Accepted Answer
0 votes

The problem was because i was on 32 bit server and therefore the system was not able to reserve enough memory and was abruptly shutting down with out of memory logs.after upgrading to 64 bit, it was fine

rahul

How frequently is it happening (e.g. 8hrs appart?)? What Java version? Have you tweaked your logging up to try to capture more? You can do so by altering the log4j.properties file. Whe you say goes down, is the process actually dead and no longer running, or is it still running but Jira is broken?

Have you made sure that your connection to MySQL is set to query before connection? MySQL kills connections after a period of time. That can kill your server.

Hi Caldwell

It goes down anytime (no patterns recognised). The last time it went down was just after an unsucessful xml backup and it threw GC limit exceeded. So, as a fix i have now disabled the xml backup.

Atlassian also suggested me to clear all plugins folders and work folders and reindex and restart.

Apart from that i was advised to increase the connection pool from 25 to 50 in dbconfig.xml

Fingers crossed, these should fix my issues

Rahul

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 18, 2018 in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

21,505 views 2 7
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you