: Re: Strange IllegalAccessError w/FastClassByCGLIB class
Jason, can you try adding an ejbRemove method directly to the class
and see if the problem goes away?
-dain
On Feb 13, 2006, at 4:56 PM, Aaron Mulder wrote:
It may be the inheritance causing problems rather than the CL, as
well. You know
On 2/13/06, Jason Dillon [EMAIL PROTECTED] wrote:
I will look at it more... I'm not familiar with the proxy gen in G
yet... but a race condition sounds likely since this problem only
shows up in multithreaded concurrency test.
I'm not convinced it's a proxy error. I mean, clearly
On Feb 13, 2006, at 4:43 AM, Aaron Mulder wrote:
On 2/13/06, Jason Dillon [EMAIL PROTECTED] wrote:
I will look at it more... I'm not familiar with the proxy gen in G
yet... but a race condition sounds likely since this problem only
shows up in multithreaded concurrency test.
I'm not
MerchantViewServiceBean does not have its own ejbRemote(), it picks it
up from AbstractStatelessSessionBean (from app), which picks it up
from AbstractStatelessSessionBean (from spring).
Could be a CL problem... the application is using Spring 1.1.4, which
is included in the EAR.
In my plan I
It may be the inheritance causing problems rather than the CL, as
well. You know, maybe we try calling ejbRemove on your bean class
even though it's declared on the superclass or something. If the CL
manipulations don't work out, we can follow that path.
As far as the hidden classes, we
Jason, can you try adding an ejbRemove method directly to the class
and see if the problem goes away?
-dain
On Feb 13, 2006, at 4:56 PM, Aaron Mulder wrote:
It may be the inheritance causing problems rather than the CL, as
well. You know, maybe we try calling ejbRemove on your bean class
This did appear to fix the problem No more IAE.
--jason
-Original Message-
From: Dain Sundstrom [EMAIL PROTECTED]
Date: Mon, 13 Feb 2006 17:04:01
To:dev@geronimo.apache.org
Subject: Re: Strange IllegalAccessError w/FastClassByCGLIB class
Jason, can you try adding an ejbRemove
I don't, but have you looked up what it is in StatelessInstanceFactory
that generates that message? Perhaps we have a race condition?
Aaron
On 2/12/06, Jason Dillon [EMAIL PROTECTED] wrote:
Anyone have any idea why this happens?
--jason
On Feb 10, 2006, at 5:03 PM, Jason Dillon wrote:
I will look at it more... I'm not familiar with the proxy gen in G
yet... but a race condition sounds likely since this problem only
shows up in multithreaded concurrency test.
Is there an existing test for G somewhere? I can commit my work on
JMeter components if that would be helpful.
