They will respond that you should not tweak the
classloading delegation as we do such that mutual dependencies occur ...
So we must first have a good advocate there.
CGJ
-Ursprüngliche Nachricht-
Von: Ignacio Coloma [mailto:[EMAIL PROTECTED]]
Gesendet: Freitag, 5. Oktober 2001 00:21
Jung , Dr. Christoph wrote:
IMHO, your nice patch has partly solved the problem, i.e., the issue that
Sacha was noticing with the patch.jar NOT;-) applied. And even without
patch.jar, it should have greatly diminished the deadlock possibilities ...
But nevertheless, I could imagine a
Ignacio Coloma wrote:
You can document it as a bug on Sun. If it really is, they can confirm it.
Only take care of NOT SPEAKING ABOUT any imaginary patch :)
Sun doesn't mind patches to the java.* libraries when
commmitting bug reports.
The also dont mind it for the purpose of internal
If the deadlock between these two classes can occur, CL1
must use CL2 to load C2, and CL2 must use CL1 to load C1.
But that would mean that CL2 is a parent of CL1, and CL1
is a parent of CL2. I believe that circular class loader
parentage is impossible in Java.
But that is exactly the central
Jung , Dr. Christoph wrote:
If the deadlock between these two classes can occur, CL1
must use CL2 to load C2, and CL2 must use CL1 to load C1.
But that would mean that CL2 is a parent of CL1, and CL1
is a parent of CL2. I believe that circular class loader
parentage is impossible in Java.
-Ursprüngliche Nachricht-
Von: Ole Husgaard [mailto:[EMAIL PROTECTED]]
Gesendet: Freitag, 5. Oktober 2001 17:56
An: Jboss-Development (E-Mail)
Betreff: Re: AW: AW: [JBoss-dev] The rabbit has a bug in its pelt:
org.jboss.system.URLClassLoader
Sorry, I still do not see how this is
[ Forwarding to the list. D*mn missing reply-to. ]
Jung , Dr. Christoph wrote:
- org.jboss.system.URLClassLoader.loadClass(String, boolean)
delegates directly to the ServiceLibraries _without_ obtaining
an instance lock.
that is true, but remember that
Hi Ole others,
IMHO, your nice patch has partly solved the problem, i.e., the issue that
Sacha was noticing with the patch.jar NOT;-) applied. And even without
patch.jar, it should have greatly diminished the deadlock possibilities ...
But nevertheless, I could imagine a scenario, where a
You can document it as a bug on Sun. If it really is, they can confirm it.
Only take care of NOT SPEAKING ABOUT any imaginary patch :)
-Mensaje original-
De: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]En nombre de Jung
, Dr. Christoph
Enviado el: jueves, 04 de octubre de 2001 9:06
Hi,
I think this bug is the reason for the problems
we see with the automated tests.
Here the test count sometimes gets very low due
to the tests timing out.
Looking into this is hard, as it seems to change
with every run, but one thing seems to be common:
The deployer stops working, and the
Hey Ole,
as I said I have a small tool written with JDI that will tell you who is
holding what and who is waiting (so in the wait for monitor entry you'll
know who is the monitor)
If you wanna play, just tell me ;)
Simon
-Original Message-
From: Ole Husgaard [mailto:[EMAIL
we though you were dead, totally assimilated...
marcf
|-Original Message-
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of
|Bordet, Simone
|Sent: Tuesday, October 02, 2001 12:53 PM
|To: JBoss Development Mailing List (E-mail)
|Subject: RE: [JBoss-dev] The rabbit has a
Jung , Dr. Christoph wrote:
I must correct myself! We have a principle problem, unfortunately, for which
I do not
have an immediate answer right now:
Actually, instead of synchronized(classLoaders) in ServiceLibraries, there
would be the need
to *atomically* synchronize on all instances
Hi there (got currently huge problems with our firewall, prevents a proper
bug report :-(
Sascha has noticed that the RH startup process sometimes deadlocks in the
new classloading scheme especially when he is starting up JavaGroups and his
HA MBeans.
My hypothesis (see snippets from his
I must correct myself! We have a principle problem, unfortunately, for which
I do not
have an immediate answer right now:
Actually, instead of synchronized(classLoaders) in ServiceLibraries, there
would be the need
to *atomically* synchronize on all instances of the set in order not to
|(BTW: If somebody would offer Voodoo-puppets of SUN developers in the
|jboss-store, you could make a fortune! If you would additionally provide
|JBoss-needles, you could even make a bigger one!)
LOL ^ 10
listen I really want to finish the website but will try to come back to this
soon (like
16 matches
Mail list logo
