Documentation for Crowd 2.9. Documentation for earlier versions of Crowd is available too.

Skip to end of metadata
Go to start of metadata

This page describes the supported platforms and hardware requirements for Crowd 2.9.

Key: (tick) = Supported. (error) = Not Supported

Java Version



Oracle JDK (1)

(tick) 1.8

Please note that JDK versions older than 8u65 may have problems connecting to LDAP servers over SSL - see CWD-4444 - Secure LDAP connections are broken when using Java 1.8u51, 1.8u60, 1.7.0_85+ and 1.6.0_101+ RESOLVED  for more details.
OpenJDK(tick) 1.8
Operating Systems



Microsoft Windows ( 2 )



Linux / Solaris ( 2 )



Apple Mac OS X ( 2 )


Application Servers



Apache Tomcat ( 3 )

(tick) 7.0.x (Crowd ships with Apache Tomcat 7.0.69)





MySQL ( 4 )

(tick) 5.0.37 and later



(tick) 12c
(tick) 11g (Tested on
(tick) 10g (Tested on



(tick) 9.3
(tick) 9.2
(tick) 8.x
(tick) 7.x


Microsoft SQL Server

(tick) 2012
(tick) 2008 R2, 2008
(tick) 2005


HSQLDB ( 5 )

(tick) (For evaluation only.)

Web Browsers


Chrome (tick) Latest stable version supported 

Microsoft Internet Explorer (Windows)

(tick) 10, 11


Mozilla Firefox (all platforms)

(tick) Latest stable version supported



(tick) Latest stable version supported



1. JDK:

  • It is not enough to have the JRE only. Please ensure that you have the full JDK. You can download the Java SE Development Kit (JDK) from the Oracle website.
  • Once the JDK is installed, you will need to set the JAVA_HOME environment variable, pointing to the root directory of the JDK. Some JDK installers set this automatically (check by typing 'echo %JAVA_HOME%' in a DOS prompt, or 'echo $JAVA_HOME' in a shell). If it is not set, please see Setting JAVA_HOME.

2. Operating systems: Crowd is a pure Java application and should run on any platform provided the Java runtime platform requirements are satisfied.

3. Tomcat: 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. See this FAQ for more information.

There are also a number of practical reasons why we do not support deploying multiple Atlassian applications in a single Tomcat container. Firstly, you must shut down Tomcat to upgrade any application and secondly, if one application crashes, the other applications running in that Tomcat container will be inaccessible.

Finally, we recommend not deploying any other applications to the same Tomcat container that runs Crowd, especially if these other applications have large memory requirements or require additional libraries in Tomcat's lib subdirectory.

4. MySQL: Please ensure that you set transaction isolation to 'read-committed' instead of the default 'repeatable-read', as described in the database configuration guide.

5. HSQLDB: Crowd ships with a built-in HSQL database, which is fine for evaluation purposes but is somewhat susceptible to data loss during system crashes. For production environments we recommend that you configure Crowd to use an external database.

Hardware Requirements

The hardware required to run Crowd depends significantly on the number of applications and users that your installation will have, as well as the maximum number of concurrent requests that the system will experience during peak hours.

During evaluation Crowd will run well on any reasonably fast workstation computer (eg. 1.5+Ghz processor). Memory requirements depend on how many applications and users you will store, but 256MB is enough for most evaluation purposes.

Most users start by downloading Crowd, and running it on their local computer. It is easy to migrate Crowd to your enterprise infrastructure later.

We would appreciate if you let us know what hardware configuration works for you. Please create a support request in JIRA with your hardware specification and mention the number of applications and users in your Crowd installation.

While some of our customers run Crowd on SPARC-based hardware, Atlassian only officially supports Crowd running on x86 hardware and 64-bit derivatives of x86 hardware.



  1. Crowd seems to work perfectly on Resin 3.1.9, once it's configured properly (smile)
    Now, Crowd uses XFire, XFire works best with WoodStox, and voila (wink)

    I have posted what seems to be the solution to CWD-1192:
    Set all required parser factories using corresponding system properties, best if isolated for the corresponding web-app.

          <web-app id="/crowd" root-directory="webapps/crowd" >
             <!-- xml -->
             <system-property javax.xml.parsers.DocumentBuilderFactory=
             <system-property javax.xml.parsers.SAXParserFactory=
             <!--  xslt -->
             <system-property javax.xml.transform.TransformerFactory=
             <!-- StAX for XFire! -->
             <system-property"com.ctc.wstx.stax.WstxInputFactory" />
             <system-property"com.ctc.wstx.stax.WstxOutputFactory" />
             <system-property"com.ctc.wstx.stax.WstxEventFactory" />

    Enjoy (smile)

  2. In regards to Java - you should really link to this page to ensure that people are aware of this PRIOR to the installation of the JDK:

    I installed a 64 bit version and now have to configure my way around the problem. I would have gone for the 32 bit version if I knew.

    1. Anonymous

      Seconded: I too now have to go back and install the 32 bit version.  Far too much of the Atlassian documentation is like spaghetti, one has to go backwards and forwards a LOT!  I find it very frustrating that I am now having to spend yet more time (already up to about 5 hours and climbing rapidly) on what should be a much simpler installation process, and if they had listened to you when you posted this over half a year ago, (how long does it take to add a sentence warning used to install the 32 bit version?), I would not be having to spend yet more precious time unnecessarily.  Grr....

      1. Anonymous

        In case this helps those who find themselves in the same situation, here are the steps that worked for me:

        After some experimentation, I solved the problem by uninstalling the 64 bit JDK, then installing the 32 bit one, then changing the environment variable JAVA_HOME to the 32 bit path ( C:\Program Files (x86)\Java\jdk1.7.0), then uninstalling Crowd as a service (via the command line: service.bat uninstall Crowd), then carrying out the instructions to add Crowd as a windows service (service.bat install Crowd, etc., see

  3. Successfully running Crowd 2.2.7 with FreeBSD 6.3 / PostgreSQL / JDK 1.6.0_03.

    I'm using the following rc script to start / stop crowd services.

    # PROVIDE: crowd
    # REQUIRE: LOGIN cleanvar
    . /etc/rc.subr
    load_rc_config $name
    export JAVA_HOME=/usr/local/jdk1.6.0/
    export CATALINA_PID=${pidfile}
    export JAVA_OPTS="-Xms128m -Xmx256m -XX:MaxPermSize=160m"
       if [ ! -f ${pidfile} ]; then
          debug "pid file (${pidfile}): not readable."
       read _pid _junk < ${pidfile}
       if [ -z $_pid ]; then
          debug "pid file (${pidfile}): no pid in file."
       return $_pid
       if [ $_pid -ne 0 ]; then
         echo "Stopping crowd with pid: $_pid."
         cd ${crowd_home}
       if [ $_pid -ne 0 ]; then
         echo "Crowd is running with pid: $_pid."
         echo "Crowd is not running."
    run_rc_command "$1"
  4. Anonymous


    is oracle11g supported ?

  5. Anonymous

    Is there a timeline for Oracle 11 support?

  6. JDK 1.7 should be added to the list of supported Java versions. According to the release notes, it is supported in Crowd 2.5.