Hmmm. While trying to create a unit test method for you (for the latest version
from CVS), I wrote the following method (added to ExplicitVersionsTest):
|Node root = cache.getRoot();
|
|TestVersion lev2V = new TestVersion(Lev2-v);
|
Hi,
I've been trying to use explicit versioning and experiencing some problems .
On certain cases, the OptimisticValidatorInterceptor is throwing exceptions at
commit: When calling wrappedNode.isVersioningImplicit(), 'true' is returned
even though I can see that my specialized version object
Great! Thank you for the quick round-up.
I've taken a look at NodeAPITest (and NodeAPIOptimisticTest) and indeed, the
problem is well tested there.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3998035#3998035
Reply to the post :
Hi,
I'm talking about the regular Cache (TreeCache), not PojoCache.
It seems that if I try to use the Node interface directly (after getting some
sub-node from the Cache interface), in optimistic locking mode, a simple
node.put(k, v) will not make a subsequent node.get(k) return v.
However, if
Great to hear that! However, I'm talking about the latest version from CVS (as
of today) - so assuming the ALPHA2 changes have already been committed, this
issue persists in the updated version...
Are these changes indeed yet to be committed?
View the original post :
Thanks for your reply.
Unfortunately, I need to use optimistic locking because in my usage scenario,
deadlock prevention and/or recovery will be very hard when using pessimistic
locking... That was one of the reasons for us to use JBossCache in the first
place...
Any chance this will get
Hi,
I'm experiencing a problem which I believe might be related to the new tree
structure in PojoCache (i.e., the structure that enables canonical locking). It
seems that when using optimistic locking, since attaching an object to the
PojoCache will cause a version increment on
You'll find many sample configurations in the CVS, under etc/META-INF.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3994476#3994476
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3994476
Hi,
I've ran the test, and indeed it works in its current form - but not when using
optimistic locking (e.g. subsistute 'local-service.xml' in
'replAsync-optimistic-service' in the setUp() method). Results of running unit
tests from yesterday's CVS version:
| Before (using
Here are the stack traces of the locked threads (copied from Eclipse's
debugger, after suspending them):
Thread 1
Thread [TotalRecordings Thread] (Suspended)
ClassLoader.findBootstrapClass(String) line: not available [native
method]
Thank you very much for your help!
I've tried using ClassicWeavingStrategy. Unfortunately, the problem still
occurs: One thread is stuck as before (ClassLoader.findBoostrapClass(...) ) and
the other is now stuck on ClassicWeavingStrategy.translate(AspectManager,
String, ClassLoader, byte[]) -
Hi again,
I've not been able to recreate the bug in a test program. However, it now
definitely happens again, with the updated lib. One thread is stuck on
ClassLoader.findBoostrapClass() and another one on
SuperClassesFirstWeavingStrategy.obtainCtClassInfo(). One of them is trying to
load an
Hi,
This regards a bug (?) in v2.0 alpha that'll affect only the case of storing a
sorted set (e.g. TreeSet) in PojoCache. Now, the documentation specifies that
The Set interface maps to java.util.HashSet implementation, but does that
mean the user should never store i.e. TreeSets (e.g., as a
Thanks for your quick reply (and for a great product :-) ) !
I tried out the fix, and it seems to be working. However, trying a few runs,
one of them still seemed to hang as before. This didn't happen again, though...
I'm trying to create a simple program to reproduce the bug (using the old
Regards,
Chasta
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3989068#3989068
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3989068
___
jboss-user mailing list
jboss-user
, and should look elsewhere to implement my functionality? If
I'm not wrong, would you consider modifying the API to allow for such usage
scenarios?
Thanks Regards,
Chasta
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3984125#3984125
Reply to the post :
http
16 matches
Mail list logo
