April 2008 - jboss-user - Jboss List Archives

[JBoss Cache: Core Edition] - Re: Need helps with initial state transfer in production

by manik.surtani＠jboss.com

Hmm, I don't see the part where | org.jboss.cache.CacheException: Initial state transfer failed: Channel.getState() returned false | appears in your debug log? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144099#4144099 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144099

18 years, 2 months

1
0
0 / 0

[JBoss Cache: Core Edition] - Re: Expiring elements after restarting cache

by manik.surtani＠jboss.com

It should evict stuff that has been reloaded as well. Do you only see this problem with the FCL, or with other cache loaders as well? Do you have a unit test that recreates this? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144098#4144098 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144098

18 years, 2 months

1
0
0 / 0

[JBoss Cache: Core Edition] - Re: Cache modified time not updated in a clustered environme

by manik.surtani＠jboss.com

Another not-too-elegant approach would be to start a transaction and read the node, then mark the node as in use. This way, 1) local evictions won't remove your node because you have marked it as in use. 2) remote evictions won't remove your node since your tx has a lock on it. Remote evictions will in fact fail and be put on a recycle queue if you are using synchronous replication, or fail quietly if you are using async replication. When you are done with your update, call unmarkNodeCurrentlyInUse() and commit your transaction to release locks. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144095#4144095 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144095

18 years, 2 months

1
0
0 / 0

[JBoss Cache: Core Edition] - Re: Cache modified time not updated in a clustered environme

by manik.surtani＠jboss.com

All eviction logic, queues and timers are local to a single cache instance and is not shared across a cluster. Marking a node as in use, also, only affects a single cache instance. Since you have your own eviction policy that actually does a remove instead of an evict, that's where you may have a problem. Perhaps using your own RPC call across a cluster to have all caches call markNodeCurrentlyInUse()? Why do you need a custom eviction policy that does a remove anyway, why not just a standard eviction policy? If you don't use a cache loader it has almost the same effect as a remove, and won't affect the entire cluster. Oh and FYI this API call is available in 1.4.X - you just need to get a hold of the TreeCache, not just the TreeCacheMBean, and call getEvictionRegionManager(). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144094#4144094 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144094

18 years, 2 months

1
0
0 / 0

[JBoss Cache: Core Edition] - Re: How to know the size of the Cache

by manik.surtani＠jboss.com

Size meaning, number of nodes? Or number of attributes per node? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144093#4144093 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144093

18 years, 2 months

1
0
0 / 0

[JBoss Cache: Core Edition] - Re: A basic question about concurrency

by manik.surtani＠jboss.com

You could try READ_UNCOMMITTED, but you ought to make sure you thoroughly stress test things in a test environment first. :-) It just may be that your access pattern won't cause any problems, but there are no guarantees here. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144092#4144092 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144092

18 years, 2 months

1
0
0 / 0

[JBoss Cache: Core Edition] - Re: custom method to get size of nodes in cache evicts some

by manik.surtani＠jboss.com

It wouldn't be causing the node to be evicted - the EvictionEvent just marks an event for the eviction thread to process, which, depending on your algorithm, may remove the node from the eviction queue, e.g., if it has been used recently and you are using a LRU algorithm. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144091#4144091 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144091

18 years, 2 months

1
0
0 / 0

[JBoss jBPM] - Re: Contributing a New Document to JBPM Community

by gosub33

I don't know how you would do it, but please! The more documentation the better. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144079#4144079 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144079

18 years, 2 months

1
0
0 / 0

[JBossWS] - running jax-ws web service on jboss 4.0.1

by niwa_java

Hi, We have a J2EE application deployed on JBoss4.0.1. I need to call a 'document' style web service from this application. I have the client classes but I cannot access the web service. Do I need to install any jboss ws patch? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144076#4144076 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144076

18 years, 2 months

1
0
0 / 0

[JBoss Cache: Core Edition] - Re: Cache server(s) and client(s)?

by genman

Also: http://www.jboss.org/file-access/default/members/jbosscache/freezone/docs... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4144075#4144075 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4144075

18 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user April 2008