Apache OpenOffice Community Forum

Hi

This is my first post and I wasnt sure were to post this topic (maybe external programs or troubleshooting).

Running OpenOffice.org2.4
OS is Linux details are
bash-3.00$ more /etc/redhat-release
Red Hat Enterprise Linux ES release 4 (Nahant Update 5)
bash-3.00$ uname -sar
Linux bfs-hs20-05s5.bfs.phone.com 2.6.9-55.ELsmp #1 SMP Fri Apr 20 17:03:35 EDT 2007 i686 i686 i386 GNU/Linux
bash-3.00$

So Im working on using OpenOffice(OO) to convert certain document types to HTML. A Java servlet connects to an OO server over TCP and sends the document to be converted, which is then converted and written to disk. This works well. A basic prototype is up and working.

I have started the server on the command line using the following
soffice -headless -accept="socket,host=127.0.0.1,port=8100;urp;" -nofirststartwizard

1. Is it possible to configure the number of concurrent connections allowed to the OO server at any one time?
2. What is the default number of concurrent connections allowed to the OO server?
3. Is there any log files created by the OO server, that may illuminate this type of detail?

Thanks

A maximum of one concurrent client can reliably use one instance of an "OpenOffice.org server." Why? Think of it as if multiple people were trying to simultaneously use one instance of OpenOffice.org running on your desktop. That is basically what you are describing.

There are no logs.

If you wish to scale up (is that your goal?), you must connect to multiple instances. You may do this through a proxy. There's such an old proxy here: http://udk.openoffice.org/python/oood/

P.S. I'm moving this from Beginners to Macros and UNO API.

Andrew, that clarifys a lot for me.

Yea scaling up is what I want to acheive. So I will need to start multiple instances of OpenOffice server listening on different ports and proxy the requests accordinlgy to each instance.

Thanks

Yes, or something similar. Alternative to a proxy, you could implement load balancing with a mutex in your application. I think this is not so different from what people to do scale up databases such as MySQL: the application knows to perform read operations against random pool of one-way-replicated database servers.