April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-971) Eviction policy based on adaptive replacement

by Manik Surtani (JIRA)

Eviction policy based on adaptive replacement --------------------------------------------- Key: JBCACHE-971 URL: http://jira.jboss.com/jira/browse/JBCACHE-971 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.1.0.GA Quote from Mircea Markus: There is an eviction policy algorithm more efficient than LRU (which I found quite popular) - Adaptive Replacement Policy. The basic idea is to not rely only on the time of last access to the node, but also on the number of time(frequency) a given node was accessed. Here it is a nice description of how it works: http://en.wikipedia.org/wiki/Adaptive_Replacement_Cache. -- 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

18 years, 1 month

2
10
0 / 0

[JBoss JIRA] Created: (JBREM-677) Compression marshalling fails intermittently.

by Ron Sigal (JIRA)

Compression marshalling fails intermittently. --------------------------------------------- Key: JBREM-677 URL: http://jira.jboss.com/jira/browse/JBREM-677 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Beta2 (Boon) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.2.0.Beta2 (Boon) When used with EJB's, CompressingUnMarshaller intermittently throws java.io.IOException: Not in GZIP format. -- 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

18 years, 1 month

3
9
0 / 0

[JBoss JIRA] Created: (JBCACHE-968) Test on 80 node cluster

by Manik Surtani (JIRA)

Test on 80 node cluster ----------------------- Key: JBCACHE-968 URL: http://jira.jboss.com/jira/browse/JBCACHE-968 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.0.0.GA Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.0.GA -- 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

18 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (JBCACHE-1024) Move component construction out of Cache into Configuration to allow for better configurability

by Elias Ross (JIRA)

Move component construction out of Cache into Configuration to allow for better configurability ----------------------------------------------------------------------------------------------- Key: JBCACHE-1024 URL: http://jira.jboss.com/jira/browse/JBCACHE-1024 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Elias Ross Assigned To: Manik Surtani There's a lot of logic embedded in CacheImpl.start() and create() as to what specific object instances are created. For example, the JGroups Channel, or the InterceptorChainFactory are directly constructed here and users have no control on this. A bunch of other objects are also created based on class names and whatnot; these are configurable to some extent but why does the CacheImpl need to know how to build these? What really should be done is allow the Configuration class to play the role as factory class, and take out all factory details from the Cache itself. -- 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

18 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-1011) memory based eviction policy

by Mircea Markus (JIRA)

memory based eviction policy ---------------------------- Key: JBCACHE-1011 URL: http://jira.jboss.com/jira/browse/JBCACHE-1011 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 2.2.0.GA Reporter: Mircea Markus Assigned To: Manik Surtani Fix For: 2.1.0.GA As with Java5 java offers support for determining the size of objects. An memory based eviction policy can be written for this java version only. The basic idea is to let the user to specify the amount of memory he wants to use. -- 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

18 years, 1 month

3
9
0 / 0

[JBoss JIRA] Created: (JBCACHE-816) Create a CacheProxy to allow cache replication across WANs

by Manik Surtani (JIRA)

Create a CacheProxy to allow cache replication across WANs ---------------------------------------------------------- Key: JBCACHE-816 URL: http://jira.jboss.com/jira/browse/JBCACHE-816 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering Affects Versions: 1.4.0, 2.0.0 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.3.0 This has to do with multiple JBoss Cache clusters deployed on LANs as islands, requiring a bridge between such islands. An ideal use case is where a cluster spans multiple data centres and would need to replicate across a WAN. The ideal strategy would be to allow for async bridging, since most calls would be colocated to a single LAN, but may fail over to a remote LAN (pretty much the same idea of async repl within a LAN, except that now we treat an entire LAN as a host. Sort of a meta-cluster). For more details and some brainstorming ideas, see: http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheAcrossDataCentres -- 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

18 years, 1 month

3
4
0 / 0

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

by Ben Wang (JIRA)

Replication eats out exception on the remote node ------------------------------------------------- Key: JBCACHE-711 URL: http://jira.jboss.com/jira/browse/JBCACHE-711 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: Replication Affects Versions: 1.4.0 Reporter: Ben Wang Assigned To: Manik Surtani Fix For: 2.0.0 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: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (BPEL-249) create ws stack integration subprojects

by Alejandro Guizar (JIRA)

create ws stack integration subprojects --------------------------------------- Key: BPEL-249 URL: http://jira.jboss.com/jira/browse/BPEL-249 Project: JBoss jBPM BPEL Issue Type: Task Security Level: Public (Everyone can see) Components: Engine Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1.GA -- 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

18 years, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (BPEL-251) cover document-style bindings in service generation tool

by Alejandro Guizar (JIRA)

cover document-style bindings in service generation tool -------------------------------------------------------- Key: BPEL-251 URL: http://jira.jboss.com/jira/browse/BPEL-251 Project: JBoss jBPM BPEL Issue Type: Task Security Level: Public (Everyone can see) Components: Engine Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1 GA Enhance the service generation tool to cover the document style when generating a binding element. According to the WS-I Basic Profile, "a document-literal binding MUST refer only to wsdl:part element(s) that have been defined using the element attribute". Port types that refer to any part defined using the type attribute generate RPC bindings. -- 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

18 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (BPEL-243) throw selectionFailure when copying from an element with xsi:nil=true

by Alejandro Guizar (JIRA)

throw selectionFailure when copying from an element with xsi:nil=true --------------------------------------------------------------------- Key: BPEL-243 URL: http://jira.jboss.com/jira/browse/BPEL-243 Project: JBoss jBPM BPEL Issue Type: Task Security Level: Public (Everyone can see) Components: Engine Affects Versions: jBPM BPEL 1.1 beta 3 Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1.GA -- 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

18 years, 1 month

1
2
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 April 2007