This page last changed on Jun 24, 2010 by alui.

Deploying multiple Atlassian applications in a single Tomcat container is not supported. We do not test this configuration and upgrading any of the applications (even for point releases) is likely to break it. There are also a number of known issues with this configuration:

  • You may not be able to start up all of the applications in the container, due to class conflicts that result from the Atlassian applications sharing a single JVM in the Tomcat container.
  • You will not be able to determine the startup order of the applications. Hence, you may experience problems such as JIRA starting before Crowd, rather than vice versa.
  • Memory problems are also common as one application may allocate all of the memory in the Tomcat JVM to itself, starving the other applications.

We also recommend that you do not deploy multiple Atlassian applications in a single Tomcat container for a number of practical reasons:

  • You will need to shut down Tomcat to upgrade any application.
  • If one application crashes, the other applications running in the Tomcat container will be inaccessible.
Document generated by Confluence on Jul 09, 2010 01:11