soffice stays at 43%CPU

[rasacasa]

We are developing an application that runs on Linux that uses the OpenOffice API. We are finding that whenever we make an UNO Interprocess Connection to OpenOffice, the soffice process begins using about 43% of the CPU and continues to do so even if no API calls are being made after the initial connection is established.

We use the following command to start OpenOffice on the Linux server: /usr/bin/soffice -headless -norestore -accept="socket,host=0,port=8100;urp;" &

We have also use the following startup command with the same result: /usr/bin/soffice -headless -norestore -accept="socket,host=localhost,port=8100;urp;StarOffice.ServiceManager" &

We then start our application, which calls the following OO bootstrap API:

import ooo.connector.BootstrapSocketConnector;

xContext = BootstrapSocketConnector.bootstrap("/usr/local/opt/openoffice.org2.4/program");

The result of this single API call is that the soffice process on our Linux server starts using over 40% of the CPU and continues to do so. Has anyone seen similar behavior and know how to resolve this problem?

Thanks

[TerryE]

How many cores do you have on your server? I suspect 2. What is the average system load? 10-20% ? Probably what is happening here is that some thread in soffice.bin is becoming stuck at 100% compute bound and therefore taking up 50% of the machine's CPU. As to why this API call is doing this is another matter. Try having a scan of the issue database. Failing that I am afraid it's a case of binary chop diagnosis or using a debug build.

For this type of issue you might have more success on the Developers Mailing List.