> The inner exception is RetryTimeoutException, which means the OOo
> process has been started, but the Java app couldn't connect to it
> within the timeout (30 seconds).
Well, I can't see the process by the end of these 30 seconds.
> Either your machine is very slow, or OOo is not starting up properly
> for some other reason. Try starting it manually and see if there's
> anything strange - like sometimes OOo gets stuck in "javaldx" trying
> to find a JVM.
Well, OOo doesn't seem to get stuck, as it exits very quickly when I
start it manually.
Maybe does something lack in my OOo installation...
Kind regards,
--
Bruno Verachten
Kind regards
Mirko
>> Maybe does something lack in my OOo installation...
> Yes could be. In any case if you start OOo manually with e.g.
> -headless "-accept=socket,port=2002" then you can check that 1) the
> process is running; 2) netstat shows it's listening on port 2002.
The process exists as soon as I start it. :-/
Best regards,
--
Bruno Verachten
2009/10/29 Verachten Bruno <goun...@gmail.com>:
>
>>> Maybe does something lack in my OOo installation...
>> Yes could be. In any case if you start OOo manually with e.g.
>> -headless "-accept=socket,port=2002" then you can check that 1) the
>> process is running; 2) netstat shows it's listening on port 2002.
> The process exists as soon as I start it. :-/
>
Well then clearly there's something wrong with your OOo installation.
I don't know anything about your system so I can't make a guess. Is it
the latest OOo from download.openoffice.org?
Kind regards
Mirko
> Well then clearly there's something wrong with your OOo installation.
> I don't know anything about your system so I can't make a guess. Is it
> the latest OOo from download.openoffice.org?
No, it wasn't. :-( We now have the official release, and it works.
Sorry to have made you loose some time.