Hi,
it is a known fact that OOo has several multithreading problems. Most of them reveal when using OOo API via remote UNO. Every single multithreading problem can be considered a bug, but fixing all of them is a rather complex task (due to the size and complexity of OOo code). However, we're working on it... but even OOo 2.0 will still suffer from multithreading issues.
For now, I strongly suggest not to use OOo in a multithreaded way.
Several workarounds for OOo's multithreading problems have been discussed in the OOo mailing lists already. You should follow one of these approaches.
- Kai.
John Sisson wrote:
Hello We have a Java gui client that manages a pool of oo documents (xp + oo.1.1..3) and executes oo-Basic macros on them via a UNO XDispatch interface. We also have Java robotic processes that need to do the same.
While we can serialize attempts to execute macros in a single client (or robotic) process, there is the chance that two robotic processes on the same machine, sharing the same soffice.exe instance will attempt to launch oo-basic macros on their documents simultaneously. The documentation implies that this will cause oo-basic to fail.
- is this so? - will XDispatch try to launch a basic macro on behalf of one client while another is running on behalf of another client?
- is there any defense against this? - I imagine it would require some mutexes in the heart of the oo side of XDispatch
thank you john sisson
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]