Tomcat 5.5 notes

JIRA Documentation

Index

This page has general notes on installing JIRA on Tomcat 5.5.x. It supplements the official Tomcat installation docs.

add your notes

A user writes: 

There is a readme file shipped with JIRA. It said that you need to change port 8080 in order to get Tomcat(say a) to start up. BUT, if you have a CATALINA_HOME environment variable already set for an existing Tomcat(say b) running on the same server, running startup from the bin directory will start up Tomcat(b). For Tomcat(a) to start one needs to delete the existing CATALINA_HOME environment variable as well.

Labels

 
(None)
  1. Apr 08, 2007

    Grant Burnes says:

    Also, the documentation does not include the note to remove the PUBLIC schema na...

    Also, the documentation does not include the note to remove the PUBLIC schema name if you are using MySQL   

    1. Apr 11, 2007

      Dushan Hanuska says:

      The fact that {{PUBLIC}} schema should be removed from JIRA entity engine ({{WEB...

      The fact that PUBLIC schema should be removed from JIRA entity engine (WEB-INF/classes/entityengine.xml) is documented in Connecting JIRA to MySQL

  2. Jun 14, 2007

    Owen Carter says:

    The file .../tomcat/bin/setenv.sh did not exist in my tomcat install (tomcat 5.5...

    The file .../tomcat/bin/setenv.sh did not exist in my tomcat install (tomcat 5.5.23) although the startup.sh (and .bat etc.) scripts test for it's presence and use it if available.

    To complete the 'avoid memory leak' step I had to create the file, copy in the memory leak fix and then set it executable.

  3. Mar 26

    Jamie says:

    Does the memory leak warning apply to standalone jira? We are using 3.11 and don...

    Does the memory leak warning apply to standalone jira? We are using 3.11 and don't see that property set in the setenv.sh scripts.
    cheers, jamie

  4. May 21

    Ivan Hudak says:

    tomcat issues on OpenSuSE 10.3 I had problems installing Jira to OpenSuSE 10.3 ...

    tomcat issues on OpenSuSE 10.3

    I had problems installing Jira to OpenSuSE 10.3 to tomcat 5.5:
    2008-01-04 23:22:59,963 main WARN [core.entity.transaction.JNDIFactory] [ConnectionFactory.getConnection] Failed to find DataSource named java:comp/env/jdbc/JiraDS in JNDI server with name default. Trying normal database. javax.naming.NamingException: Could not create resource factory instance [Root exception is java.lang.ClassNotFoundException: org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory]

    I could not find the solution on atlassian site but found it here: http://toscano.org/~pete/blog/
    ...the problem is with the distro's use of the Jakarta Commons version of DBCP and Tomcat's expectation that the BasicDataSourceFactory class being in Tomcat's naming-factory-dbcp.jar file. For whatever reason, the distro preferred the Jakarta version.This can be simply solved by adding the following to your JAVA_OPTS environmental variable:

    -Djavax.sql.DataSource.Factory=org.apache.commons.dbcp.BasicDataSourceFactory

    ...which is most likely in /etc/sysconfig/tomcat55