-
15. Re: Config Question
Just so you know, i wont be around next week so you wont get any replies from me till monday week!!
Cheers,
LL -
16. Re: Config Question
"lovelyliatroim" wrote:
Hmm - have you tried this with 2.1.0.CR3 as well?
No I havent but i have now!!
Had some issues getting the 2.1.0.CR3 to work in JBoss AS 5.0 Beta3. First off the binary lib jboss-cachecore.jar in the meta-inf directory contains all -service.xml files, so JBoss AS picks this up and tries to deploy them and fails in doing so. Removed the -service files and re-jared the jboss-cachecore.jar without -service files.
http://jira.jboss.org/jira/browse/JBCACHE-1277 -
17. Re: Config Question
Issue appears when using OptionOverrides with cache mode set to LOCAL. Is this your scenario?
-
18. Re: Config Question
I wouldnt say its my exact scenario but more a consequence of me playing around with JbossCache.
When i was playing around i wanted to use the cache with the ClusteredCacheLoader but in order to use the ClusteredCacheLoader i needed to have it configured to replicate, you cant use the clusteredcacheloader in LOCAL mode which is what I wanted to do. Which resulted in this jira http://jira.jboss.com/jira/browse/JBCACHE-1273.
However as a work around, to stop replication happening and use the clusteredcacheloader, the guys gave me a work around. See this thread which kicked it all off http://www.jboss.com/index.html?module=bb&op=viewtopic&t=124722
So back to this, when i was running/playing with this set up, I still had the Option overrides in my code (Unintentionally at the time but i will need it there).
So for every entry i put into the cache i have this line of code just before i inserttreeCache.getInvocationContext().getOptionOverrides().setCacheModeLocal(true); treeCache.put(nodePath,map);
But just looking back at the posted cache-config, i already had the cache configured as LOCAL. Strange that it should effect it considering the cache is LOCAL. -
19. Re: Config Question
"lovelyliatroim" wrote:
But just looking back at the posted cache-config, i already had the cache configured as LOCAL. Strange that it should effect it considering the cache is LOCAL.
Strange but definitely a bug. And something we're looking into.