Jochen, all,

I think this issue shows two problems with javaldx and Java debug switches:

1 If what Steffen describes below (setting -Xdebug etc. in "Tools - Options... - Java" lets javaldx hang whenever it searches for a Java installation) can also happen with issue 101457 fixed, I think that is a bug that needs to be fixed in javaldx.

2 According to Steffen, NetBeans passes the debug switches to the JVM (that gets instantiated within OOo) via environment variables that are directly evaluated by the JVM. So that this does not interfere with javaldx starting JVMs, NetBeans should set an additional environment variable (or similar) to tell javaldx not to start any JVMs. (The chances are slim, but it could happen that NetBeans calls OOo to register the extension, then the Java installation used by OOo is removed, then NetBeans calls OOo again---this time with the JVM debug environment variables set---to debug the extension, and now javaldx notices that the old Java installation is no longer available and searches for a new one, starting up---hanging---JVMs.)

-Stephan

On 05/18/09 16:49, Ariel Constenla-Haile wrote:
Hello Stephan, Steffen, *

On Monday 18 May 2009, 05:45, Stephan Bergmann wrote:
Sounds like a consequence of
<http://qa.openoffice.org/issues/show_bug.cgi?id=101457> "javaldx
searches for Java on every startup."

yes indeed, and your patch has fixed it on my DEV300_m48 :-)
Log attached here

this happens for me (on Solaris x86) even without NetBeans etc.
I simply add e.g.
-Xdebug
-Xrunjdwp:transport=dt_socket,address=8701
as parameters to the JavaVM in OpenOffice.org. The next time I start
OpenOffice.org, I get the message box stating the JRE is defect.
I cannot reproduce this on Windows.

this means no debugging at all (even attaching) on Linux and Solaris.
I guess API developers on these plataforms will need you to upload somewhere a patched build of jvmfwk (or wait untill 3.1.1?)

Regards

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to