Hi Mike, I read somewhere that JodConverter (http://www.artofsolving.com/opensource/jodconverter) is moving in this direction.
Some time ago I wrote an application to manage a pool of OOo instances; it is now available as 3BTransform (commercial). It manages a pool of OOo instances under Java, restarting and retrying jobs as necessary. It took a lot of time to get the reliability required - running flat out for a couple of weeks with no errors. HTH Martin On Thu, 2008-11-13 at 11:09 -0700, Mike Patterson wrote: > I'm trying to set up an openoffice server environment to merge documents > and convert them to pdfs. I found the oood script located at > http://udk.openoffice.org/python/oood/index.html and updated it enough > to work with openoffice 2.x and didn't have to change anything to work > with 3.0. It works great, however when it gets under heavy load it will > segfault. It usually segfaults after a couple hundred uses and the > last time I tested it it segfaulted after 700. I was wondering if > anybody else has experienced this or had any other solutions I could > look at. > > I've tried just running several openoffice processes without using oood > and connecting to them directly, however I believe I'm getting hit by > the memory leak documented > http://www.openoffice.org/issues/show_bug.cgi?id=41675 and it ends up > taking out the server. I'd like to use oood to manage the processes and > handle restarting the servers as it works really well (until it > segfaults). But the main thing for me is to just get a stable > openoffice server environment up and running. > > We're using a new box with 8 processors and 4 gigs of ram, running Linux > version 2.6.18-92.1.13.el5 ([EMAIL PROTECTED]) (gcc version > 4.1.2 20071124 (Red Hat 4.1.2-42)) #1 SMP Wed Sep 24 19:32:05 EDT 2008 > > Here's the backtrace of the core file generated from the segfault: > Core was generated by > `/opt/openoffice.org3/program/../basis-link/program/python.bin > /opt/openoffice.o'. > Program terminated with signal 11, Segmentation fault. > #0 0xf7aa2827 in pyuno::GCThread::run () from > /opt/openoffice.org3/basis-link/program/libpyuno.so > (gdb) bt > #0 0xf7aa2827 in pyuno::GCThread::run () from > /opt/openoffice.org3/basis-link/program/libpyuno.so > #1 0xf7aa2b71 in threadFunc () from > /opt/openoffice.org3/basis-link/program/libpyuno.so > #2 0xf77ef0bb in osl_yieldThread () from > /opt/openoffice.org3/basis-link/program/../ure-link/lib/libuno_sal.so.3 > #3 0x002a646b in start_thread () from /lib/libpthread.so.0 > #4 0x0022cdbe in clone () from /lib/libc.so.6 > > Please let me know if anyone else has encountered this, has a solution, > or has had to do anything similar with keeping several openoffice > process running and recycling them to keep them from using too much memory. > > Thanks, > Mike > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > Filtered by 3BClean from http://www.3bview.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
