Stephan, thanks for your help.
If my batch script which starts the Java program, starts an invisible
Libreoffice64 instance first (--invisible or such), maybe I find a way to
just connect to that running instance from within Java64. So I would bypass
the spawning of a Libreoffice64 instance from within Java64, which doesn't
work so far.
We'll see. In any case, thanks for your friendly efforts. All the best.
Greetings,
Aurelius
Am 24.08.2015 um 16:18 schrieb Stephan Bergmann:
On 08/24/2015 02:28 PM, Aurelius Octavian wrote:
Thank you Stephan for the hint. Dependency's profiling the "soffice.bin"
execution from within Java worked and I got a longer log.
However, since I'm no C(++) or Windows programmer I wouldn't know where
to search for a bug in the Java64->UNO->Libreoffice64 process.
Would somebody like to take a quick look at the log file, please? It's
here:
http://pastebin.com/v1x5sEUM
Or are there people in the Libreoffice developer team who know more
about this whole UNO thing, in order to spot the error when LO 64-Bit is
being called from Java 64-Bit?
My suspicion would be that, when spawned from the java.exe process,
soffice.bin runs in some subtly altered environment that e.g. causes it to
pick up unexpected instances of certain DLLs---something like picking an
MSVCRT DLL that is suitable for the java.exe but not for soffice.bin, or
similar.
However, I at least cannot spot any obvious issue in your pastebin,
unfortunately.
--
To unsubscribe e-mail to: [email protected]
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
