Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Equinox » BUG#121737 and Eclipse 3.2.1
BUG#121737 and Eclipse 3.2.1 [message #86113] Wed, 04 April 2007 14:53 Go to next message
stoil is currently offline stoilFriend
Messages: 46
Registered: July 2009
Member
Hi all,

This is a repost - sorry later found the right newsgroup.

I've run into deadlock problems and finally found this bug
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=121737) which actually is
my problem. Is there safe workaround for 3.2.1 ? I tried -XX
+UnlockDiagnosticVMOptions -XX:+UnsyncloadClass and it worked for me, but
is this safe?

Best regards,
Stoil
Re: BUG#121737 and Eclipse 3.2.1 [message #86185 is a reply to message #86113] Wed, 04 April 2007 21:31 Go to previous message
Eclipse UserFriend
Originally posted by: john.eclipsefaq.org

That doesn't look very safe to me. I think the "XX" options in the JVM
are generally unspecified and unsupported - use at your own risk.
--

Stoil Valchkov wrote:
> Hi all,
>
> This is a repost - sorry later found the right newsgroup.
>
> I've run into deadlock problems and finally found this bug
> (https://bugs.eclipse.org/bugs/show_bug.cgi?id=121737) which actually is
> my problem. Is there safe workaround for 3.2.1 ? I tried -XX
> +UnlockDiagnosticVMOptions -XX:+UnsyncloadClass and it worked for me, but
> is this safe?
>
> Best regards,
> Stoil
Previous Topic:simple tutorial on OSGi/Equinox extension points?
Next Topic:Disabling Jetty server on startup
Goto Forum:
  


Current Time: Fri Mar 29 10:06:03 GMT 2024

Powered by FUDForum. Page generated in 0.01827 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top