Deploying JIRA on Tomcat

I'm not sure how to deploy the tar.gz I downloaded, it is not the WAR and I do not want to the self installer. I'm running Tomcat 7.

I downloaded the JIRA (TAR.GZ Archive) from

1 answer

0 votes

There are only two things you can really download - self-installation and war

The war version requires you to build the war yourself, given the contents of the download. It is simple though - download it, unpack it, make any changes you need, then run " war" and it will create a set of .war files suitable for various application servers.


Ok, Thank You. I'll try this, once I do this I can deploy multiple WARs on the same server, correct?

I followed those instructions, however it tells me an error when I submit the setup page with the DB stuff. I'm using mysql.

com.opensymphony.module.propertyset.PropertyImplementationException: while inserting: [GenericEntity:OSPropertyEntry][id,null][entityId,1][propertyKey,webwork.i18n.encoding][type,5][entityName,] (SQL Exception while executing the following:INSERT INTO propertyentry (ID, ENTITY_NAME, ENTITY_ID, PROPERTY_KEY, propertytype) VALUES (?, ?, ?, ?, ?) (Column 'ID' cannot be null))

I have these logs, I can provide more if necessary:


SEVERE: Servlet.service() for servlet jsp threw exception
com.atlassian.jira.util.dbc.Assertions$NullArgumentException: jiraLicenseService should not be null!
SEVERE: Exception Processing ErrorPage[errorCode=500, location=/500page.jsp]
org.apache.jasper.JasperException: An exception occurred processing JSP page /500page.jsp at line 113

==> /usr/local/apache-tomcat-7.0/logs/localhost_access_log.2013-01-28.txt <== - - [28/Jan/2013:04:09:30 +0000] "POST /jiralw/secure/SetupDatabase.jspa HTTP/1.1" 500 13528

==> /usr/local/apache-tomcat-7.0/logs/catalina.2013-01-28.log <==
Jan 28, 2013 4:09:54 AM org.apache.catalina.loader.WebappClassLoader loadClass
INFO: Illegal access: this web application instance has been stopped already. Could not load org.apache.commons.pool.impl.CursorableLinkedList$Cursor. The eventual following stack trace is caused by an error thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access, and has no functional impact.


The later errors are likely to be caused by the database being broken.

It's possible your database settings are incorrect, but that error implies something is wrong in the settings, as it's trying to do something it can't. You need to read the log from startup to where the first sql error occurs to trace it back. Are there other, similar errors? In fact, any errors before that insert? Can you check the database and see what has been created and if it's fully read/write by the Jira/Tomcat user?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,797 views 18 22
Read article

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