Hi,

I've also successfully installed Confluence on Glassfish (V1 M7 or V2 M1) with MySQL 5.0.22 and its latest JDBC driver (3.1.13) on Ubuntu Linux 2.6.15 and Solaris 10.

However, when I'm trying to run JIRA on the same app server (with its own connection pool), Glassfish hangs and takes 100% of the CPU (attached the jstack and ulimit on the Linux server). I think it's not a DB connection limit problem because I'm still able to connect to the DB from the configured users (tried via command line client).

A little precision on the JIRA installation, when installed alone on the same app server, it works perfectly.

Any help is welcome

Cheers,

Daniel

We also successfully run Confluence and JIRA on Glassfish. We haven't yet seen the problem mentioned above.

However, the "Remember me" checkbox for authentication does not work under Glassfish. This is reported under http://jira.atlassian.com/browse/CONF-7378. Please vote for this issue if you're interested in seeing it fixed.

Does anyone tried Glassfish V2.0 ?

I've successfully had Confluence (recently upgraded to 2.6.0 from 2.4.5) running under glassfish-v2-58g (upgraded from glassfish-v2-b41d). The old configurations were on windows platform, the upgrades moved them to linux. No issues experienced yet. We'd like to get glassfish on the supported platforms list as well.

v2-58g is the FCS release of glassfish v2

Only problem we've seen is with the attempt to deploy jira to the same system. It fails, but I'm taking that up elsewhere.

Getting Confluence running on Glassfish is providing a royal pain. I managed to get a 2.8.0 to do a blank site install, however, trying to do a restore to glassfish (2.7.2) on both Windows and Linux, appears to hang at 5% feedback with no Exceptions in server side logs, if I'm lucky. More often than not I get:

org.springframework.transaction.CannotCreateTransactionException: Could not open Hibernate Session for transaction; nested exception is java.lang.NullPointerException
 at org.springframework.orm.hibernate.HibernateTransactionManager.doBegin(HibernateTransactionManager.java:470)
caused by: java.lang.NullPointerException
 at com.sun.gjc.spi.base.ConnectionHolder.setAutoCommit(ConnectionHolder.java:625)

Mmmm.

Tony Ng commented on CAC (9/Jan/2009):

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

Here's the blog entry detailing the installation: http://blogs.sun.com/theaquarium/entry/confluence_on_glassfish_v3

I've been running confluence and jira both on glassfish at various clients over the past 2-3 years with little to no problems.

Hi, since many month now, we've bought Confluence. We're hosting it on a Glassfish V2 appserver after doing tricky things to make it works, and enjoying this really cool application.

Everything was all right, but yesterday we've decided to buy both Jira and GreeHopper and then have upgraded our Confluence in order to have all the applications up to date.
Now we can't manage to make confluence 3 works on glassfish (sic !), ok, Glassfish is not supported by Atlassian so we decided to switch temporary to tomcat ... and then ... our brand new JIRA 4.0 seem's to be incompatible with AJP (hu ! do you know how much appserver are using mod_jk? It's weird that you decided to release a stable version with such a bug !).

I'm a bit disapointed because you dont seem's to pay attention to people claiming for a glassfish support (It's the JEE5 reference implementation, and it's user base is groing significantly).

Are you planning to support Glassfish in the short term or not ?

what issues do you see when running conf3 with glassfish v2.1? I'm using that config for day to day development and it works fine.

the only thing I had to do was to fix the class path so that xalan that is distributed with confluence is used instead of the one that comes with glassfish.

I've had no problems running confluence and glassfish. It's such a fantastic container from an administrative perspective. I'd rather see glassfish support than resin or websphere, ugh, please. The cool-aid is taste! Drink!

We manage to make it work on Glassfish, but its still impossible to use it through Mod_jk, and that's what was blocking us in fact.

I see. I quit front-ending glassfish with apache that way. It doesn't add any value in my environment. But, direct to glassfish, confluence works great!

Atlassian people, please support glassfish!

Glassfish v3 related issue and solution: http://jira.atlassian.com/browse/SER-144 (doesn't affect GlassFish v2.1)

One more GlassFish v3 related issue and patch: http://jira.atlassian.com/browse/CONF-18093 (doesn't affect GlassFish v2.1)

And the last known issue with a patch that affects both GlassFish v2.1 and v3: http://jira.atlassian.com/browse/CONF-18094