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.
View the original post :
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
Issue appears when using OptionOverrides with cache mode set to LOCAL. Is this
your scenario?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4135496#4135496
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4135496
Just so you know, i wont be around next week so you wont get any replies from
me till monday week!!
Cheers,
LL
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4123421#4123421
Reply to the post :
lovelyliatroim wrote : anonymous 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
Ok tried the Dummy Transaction manager and same story, its in the memory of the
cache but not in the DB.
Log is as follows
| 2008-01-24 15:59:05,586 INFO [STDOUT] 2008-01-24 15:59:05,586 DEBUG
[at.sit.cdms.web.actions.ActionFactory] - Looking for bean addItem
|
| 2008-01-24
Sorry didnt have trace on with that last one, here it is with trace on
| 2008-01-24 16:12:02,352 INFO [STDOUT] 2008-01-24 16:12:02,352 DEBUG
[at.sit.cdms.web.actions.ActionFactory] - Looking for bean addItem
|
| 2008-01-24 16:12:02,352 DEBUG [at.sit.cdms.web.actions.ActionFactory]
Hmm - have you tried this with 2.1.0.CR3 as well?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4123122#4123122
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4123122
___
anonymous wrote :
|
| Definitely a limitation. Could you please create a feature request in JIRA
for this and vote for it?
|
If i find out how or where to do this i will ;).
anonymous wrote :
| What could be your problem is how often your eviction thread kicks in. If
you have enough
anonymous wrote :
| Definitely a limitation. Could you please create a feature request in JIRA
for this and vote for it?
|
Done.
http://jira.jboss.org/jira/browse/JBCACHE-1274
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4122536#4122536
Reply to the
lovelyliatroim wrote :
| Currently running every 5 seconds, will set it for a longer time period.
Can you set the wakeUpIntervalSeconds on a region basis or is it a global
cache setting??
|
No, this is a cache-wide setting.
lovelyliatroim wrote :
| Hmmm im not sure we are talking
anonymous wrote :
| No, this is a cache-wide setting.
|
Thats what i thought!
anonymous wrote :
| See the JavaDocs for the AsyncCacheLoader wrapper, which has all the
options you can add to your cache loader. You can control your batch size and
triggers.
|
Super, will have a look
Right, in the quest for higher throughput using my cache and the
JDBCCacheLoader im experiencing what to me is strange behaviour.
Here is my config for the record
| ?xml version=1.0 encoding=UTF-8?
|
| !-- =
--
| !--
I don't see any log entries pertaining to the CacheLoader and CacheStore
interceptors. Could you pls enable TRACE logging for these as well?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4122641#4122641
Reply to the post :
Here you go
| 2008-01-23 15:16:25,916 INFO [STDOUT] 2008-01-23 15:16:25,916 DEBUG
[at.sit.cdms.web.actions.ActionFactory] - Looking for bean addItem
|
| 2008-01-23 15:16:25,916 DEBUG [at.sit.cdms.web.actions.ActionFactory]
Looking for bean addItem
|
| 2008-01-23 15:16:25,916 DEBUG
Hmm, this is the interesting bit:
| 2008-01-23 15:16:25,931 TRACE [org.jboss.cache.interceptors.TxInterceptor]
No modifications in this tx. Skipping beforeCompletion()
|
here clearly has been a modification. Not that I recommend this in production,
but to help debug, could you try the
Hmm, just tried running
OptimisticWithCacheLoaderTest#testCacheStoringImplicitTx() with JBoss-JTA
(Arjuna's TM) instead of the DummyTM and it works fine.
Could you enable TRACE logging on all interceptors?
View the original post :
lovelyliatroim wrote :
| I have a cache configured with a JDBCCacheLoader and in my cache i have a
region where i dont want any nodes in the cache memory i.e they will be
retrieved through the cacheloader. How do i configure the region to have no
nodes in memory since if i set it to 0 then
18 matches
Mail list logo
