Re: [jbosscache-dev] State transfer unit tests status
On 22 Aug 2006, at 21:58, Vladimir Blagojevic wrote:
The cause of OptionalDataException that was messing up state
transfers
is now fixed. However, "Initial state transfer failed" error was still
popping up in some tests. The cause of this error is incorrect
logic in
TreeCache.startService related to fetching of in memory state. JBC can
not fetch in memory state based only on FetchInMemoryState element but
should rather use JBC 1.4 logic?
protected boolean shouldFetchStateOnStartup() {
return !configuration.isInactiveOnStartup() && buddyManager ==
null
&&
(configuration.isFetchInMemoryState() || (cacheLoaderManager
!= null &&
cacheLoaderManager.isFetchPersistentState()));
}
Sure, I'm just wondering how this got missed in HEAD since this part
of TreeCache should not have changed. Is this fix in CVS now?
When I use this approach "Initial state transfer failed"
errors go
away.
State transfer tests now fail on:
Ok. This we can look at individually now.
1) Region exceptions
org.jboss.cache.RegionNotEmptyException: Node / already exists and is
not empty at
org.jboss.cache.TreeCache.activateRegion(TreeCache.java:954) at
2) Activators
Activator A caught an exception
junit.framework.AssertionFailedError: Activator A caught an
exception at
org.jboss.cache.statetransfer.VersionedTestBase.concurrentActivationTe
st
(VersionedTestBase.java:427) at
org.jboss.cache.statetransfer.VersionedTestBase.testConcurrentActivati
on
Sync(VersionedTestBase.java:353)
3) Buddy integration
node /a/d not found (gtx=null, caller=Thread[main,5,main])
org.jboss.cache.NodeNotExistsException: node /a/d not found (gtx=null,
caller=Thread[main,5,main]) at
org.jboss.cache.TreeCache._put(TreeCache.java:2783) at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
_______________________________________________
jbosscache-dev mailing list
jbosscache-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosscache-dev