[
http://jira.jboss.com/jira/browse/JBCACHE-37?page=comments#action_12315103 ]
Andrew May commented on JBCACHE-37:
---
Thanks, that's one thing I hadn't tried (I hadn't seen that JBoss-AOP 1.1 had
been released) - I had tried building the AOP/aspect
[
http://jira.jboss.com/jira/browse/JBCACHE-37?page=comments#action_12315075 ]
Andrew May commented on JBCACHE-37:
---
I tried running my original test against jboss-head (I wasn't sure how to run
the test case you had checked in) and the stack
[
http://jira.jboss.com/jira/browse/JBCACHE-37?page=comments#action_12315094 ]
Ben Wang commented on JBCACHE-37:
-
Andrew,
I have backported my unit test case (build.sh one-test
-Dtest=org.jboss.test.cache.test.aop.CacheObjectMBeanUnitTestCase, with
[
http://jira.jboss.com/jira/browse/JBCACHE-37?page=comments#action_12315062 ]
Ben Wang commented on JBCACHE-37:
-
Andrew,
I have checked in a CacheObjectMBeanUnitTestCase under
jboss-head/testsuite/src/main/org/jboss/test/cache/test/aop directory. I
[
http://jira.jboss.com/jira/browse/JBCACHE-37?page=comments#action_12314997 ]
Andrew May commented on JBCACHE-37:
---
Firstly, could I ask whether this is still being looked at in light of my
previous comment? If so, could you re-open the bug.
I've
[
http://jira.jboss.com/jira/browse/JBCACHE-37?page=comments#action_12314936 ]
Andrew May commented on JBCACHE-37:
---
Getting the cache from the MBean doesn't seem to make any difference. I'm still
getting the same stack overflow.
I've changed
[
http://jira.jboss.com/jira/browse/JBCACHE-37?page=comments#action_12314920 ]
Ben Wang commented on JBCACHE-37:
-
Andrew,
I was able to reprouce it in 4.0 tree. I think the problem is in jndi binding.
However, in the upcoming cache 1.2.1 release,
[
http://jira.jboss.com/jira/browse/JBCACHE-37?page=comments#action_12314755 ]
Ben Wang commented on JBCACHE-37:
-
Andres,
I have tried to produce this problem using standalone but without success. So
looks like the problem is when the it deploys
