March 2009 - jbosscache-issues - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-1488) Please add more equivalents of operations on Node to Cache interface

by Krzysztof Sobolewski (JIRA)

Please add more equivalents of operations on Node to Cache interface -------------------------------------------------------------------- Key: JBCACHE-1488 URL: https://jira.jboss.org/jira/browse/JBCACHE-1488 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 3.1.0.GA Reporter: Krzysztof Sobolewski Assignee: Manik Surtani There's a slight asymmetry between operations on Node and equivalent convenience operations on Cache, like lack of getChildren(Fqn), addChild(Fqn) etc.. The convenience operations are desirable because of their atomicity, so I think there should be equivalents for as many operations on Node as possible. Moreover, some of them are in CacheSPI that I think should be present in Cache interface instead. Namely: Set<Object> getChildrenNames(Fqn fqn); and its convenience variant Set<String> getChildrenNames(String fqn); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-1490) Cache.evict(Fqn.ROOT, true) does not work

by Krzysztof Sobolewski (JIRA)

Cache.evict(Fqn.ROOT, true) does not work ----------------------------------------- Key: JBCACHE-1490 URL: https://jira.jboss.org/jira/browse/JBCACHE-1490 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Eviction Affects Versions: 3.0.3.GA Reporter: Krzysztof Sobolewski Assignee: Manik Surtani Eviction of all nodes via a single call to recursive eviction of root node does not evict enything (maybe apart from the root itself): Cache.evict(Fqn.ROOT, true); The attached test case illustrates 3 scenarios: * Nodes are evicted (non-recursively) one by one: OK * Nodes are evicted (recursively) by common parent (not root): OK * Nodes are evicted (recursively) by root: FAIL -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-1491) JBC 1.4.x cache wrapper not reading data in cache

by Galder Zamarreno (JIRA)

JBC 1.4.x cache wrapper not reading data in cache ------------------------------------------------- Key: JBCACHE-1491 URL: https://jira.jboss.org/jira/browse/JBCACHE-1491 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: CacheBenchFwk Reporter: Galder Zamarreno Assignee: Galder Zamarreno Eventually figured out why no matter how I did it, the benchmark for JBC 1.4.x did not work: org.cachebench.cachewrappers.JBossCacheWrapper inside jbosscache-1.4.1 shows: public Object getReplicatedData(List<String> l, String key) { return null; } So, replication works but checking whether the data has been replicated has not been implemented!! I'll get it fixed. Where do we fill JIRAs for the cache benchmark framework? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Resolved: (JBCACHE-1245) Visual admin tool for buddy replication

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-1245?page=com.atlassian.jira.p... ] Manik Surtani resolved JBCACHE-1245. ------------------------------------ Fix Version/s: (was: 3.2.0.GA) Resolution: Won't Fix > Visual admin tool for buddy replication > --------------------------------------- > > Key: JBCACHE-1245 > URL: https://jira.jboss.org/jira/browse/JBCACHE-1245 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Manik Surtani > Assignee: Manik Surtani > > Perhaps something that works entirely off JMX, and then both a command-line and GUI tool that can visualise/operate on it. > In terms of buddy info, this could be textual information, perhaps even XML. In terms of a GUI tool to visualise this information, this can be put together using Swing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBCACHE-711) Replication eats out exception on the remote node

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-711?page=com.atlassian.jira.pl... ] Manik Surtani resolved JBCACHE-711. ----------------------------------- Fix Version/s: (was: 3.2.0.GA) Resolution: Won't Fix > Replication eats out exception on the remote node > ------------------------------------------------- > > Key: JBCACHE-711 > URL: https://jira.jboss.org/jira/browse/JBCACHE-711 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Replication > Affects Versions: 1.4.0.GA > Reporter: Ben Wang > Assignee: Manik Surtani > > I have seen this on the 1.4 release on ejb3. Here is what happens. Two nodes replication. When the remote node throws an exception like NPE, the originating node will display with NonSerializableException. I don't a unit test for this but I think it should be easy to reproduce. > 21:51:32,490 INFO [TxInterceptor] There was a problem handling this request > java.io.NotSerializableException: RpcDispatcher returned a null. This is most often caused by args for _replicate(_put(null, /testNestedStateful/5c4o1e-xzw6rx-eq1m0jea-1-eq1m4tna-5, bean, org.jboss.ejb3.stateful.ProxiedStatefulBeanContext@7b8be7, true)) not being serializable. > at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4166) > at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4113) > at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:4214) > at org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall(BaseRpcInterceptor.java:110) > at org.jboss.cache.interceptors.BaseRpcInterceptor.replicateCall(BaseRpcInterceptor.java:88) > at org.jboss.cache.interceptors.ReplicationInterceptor.handleReplicatedMethod(ReplicationInterceptor.java:114) > at org.jboss.cache.interceptors.ReplicationInterceptor.invoke(ReplicationInterceptor.java:83) > at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68) > at org.jboss.cache.interceptors.PassivationInterceptor.invoke(PassivationInterceptor.java:69) > at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68) > at org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterce -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBCACHE-70) Make JBossCache an XAResource

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-70?page=com.atlassian.jira.plu... ] Manik Surtani resolved JBCACHE-70. ---------------------------------- Fix Version/s: (was: 3.2.0.GA) Resolution: Won't Fix > Make JBossCache an XAResource > ----------------------------- > > Key: JBCACHE-70 > URL: https://jira.jboss.org/jira/browse/JBCACHE-70 > Project: JBoss Cache > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Manik Surtani > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBCACHE-1306) Search interface for JBoss Cache

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-1306?page=com.atlassian.jira.p... ] Manik Surtani resolved JBCACHE-1306. ------------------------------------ Fix Version/s: (was: 3.2.0.GA) Resolution: Won't Fix > Search interface for JBoss Cache > -------------------------------- > > Key: JBCACHE-1306 > URL: https://jira.jboss.org/jira/browse/JBCACHE-1306 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: SearchableCache > Reporter: Manik Surtani > Assignee: Navin Surtani > Original Estimate: 4 weeks > Remaining Estimate: 4 weeks > > Could involve either Hibernate Search or JOFTI. > Re: Hibernate Search: > "HS uses Hibernate's event model to detect changes in objects and updates it's index accordingly. The interface with HS involves search terms which uses the index to extract a set of PKs, which HS uses with Hibernate to return a set of Objects. According to Emmanuel, all that needs to be done is to change HS to use an interface rather than Hibernate's event model directly, and Hibernate's querying directly, and write an implementation that uses JBC's notifications and a cache access instead of the Hibernate counterparts." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBCACHE-1306) Search interface for JBoss Cache

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-1306?page=com.atlassian.jira.p... ] Manik Surtani commented on JBCACHE-1306: ---------------------------------------- Already available in JBoss Cache - Searchable http://www.jboss.org/community/docs/DOC-10286 > Search interface for JBoss Cache > -------------------------------- > > Key: JBCACHE-1306 > URL: https://jira.jboss.org/jira/browse/JBCACHE-1306 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: SearchableCache > Reporter: Manik Surtani > Assignee: Navin Surtani > Original Estimate: 4 weeks > Remaining Estimate: 4 weeks > > Could involve either Hibernate Search or JOFTI. > Re: Hibernate Search: > "HS uses Hibernate's event model to detect changes in objects and updates it's index accordingly. The interface with HS involves search terms which uses the index to extract a set of PKs, which HS uses with Hibernate to return a set of Objects. According to Emmanuel, all that needs to be done is to change HS to use an interface rather than Hibernate's event model directly, and Hibernate's querying directly, and write an implementation that uses JBC's notifications and a cache access instead of the Hibernate counterparts." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBCACHE-60) Partitioned Cache

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-60?page=com.atlassian.jira.plu... ] Manik Surtani commented on JBCACHE-60: -------------------------------------- See HORIZON-22 for details > Partitioned Cache > ----------------- > > Key: JBCACHE-60 > URL: https://jira.jboss.org/jira/browse/JBCACHE-60 > Project: JBoss Cache > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Manik Surtani > Original Estimate: 10 weeks > Remaining Estimate: 10 weeks > > - Distributed load across multiple nodes in a cluster > - No replication/redundancy -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBCACHE-60) Partitioned Cache

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/JBCACHE-60?page=com.atlassian.jira.plu... ] Manik Surtani resolved JBCACHE-60. ---------------------------------- Fix Version/s: (was: 3.2.0.GA) Resolution: Won't Fix > Partitioned Cache > ----------------- > > Key: JBCACHE-60 > URL: https://jira.jboss.org/jira/browse/JBCACHE-60 > Project: JBoss Cache > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Manik Surtani > Original Estimate: 10 weeks > Remaining Estimate: 10 weeks > > - Distributed load across multiple nodes in a cluster > - No replication/redundancy -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosscache-issues March 2009