We are getting the following error in our log all over the place... but the cache
still seems to work okay. Is it an expected exception, something we are causing, or a
bug to be logged?
2004-04-21 14:46:28,474 DEBUG- Node.acquireWriteLock - acquired WL: fqn=/,
owner=172.20.31.123:3085:4,
Unfortunately I couldn't send you the code to test since it is hitting up on the DB
(which is constantly changing itself). All I am doing is a mass bulk from a DB table
(about 2 at a time), and they are all just simple strings. ie
cache.put(/DBConstant/State, California, 5);
We had the same issue, and what we did was cached a bunch of key matchups along with
the object. So we would do something like this:
cache.put(/foo/byId, Id, Object)
Then also
cache.put (/keylookup, /foo/byName, + Name, /foo/byId, + Id)
That way when it comes lookup time you can first do a
Ben,
When you get a chance please let me know what is coming up null. Is it something I can
check before each put?
Thanks again,
Chris
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3828988#3828988
Reply to the post :
It is while doing a bulk insert of a few thousand elements and it seems to happen
about once every 4 or 5 runs. And it isn't ever really on the same element. Sometimes
it will only get through 50 or 60 and sometimes it does 1 before it crashes.
Thanks again,
Chris
View the original post :
I am using the LRUAlgorithm for my puts. They all work perfectly nicely but every once
and a while on a put I will get this:
java.lang.NullPointerException
at org.jboss.cache.eviction.LRUAlgorithm.processQueues(LRUAlgorithm.java:72)
at
I see, so let's say I wanted to use the LRUAlgorithm on node /a of my cache to give
it a 10 second timeout. In such a case I would declare a regionManager to have my
LRUPolicy, grab a region from the manager with a node /a and the LRUAlgorithm and
set the region timeout. As follows:
I have been playing around with the new cache eviction features (Kudos by the way,
very nicely done), but I have a question.
I have successfully been able to set up regions and their eviction properties using an
xml file then loaded this into the cache using PropertyConfigurator. I have also
I understand, and thank you for the swiftness of your reply.
My question then becomes is there a way to dynamically set the timeouts of nodes
without using the xml and PropertyConfigurator? Basically a function like this:
int timeOutInSeconds = 60;
cache.setNodeTimeout(/a/b,
