Hi, I have taken a look at the fix and have talked to Bill Burke about it.
Unfortunately, the current JBossAop instrumentation is too expensive to skip
field interception based on method call stack. So we will need to push this fix
to 1.3 release when JBossAop can optimize that part.
To
This is a bug. No, we never have a test case with a composite value object key.
I will fix it in release 1.2 (hopefully the next couple days).
Thanks,
-Ben
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3854692#3854692
Reply to the post :
Awesome, thanks Ben.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3854702#3854702
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3854702
---
This SF.Net email is
Some more information. I'm running this test with JBossCache 1.1, but have also
tried the latest HEAD revision with the same results. Here's a stack trace from
1.1 that shows the loop.
| checkCacheConsistency():142, org.jboss.cache.aop.CacheInterceptor
| invoke():88,
