This documentation relates to the latest version of Confluence.
If you are using an earlier version, please go to the documentation home page and select the relevant version.
The Confluence EAR-WAR edition is intended for deployment into an existing J2EE application server.
To use this method of installation, you or your application server administrator must already know how to deploy a web application on the application server of choice. If not, please use the Confluence Standalone edition instead.
In addition to the above requirements, the EAR-WAR edition requires an application server. Here are our guidelines on compatible and supported servers:
Supported and Compatible J2EE Application Servers
Confluence supports the following application servers, provided they are running on a Windows, Unix (NetBSD, FreeBSD, OpenBSD, Solarix, Linux), Mac OS X on X86 or X86-64 processors.
Supported in Confluence 3.0 (JUN/2009)
Works with Confluence 3.0
Apache Tomcat
5.5.20+, 6.0
5.5
BEA Weblogic
9.2
9.1, 10
IBM Websphere Application Server
6.1
Caucho Resin
3.0, 3.1.6, 3.1.7
JBoss
4.2
Column labelled 'Works with' as opposed to 'Supported in': We assume that Confluence works fine with these application server versions. But please be aware that we don't test these versions regularly and that we may ask you to upgrade to a supported version before we can provide more detailed support.
If you have no preference, we recommend using Confluence Standalone which includes Apache Tomcat.
Unsupported J2EE Application Servers
For Confluence 2.10 and later, the following application servers are no longer supported:
Tomcat 5.0 — please upgrade to Tomcat 5.5 or 6
Resin 2 — please upgrade to Resin 3.0 or 3.1
JBoss 4.0.x — please upgrade to JBoss 4.2.x or higher.
The decision to deprecate these platforms was announced previously.
Potentially Compatible Application Servers
The following application servers may work with Confluence. Whilst they are not known to possess any problems or incompatibilities with Confluence, they have not been sufficiently tested to be considered a compatible Application Server. Consequently, they are not supported.
The following application servers may (in part) work with Confluence. However, they are known to possess problems or incompatibilities with Confluence and consequently are not supported.
Oracle OC4J / Oracle Application Server — see reported issue
If you deploy Confluence on an unsupported server, server-related issues cannot be covered by Atlassian technical support. You can try the user forums for assistance instead.
"The value of this field must not be set except when statically defining a Context in server.xml, as it will be inferred from the filenames used for either the .xml context file or the docBase."
Kind of annoying as when I configure it this way, I get confluence trying to start twice.
Hi Tony,
Thank you for sharing that with us As you may have already noticed, w...
Hi Tony,
Thank you for sharing that with us As you may have already noticed, we have a feature request to support GlassFish. I have added your comment to the report, as I believe, it would be helpful for GlassFish adopters and our developers as well.
Hello Tony,
Thanks for making your suggestion available on this page.
The cont...
Hello Tony,
Thanks for making your suggestion available on this page.
The content above has been updated to clarify how we distinguish between the "Compatible", "Potentially Compatible" and "Known Incompatible" Application Server categories for Confluence.
We have recently received reports from customers who are experiencing configuration and functional issues with Confluence on GlassFish. However, we will consider moving GlassFish out of its current category (above) once these issues have been resolved.
Confluence requires a maximum heap allocation (Xmx) of at least 256 MB
Is this...
Confluence requires a maximum heap allocation (Xmx) of at least 256 MB
Is this still a realistic minimum? For example, functions such as a PDF export of even a small space will require hundreds of megabytes. Likewise for XML exports.
Hi Paul,
It is actually really depending on your instance and your usage. If yo...
Hi Paul,
It is actually really depending on your instance and your usage. If you install a lot of plugins in your instance, Confluence needs more memory. And also, if your instance is being accessed by a lot of people, it is also need more memory. The memory is needed to populate Java object. I use a simple usage on my local machine with 256m, it works fine when exporting my space to PDF, HTML or XML.
Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.
Comments (6)
May 01, 2008
Nathan Ollerenshaw says:
You can't set confluence to be the root in at last Tomcat 5.5 inside the conflue...You can't set confluence to be the root in at last Tomcat 5.5 inside the confluence.xml file using the hint:
"To run Confluence without a context path of "/confluence", change the path in the Context tag to an empty string ("")."
The documentation for tomcat seems to explicitly define this use case to be configured in the server.xml:
in http://tomcat.apache.org/tomcat-5.5-doc/config/context.html:
"The value of this field must not be set except when statically defining a Context in server.xml, as it will be inferred from the filenames used for either the .xml context file or the docBase."
Kind of annoying as when I configure it this way, I get confluence trying to start twice.
Jan 08
Tony Ng says:
I have just downloaded GlassFish v3 Prelude and tried it with Confluence 2.10 us...I have just downloaded GlassFish v3 Prelude and tried it with Confluence 2.10 using eval license. It works just fine.
The only change I have to make is to increase the heap & perm gen space with the following options in domain.xml under <java-config>
<jvm-options>-server</jvm-options>
<jvm-options>-Xmx1024m</jvm-options>
<jvm-options>-XX:MaxPermSize=512m</jvm-options>
Would appreciate if Confluence can update the above table regarding GlassFish compatibility.
Thanks,
Tony
Jan 09
Azwandi Mohd Aris says:
Hi Tony, Thank you for sharing that with us As you may have already noticed, w...Hi Tony,
Thank you for sharing that with us
As you may have already noticed, we have a feature request to support GlassFish. I have added your comment to the report, as I believe, it would be helpful for GlassFish adopters and our developers as well.
Cheers,
Azwandi
Jan 21
Giles Gaskell [Atlassian Technical Writer] says:
Hello Tony, Thanks for making your suggestion available on this page. The cont...Hello Tony,
Thanks for making your suggestion available on this page.
The content above has been updated to clarify how we distinguish between the "Compatible", "Potentially Compatible" and "Known Incompatible" Application Server categories for Confluence.
We have recently received reports from customers who are experiencing configuration and functional issues with Confluence on GlassFish. However, we will consider moving GlassFish out of its current category (above) once these issues have been resolved.
Best regards,
Giles Gaskell
Technical Writer
ggaskell@atlassian.com
ATLASSIAN - http://www.atlassian.com
Apr 23
Paul Curren says:
Confluence requires a maximum heap allocation (Xmx) of at least 256 MB Is this...Is this still a realistic minimum? For example, functions such as a PDF export of even a small space will require hundreds of megabytes. Likewise for XML exports.
May 07
Arie Murdianto says:
Hi Paul, It is actually really depending on your instance and your usage. If yo...Hi Paul,
It is actually really depending on your instance and your usage. If you install a lot of plugins in your instance, Confluence needs more memory. And also, if your instance is being accessed by a lot of people, it is also need more memory. The memory is needed to populate Java object. I use a simple usage on my local machine with 256m, it works fine when exporting my space to PDF, HTML or XML.
Cheers,
Add Comment