Apache OpenOffice Community Forum

I've got a more general question, so hopefully this is the right place to ask. When I use OpenOffice (in particular Writer) as a server and headless, how is its memory consumption? More importantly, how does it scale with increasing numbers of connection and documents?

http://sourceforge.net/projects/oodaemon/

Description

Open Office Server Daemon based on older daemon written in python (oood).
Open Office is unstable as a server (memory leaks, not multithreaded, ...), this daemon makes it working in long-term without having to change anything in your code.

Hum, thank you for that link! The demon website seems a little bit dated too and the demon itself is from 2007?

After some time of silence I'd like to reactivate this question: has anything changed and/or improved?

Did you try the oodaemon?

Villeroy wrote:Did you try the oodaemon?

Do you refer to this Sourceforge project with last update 2013? I read through it but was discouraged by the old date. Is this the recommended way of using AOO as a server?

I was wondering if anything had changed since I asked the question several years ago.

If you are discouraged by the old date, why do you run Openoffice then?

Villeroy wrote:If you are discouraged by the old date, why do you run Openoffice then?

AOO or LO, I've never really figured out which one to use. Can I interpret your question as AOO is outdated then?

Since 2010 only the side bar and a couple of bug fixes have been added to OpenOffice. If you ignore the sidebar (like I do), the latest AOO is the very much the same as OpenOffice.org 3.3 of 2010. It is very unlikely that the ooodaemon of 2013 is incompatible in any way with today's OpenOffice.
LibreOffice introduces more features and fixes within 3 months although some of the new featues are questionable. I would not be surprised if the ooodeamon fails to run with LO, however when searching the web for "LibreOffice daemon" you get completely different options e.g. running LO in a browser.

Thank you. I’ve read through some of the LO threads regarding server-mode and that wasn’t too promising either. It looks like my best option is to write a wrapper myself, perhaps even based on the oodemon’s source code. My current approach of starting a LO/AOO instance whenever I need it, and then completely tear it down when done just doesn’t scale and takes quite a lot of time...

Recent topic where someone found his solution for a Linux server: viewtopic.php?f=44&t=87188