what happens during startup step: "Running JIRA startup checks."?

Britt Fitch
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 18, 2011

I have multiple instances of jira 4.3 that are running in tomcat and connecting to mysql.

Starting on saturday when I try to bounce tomcat, the applications get as far as logging " Running JIRA startup checks. " and then they hang indefinitely.

for example:

user.dir                                      : ${catalina.base}/temp
     user.home                                     : /www/jira.cbmi.med.harvard.edu/support/home
     user.language                                 : en
     user.name                                     : jiracbmi
     user.timezone                                 : America/New_York

2011-09-19 13:09:22,897 main INFO      [atlassian.jira.startup.JiraStartupLogger] Running JIRA startup checks.

Looking at old logs where the start up was successful I can see that the next log messages are about acquiring a lock and checking the db.

I can confirm that even in the case where this hangs, it is still successfully creating the lock file, although it does not show that in the log.

Setting logging to debug does not give any additional information about this.

So my question is, what is actually happening in that step?

Determining this will help me figure out why these instances are no longer startable.

1 answer

0 votes
John Chin
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 18, 2012

Hi Britt,

I suspect is some kind of MySQL datasource connection problem with tomcat. Coud you check the following information?

The database connection is set on the server.xml file located at $JIRA_INSTALL/conf/. There are some parameters you can define to set it up, as the number of database connections. Following I will specify some that may help you:

  • maxActive is the maximum number of database connections in pool. Setting this value to zero means no limit.
  • maxIdle is the maximum number of idle connections in pool.
  • maxWait is the maximum time to wait for a database connection to become available in ms, An Exception is thrown if this timeout is exceeded. A value -1 means waiting indefinitely.
  • username and password is the username and password to connect to MySQL database.
  • url is the JDBC connection URL. Replace the values with the correct parameters to connect to database.

I also suggest you to take a look on Configuring a MySQL Datasource in Apache Tomcat.

Hope the information would help.

Regards,

John Chin

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events