Sounds like a consequence of
<http://qa.openoffice.org/issues/show_bug.cgi?id=101457> "javaldx
searches for Java on every startup."
-Stephan
On 05/18/09 10:37, Steffen Grund wrote:
Hello Ariel,
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.
I have to investigate further.
Regards, Steffen
Ariel Constenla-Haile wrote:
Hi there,
trying OOo 3.1 (Sun's build, OOO310_m11), I find it's impossible (at
least on Linux) to make "Debug Extension in Target OOo". If fails
poping up the dialog with a deffective JRE, asking to choose a new one
in the Options dialog.
In NB output window:
ERROR: transport error 202: connect failed: Conexión rehusada
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports
initialized [../../../src/share/back/debugInit.c:690]
FATAL ERROR in native method: JDWP No transports initialized,
jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
JavaVM: JNI_CreateJavaVM called _exit, caught by abort_handler in
javavm.cxx
[Java framework] sunjavaplugin.soCan not create JavaVirtualMachine,
abort handler was called.
[Java framework] sunjavaplugin.soCan not create Java Virtual Machine
[Java framework] sunjavaplugin.soCan not create Java Virtual Machine
Of course, with this "Debug Extension in Target OOo" option, a new
user dir. is created on the build dir., which has no Java settings (as
it's a brand new user dir.).
In OOo 3.0.1 everything works.
Any hints?
Regards
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
