I was writing a piece on Glassfish this evening, as I’m looking to move Confluence to be deployed on it as opposed to Tomcat. I think Tomcat must have sniffed trouble though, as it’s been incredibly demanding on the VM front tonight. I suspect it’s been grabbing resource for a few days now, and so this box has been ridiculously sluggish to respond to anything.
Ceteris paribus, assuming Glassfish works out, Tomcat is outahere for being fat and greedy on the memory front. I mean – consuming 300Mb is just crazy talk for a personal wiki.
No related posts.
Related posts brought to you by Yet Another Related Posts Plugin.
Paul lives, rides and works in Cardiff, South Wales. His work seems to largely entail fixing things and keeping wheels on. Officially, he is actively engaged and interested in Enterprise Architecture these days, but has a secret past that involved standing around on glaciers collecting meltwater samples, and walking through endless fields of wheat taking radiance measurements. 
Please let us know (theaquarium@sun.com) when you succeed in moving Confluence to GlassFish. I’ve heard of other reports but it is always good to confirm. And ditto if you encounter problems – we will work with you to fix them. – eduard/o
Will do. Given we seem to moving towards sneaking Glassfish in at work at the moment, it makes sense to give it a try
That Roller install we did sits at about 300Mb – that’s the whole zone though, so hopefully you’d see some benefit.
We’d save a lot of space by not using all the EJB stuff – I’m holding out for v3 and the HK2 (‘hundred Kb kernel’) for a true tomcat replacement.
I’ll take a look at Confluence – so long as it’s WARred, it should be easy enough.
See me next week to talk about Terracota too.
We have an old version of Confluence (2.2.9) running on Tomcat 5.5.15 on Linux, and using MySQL (on the same server).
With a max heap size of 512 MB the backup process has started to fail consistently with an OutOfMemoryError.
When I’ve tried to increase the max heap size to 1GB, Tomcat would fail to start with an OutOfMemoryError. There was more than 2GB available memory. Even 600MB was doing the same.
Yesterday, though, the stars seemed to have lined up correctly for me. I set the max heap to 640 MB and Tomcat did start, and the 4GB backup zipped file was created at 2 AM.
I’m in the process of moving Confluence to Sun AS 8.1 on Solaris, in a 2 node cluster, with DB2. I’ve got it to work, but more testing is needed.
breadedcod,
Did you experience similiar issues with Tomcat, as mentioned in my previous post?
What are you planning to do about support from Atlassian? They currently don’t support Confluence on Sun AS or Glassfish.
I did speak to Atlassian about this. They claim that they just don’t have the demand, at present, to warrant assigning their resources to start supporting these app servers.
I think if I can get the move done, we’ll have a chat with Atlassian about future support for GF. What prompted to look was As we run with mainly ORA or MySQL backend, it’d be fairly trivial to fall back to Tomcat if we really need to – for testing and the like. Support has never really raised its head in the past, but it’s a valid point
Replacing a servlet container with a full J2EE server just to run Confluence seems extreme.
How about Jetty?
Well, yes, perhaps. However – life is far too short to be a-messin’ with too many pick-n-mix approaches to the application server issues @ work, so I’d really like to get to some sort of agreement on what we use other than WAS for stuff we have control over. Besides that, I’m not all that fussed as Dick will have to look after everything anyway
@Mike – hi, long time no see. The glassfish admin bits are what sells it – you know how anti-J2EE I am, but it’s easy on the RAM and a piece of cake to use.