1. Regarding soft references in the cache, again this isn't something that
people have asked for; you're the first. Feel free to raise a JIRA for it.
2. There is no memory-based eviction policy yet (see JBCACHE-11). Have a
look, vote for it, and if you have the time maybe even contribute an
No idea - try enabling your logs and see if all your invocations actually
result in cache misses?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4152596#4152596
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4152596
Thanks Manik!
Good idea to contribute that memory eviction... I should think about it.
I have another question.
Why once I've started use OptimisticLocking(with transaction manager), hits
statistics are always 0. Puts and Miss counter grows, but hits are always 0.
Can you explain?
Thank you.
What version of JBC is this?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4152610#4152610
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4152610
___
jboss-user mailing list
I've noticed in log:
[EMAIL PROTECTED]:53:31 INFO (OptimisticNodeInterceptor.java:103) - CRUD
Method _put(GlobalTransaction:172.16.194.121:2104:6,
/test/web/TestEntity/test.web.TestEntity#5, item,
{_subclass=test.web.TestEntity, _version=null, name=name-4,
_lazyPropertiesUnfetched=true},
java.lang.NoClassDefFoundError: org/jboss/cache/TransactionManagerLookup
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:2357)
at java.lang.Class.getConstructor0(Class.java:2671)
at
1.3-pre-alpha
But it's the one shipped with last hibernate.
When I tried to use newest JBC, hibernate complained, that it can't find a
class , something like ../cache/ when JBC has this class under
../transaction/cache...
some change in package name and no integration anymore...
View the
Use the latest 1.4.X release. I wouldn't recommend using alpha software, much
less pre-alpha! :-)
JBC 2.x will only be compatible with Hibernate 3.3.x which hasn't been released
yet.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4152639#4152639
Reply to
Great!
But after that installation I have an error:
org.hibernate.cache.CacheException: java.lang.UnsupportedOperationException:
putFailFast() is not supported with Optimistic Locking
org.hibernate.cache.TreeCache.put(TreeCache.java:81)
Have you seen http://wiki.jboss.org/wiki/JBossCacheHibernate?
From the wiki: wrote :
| If you are using OPTIMISTIC locking, make sure you use the
OptimisticTreeCacheProvider that ships with Hibernate 3.2.x and higher.
|
View the original post :
We sent messages in the same time!
Thanks Manik!
I appreciate your help so much!!! Peter.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4152661#4152661
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4152661
One more thanks!
Optimistic works. I use JBC 1.4 SP9.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4152662#4152662
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4152662
___
I see, where you throw that exception, seems you have reasons for that.
But why hibernate use that putFailFast I do not know...
Seems Optimistic locking is gone for me...
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4152660#4152660
Reply to the post :
13 matches
Mail list logo
