September 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Resolved: (JBCACHE-675) Test case failure RecursiveRefTest

by Ben Wang (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-675?page=all ] Ben Wang resolved JBCACHE-675. ------------------------------ Resolution: Done > Test case failure RecursiveRefTest > ---------------------------------- > > Key: JBCACHE-675 > URL: http://jira.jboss.com/jira/browse/JBCACHE-675 > Project: JBoss Cache > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: PojoCache > Reporter: Ben Wang > Assigned To: Ben Wang > Fix For: 2.0.0 > > > The fix to require key as Serialiable cuases this test case: > org.jboss.cache.pojo.RecrusiveRefTest to fail because in there it is put(valueId, valueObject) where valueId is a PojoCacheable object (but not Serializable). It is PojoCacheable becuase valueObject also uses valueId as the primary key. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBCACHE-675) Test case failure RecursiveRefTest

by Ben Wang (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-675?page=comments#action_12343447 ] Ben Wang commented on JBCACHE-675: ---------------------------------- This test passes now in 2.0. Should also update the documentation. > Test case failure RecursiveRefTest > ---------------------------------- > > Key: JBCACHE-675 > URL: http://jira.jboss.com/jira/browse/JBCACHE-675 > Project: JBoss Cache > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: PojoCache > Reporter: Ben Wang > Assigned To: Ben Wang > Fix For: 2.0.0 > > > The fix to require key as Serialiable cuases this test case: > org.jboss.cache.pojo.RecrusiveRefTest to fail because in there it is put(valueId, valueObject) where valueId is a PojoCacheable object (but not Serializable). It is PojoCacheable becuase valueObject also uses valueId as the primary key. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-675) Test case failure RecursiveRefTest

by Ben Wang (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-675?page=all ] Ben Wang updated JBCACHE-675: ----------------------------- Affects: [Documentation (Ref Guide, User Guide, etc.)] Assignee: Ben Wang (was: Scott Marlow) > Test case failure RecursiveRefTest > ---------------------------------- > > Key: JBCACHE-675 > URL: http://jira.jboss.com/jira/browse/JBCACHE-675 > Project: JBoss Cache > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: PojoCache > Reporter: Ben Wang > Assigned To: Ben Wang > Fix For: 2.0.0 > > > The fix to require key as Serialiable cuases this test case: > org.jboss.cache.pojo.RecrusiveRefTest to fail because in there it is put(valueId, valueObject) where valueId is a PojoCacheable object (but not Serializable). It is PojoCacheable becuase valueObject also uses valueId as the primary key. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBCACHE-110) PojoCache overriding toString or hashCode can trigger stack overflow

by Ben Wang (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-110?page=all ] Ben Wang resolved JBCACHE-110. ------------------------------ Resolution: Done > PojoCache overriding toString or hashCode can trigger stack overflow > -------------------------------------------------------------------- > > Key: JBCACHE-110 > URL: http://jira.jboss.com/jira/browse/JBCACHE-110 > Project: JBoss Cache > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: PojoCache > Affects Versions: 1.2 > Reporter: Ben Wang > Assigned To: Ben Wang > Fix For: 2.0.0 > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > In TreeCacheAOp, certain over-riding will trigger stack overflow. THis is becuase of the recursive field interecption that results. Solution is to detect the field recusion. > Kabir has done it in: > org.jboss.aspects.dbc.DesignByContractAspect -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBCACHE-110) PojoCache overriding toString or hashCode can trigger stack overflow

by Ben Wang (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-110?page=comments#action_12343446 ] Ben Wang commented on JBCACHE-110: ---------------------------------- Currently, I have used an annotation @Reentrant and the following declaration in jboss-aop.xml:  <bind pointcut="execution(* @org.jboss.cache.pojo.annotation.Reentrant->toString())"> <interceptor-ref name="Reentrant"/> </bind>  <interceptor name="Reentrant" class="org.jboss.cache.pojo.interceptors.MethodReentrancyStopperInterceptor" scope="PER_INSTANCE"/> The annotation currently applies only to List, Set, and Map impl now. > PojoCache overriding toString or hashCode can trigger stack overflow > -------------------------------------------------------------------- > > Key: JBCACHE-110 > URL: http://jira.jboss.com/jira/browse/JBCACHE-110 > Project: JBoss Cache > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: PojoCache > Affects Versions: 1.2 > Reporter: Ben Wang > Assigned To: Ben Wang > Fix For: 2.0.0 > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > In TreeCacheAOp, certain over-riding will trigger stack overflow. THis is becuase of the recursive field interecption that results. Solution is to detect the field recusion. > Kabir has done it in: > org.jboss.aspects.dbc.DesignByContractAspect -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-110) PojoCache overriding toString or hashCode can trigger stack overflow

by Ben Wang (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-110?page=all ] Ben Wang updated JBCACHE-110: ----------------------------- Affects: [Documentation (Ref Guide, User Guide, etc.)] Complexity: High > PojoCache overriding toString or hashCode can trigger stack overflow > -------------------------------------------------------------------- > > Key: JBCACHE-110 > URL: http://jira.jboss.com/jira/browse/JBCACHE-110 > Project: JBoss Cache > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: PojoCache > Affects Versions: 1.2 > Reporter: Ben Wang > Assigned To: Ben Wang > Fix For: 2.0.0 > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > In TreeCacheAOp, certain over-riding will trigger stack overflow. THis is becuase of the recursive field interecption that results. Solution is to detect the field recusion. > Kabir has done it in: > org.jboss.aspects.dbc.DesignByContractAspect -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-676) PojoCache map implementation needs to handle the case where key is PojoCacheable

by Ben Wang (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-676?page=all ] Ben Wang updated JBCACHE-676: ----------------------------- Affects: [Documentation (Ref Guide, User Guide, etc.)] > PojoCache map implementation needs to handle the case where key is PojoCacheable > -------------------------------------------------------------------------------- > > Key: JBCACHE-676 > URL: http://jira.jboss.com/jira/browse/JBCACHE-676 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Components: PojoCache > Reporter: Ben Wang > Assigned To: Ben Wang > Fix For: 2.0.0 > > > This is illustrated in org.jboss.cache.pojo.RecrusiveRefTest where we have map.put(valueId, valueObject) where both are PojoCacheable and valueId also embeded in valueObject. Therefore, if we treat valueId just as a Serializable, replication will cause the object reference split in valueObject (becuase in valueObject, valueId is treated by PojoCache). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBCACHE-676) PojoCache map implementation needs to handle the case where key is PojoCacheable

by Ben Wang (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-676?page=all ] Ben Wang resolved JBCACHE-676. ------------------------------ Resolution: Done The test passes now in 2.0. Still need documentation of the effect of Id is Serializable only though. > PojoCache map implementation needs to handle the case where key is PojoCacheable > -------------------------------------------------------------------------------- > > Key: JBCACHE-676 > URL: http://jira.jboss.com/jira/browse/JBCACHE-676 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Components: PojoCache > Reporter: Ben Wang > Assigned To: Ben Wang > Fix For: 2.0.0 > > > This is illustrated in org.jboss.cache.pojo.RecrusiveRefTest where we have map.put(valueId, valueObject) where both are PojoCacheable and valueId also embeded in valueObject. Therefore, if we treat valueId just as a Serializable, replication will cause the object reference split in valueObject (becuase in valueObject, valueId is treated by PojoCache). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-3507) Add ability to toggle the MultiplexerStack between UDP- and TCP-based versions

by Brian Stansberry (JIRA)

Add ability to toggle the MultiplexerStack between UDP- and TCP-based versions ------------------------------------------------------------------------------ Key: JBAS-3507 URL: http://jira.jboss.com/jira/browse/JBAS-3507 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering, Test Suite Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta Need Branch_4_0-style "tests-clustering-all-stacks" tests, but simpler to implement due to ability to change the MultiplexerStack attribute. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-3662) Add TCP_NIO tests to tests-clustering-all-stacks

by Brian Stansberry (JIRA)

Add TCP_NIO tests to tests-clustering-all-stacks ------------------------------------------------ Key: JBAS-3662 URL: http://jira.jboss.com/jira/browse/JBAS-3662 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering, Test Suite Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta The mulitiplexer-stacks.xml file will have UDP, TCP and TCP_NIO configs. Testsuite should excercise all 3, not just UDP and TCP. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

19 years, 10 months

1
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2006