Martin Gallwey wrote: > Hmm, thanks kso/kr for the document on thread safety in the UDK. This > paragraph: > > ยท *Issue*: Many OOo UNO API implementations are not thread safe. > *Expectation*: The OOo UNO API implementations can be used by multiple > threads and clients simultaneously. > *Sample Code*: [to be provided: crasher] > *Note*: Consequently that means, that the OOo API can not reliable be > programmed in Java, because of the currently available Java VMs > utilizing dedicated threads for finalization. > > Seems to shed light on my problem. With this info in mind, I took a look > at what was happening when the original jni_uno::BridgeRuntimeError was > thrown, and the results are below. Both threads are active inside the > core at the same time => Kaboom.
While the analysis of K&K is correct I don't think that the non-thread safety of object destruction is your problem, the call stack shows no indication. And BTW not all destructors create a problem, only destructors that call into the code of other, still living objects that can be accessed from other threads and so are prone to race conditions. So a general problem doesn't mean that you are hit by it *always*. > Is there a work around or do I re-write my filter in C++ ? I don't know. Before giving a judgement on that we should find out what your problem is. :-) Ciao, Mathias -- Mathias Bauer - OpenOffice.org Application Framework Project Lead Please reply to the list only, [EMAIL PROTECTED] is a spam sink. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
