Does this mean you can reproduce the CCE reliably?
--jason
On Friday 31 May 2002 06:01 am, Dave Smith wrote:
> A little more digging finds that the mbean uses a thrid party jar that
> is using the bad Class.forName to load classes. Should this matter? If
> the mbean is instaniating the object w
> Scott Stark
> Chief Technology Officer
> JBoss Group, LLC
>
> - Original Message -
> From: "Dave Smith" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, May 31, 2002 6:01 AM
> Subject: Re: [JBoss-d
- Original Message -
From: "Dave Smith" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, May 31, 2002 6:01 AM
Subject: Re: [JBoss-dev] java.lang.ClassCircularityError
> A little more digging finds that the mbean uses a thrid party jar that
> is using t
A little more digging finds that the mbean uses a thrid party jar that
is using the bad Class.forName to load classes. Should this matter? If
the mbean is instaniating the object would it's class loader not be the
UCL? Any thoughts on where to starting looking to solve this problem?
Can not touch
I'm Using Branch_3_0 latest .
Firstly my initial test of the locking code seems to work. I have a
couple of other machines to test it on, I'll keep you posted ...
If I have two mbeans that are of the same class in an .xml file I get a
java.lang.ClassCircularityError. So ...
jboss.j2ee:se
