Log error

[cwampler]

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, lock=org.jboss.cache.lock.IdentityLock@67cd84
2004-04-21 14:46:28,474 INFO - TreeCache$MessageListenerAdaptor.setState - setState(): locking the old tree was successful
2004-04-21 14:46:28,484 DEBUG- LRUPolicy.nodeAdded - nodeAdded(): fqn- /
2004-04-21 14:46:28,484 ERROR- TreeCache$MessageListenerAdaptor.setState - setState(): locking/unlocking the old tree failed
java.lang.NullPointerException
at org.jboss.cache.eviction.LRUPolicy.nodeAdded(LRUPolicy.java:49)
at org.jboss.cache.TreeCache.notifyNodeAdded(TreeCache.java:2873)
at org.jboss.cache.TreeCache.notifyAllNodesCreated(TreeCache.java:2920)
at org.jboss.cache.TreeCache$MessageListenerAdaptor.setState(TreeCache.java:2367)
at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.passUp(MessageDispatcher.java:551)
at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:316)
at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:596)
at org.jgroups.JChannel.up(JChannel.java:873)
at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:349)
at org.jgroups.stack.ProtocolStack.receiveUpEvent(ProtocolStack.java:365)
at org.jgroups.stack.Protocol.passUp(Protocol.java:482)
at org.jgroups.protocols.pbcast.STATE_TRANSFER.handleStateRsp(STATE_TRANSFER.java:299)
at org.jgroups.protocols.pbcast.STATE_TRANSFER.up(STATE_TRANSFER.java:119)
at org.jgroups.stack.UpHandler.run(Protocol.java:55)
2004-04-21 14:46:28,484 INFO - TreeCache$MessageListenerAdaptor.setState - setState(): forcing release of all locks in old tree
2004-04-21 14:46:28,484 INFO - TreeCache.fetchStateOnStartup - state was retrieved successfully
2004-04-21 14:46:28,484 INFO - LRUPolicy.cacheStarted - Starting eviction policy using the provider: org.jboss.cache.eviction.LRUPolicy

Thanks again,
Chris

[ben.wang]

This is a bug that has been fixed. It will be released in the upcoming 1.0 patch.

-Ben