| ClassLoader deadlock issues [message #74847] |
Fri, 13 October 2006 17:31  |
Eclipse User |
|
|
|
Originally posted by: kirby.bohling.gmail.com
All,
(I sent sent this same message to equinox-dev, sorry if they are the
same thru a news-to-mail gateway).
I've been working with Eclipse, and use Buddy Loaders fairly extensively
so that core plug-ins can construct objects from their child plug-ins
at runtime.
The ClassLoader segmentation is causing me lots and lots of issues w/
BuddyLoaders and the deadlock.
I've seen this thread:
http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg01354.ht ml
This pretty much exactly covers my case. Are there any workarounds or
mitigations? I use object serialization for over the wire communication
and spring both of which use Global buddy loaders. Currently my
application deadlocks 9 times out of 10.
I've been looking into writing my own classloader to deal with the
issue. That hasn't gotten me very far (I've inserted my own classloader
that forces all class loads to happen on a single threading context, but
it's so slow I haven't bothered to test it with my real application).
Are the any fixes or work arounds? Any guidelines I can follow to
mitigate the problem. A lot the time my application is completely
assembled at runtime via reflection. This deadlock has recently turn my
application into a very nice doorstop most of the time.
Thanks,
Kirby
|
|
|
| Re: ClassLoader deadlock issues [message #79819 is a reply to message #74847] |
Fri, 22 December 2006 12:29  |
| Eclipse User |
|
|
|
Hi Kirby,
There was some discussion and ultimately some resoltion for these sorts of
issues not so long ago in a bug report.
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=121737
-Simon
"Kirby C. Bohling" <kirby.bohling@gmail.com> wrote in message
news:egp0j6$k7s$1@utils.eclipse.org...
> All,
>
> (I sent sent this same message to equinox-dev, sorry if they are the same
> thru a news-to-mail gateway).
>
> I've been working with Eclipse, and use Buddy Loaders fairly extensively
> so that core plug-ins can construct objects from their child plug-ins at
> runtime.
>
> The ClassLoader segmentation is causing me lots and lots of issues w/
> BuddyLoaders and the deadlock.
>
> I've seen this thread:
> http://dev.eclipse.org/mhonarc/lists/equinox-dev/msg01354.ht ml
>
> This pretty much exactly covers my case. Are there any workarounds or
> mitigations? I use object serialization for over the wire communication
> and spring both of which use Global buddy loaders. Currently my
> application deadlocks 9 times out of 10.
>
> I've been looking into writing my own classloader to deal with the issue.
> That hasn't gotten me very far (I've inserted my own classloader that
> forces all class loads to happen on a single threading context, but it's
> so slow I haven't bothered to test it with my real application). Are the
> any fixes or work arounds? Any guidelines I can follow to mitigate the
> problem. A lot the time my application is completely assembled at runtime
> via reflection. This deadlock has recently turn my application into a
> very nice doorstop most of the time.
>
> Thanks,
> Kirby
|
|
|
Powered by
FUDForum. Page generated in 0.04958 seconds
Home