Hello,
I'd like to manually evict an item from the in-memory cache but not from the
JDBC cache loader. This method seems to be what I'm looking for:
cache.evict(Fqn)
I can call this method fine but when I then attempt to retrieve the node
(expecting it to be loaded from the database after evic
Our JBoss Cache configuration is currently using the JDBCCacheLoader and Oracle
11i. This seems to work fine but occasionally during load tests we'll get this
error:
anonymous wrote : org.jboss.cache.CacheException: java.sql.SQLException:
ORA-01461: can bind a LONG value only for insert into a
During load tests, we keep running into this error:
anonymous wrote : org.jboss.cache.lock.TimeoutException: Unable to acquire lock
on Fqn [/session/c06045ea-bb09-44c6-910d-d84eedc67d3e] after [1]
milliseconds
| for requestor [Thread[http-0.0.0.0-8080-199,5,jboss]]! Lock held by [null]
|
I have configured JBoss Cache to asynchronously write to a MySQL database. I'm
using this "write-behind" configuration in order to improve performance by not
blocking the client while writing to the database. However, it seems that there
is still a performance hit. For example, I tested writing
Yep. You nailed it. I discovered that I had an old version of the WAR file
still in JBoss's deploy directory. Somehow JBoss was inserting the newer file
into JBC but using the older class when pulling it out. I removed the old WAR
file and everything seems to be working fine. Thanks!
View the o
No, it is not mutable. The serialized classes contain this code generated by
the JAXB compiler:
private final static long serialVersionUID = 1L;
The classes seem to be getting stored with this UID but not extracted that way.
View the original post :
http://www.jboss.org/index.html?module=bb&op
I am running into a problem when deserializing objects stored in the JBoss
Cache via the JDBC cache loader. I can start the cache, load objects into it,
and read objects from it without a problem. The objects that I have stored in
the cache specifically set the serialVersionUID variable to 1. Th
In addition to the standard "jbosscache" table that contains all of the cache
data (when using the JDBCCacheLoader), JBoss Cache also creates a dummy table
named "jbosscache_D". This table seems to get recreated every time the cache is
started. The AdjListJDBCCacheLoader class's start() method c
I have two separate web applications that both need access to the same JBoss
Cache. That is, one WAR may store information in the cache that needs to be
accessed by another WAR. Here's what I've tried so far:
1. I tried storing the cache object in the JNDI tree but this doesn't work
since it is
I've been looking for TreeCacheMBean as well. It is not part of the jboss-cache
artifact mentioned above.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4247721#4247721
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=424
I'm trying to register JBoss Cache with the JBoss MBean server but I can't find
the TreeCacheMBean class anywhere. I'm using JBoss Cache Core 3.1.0.GA. Does
anyone know which JAR contains TreeCacheMBean? Also, is there a Maven
repository that hosts this JAR file?
View the original post :
http:
"galder.zamarr...@jboss.com" wrote : What JBoss Cache version are you using?
|
I'm using version 3.1.0.GA and I seem to be able to retrieve fully qualified
nodes from the root node just fine (not just the root node's immediate
children). Here is some more sample code from the Users' Guide:
"galder.zamarr...@jboss.com" wrote : getChild() takes the fqn of the child,
it's a relative method. Root already provides the first /, so the name of the
child is without that first /: content/timestamp
|
| If u used Cache rather than Node, you'd do the following using the absolute
path:
I am getting very strange results when calling node.getChild() in different
ways. For instance, I've populated a local cache (using the JDBC cache loader)
with the following node:
/content/timestamp
This node has a value in its hashmap named "timestamp" that contains a Long.
The tricky thing i
"galder.zamarr...@jboss.com" wrote :
| Looks to me the different caches accessed by your clients are not clustered
which is the root of your problem. If they're clustered, modifications could be
replicated to other cache instances or modifications could result in
invalidation messages to othe
"drcallaway" wrote : Can you say a little more about the
Option.suppressPersistence API? How would I use that? Where can I get a
reference to the Option object?
Never mind. I figured it out and your suggestion worked great. Here's the new
code:
Option option = cache.getIn
"mircea.markus" wrote : So you know that data changed in the cache store and
want to 'refresh', you cannot do a cache.remove as this would also remove it
from persistent store, right?
Yes. That's exactly the problem. Removing a node from the cache also removes it
from the data store. I would l
"galder.zamarr...@jboss.com" wrote :
| What do you exactly mean with data changing? Is data changing as a result
of your interaction with the cache? Are you changing the data directly in the
cache store? I don't understand why you'd want the data to be replaced with the
one in the cache store
Woops! Should have previewed that. Here it is again a bit more readable:
| CacheSPI cacheSpi = (CacheSPI) cache;
| CacheStoreInterceptor csi = null;
| int index = 0;
|
| for (Object o : cacheSpi.getInterceptorChain())
| {
| if (o
I was able to get this working with this code:
CacheSPI cacheSpi = (CacheSPI) cache;
CacheStoreInterceptor csi = null;
int index = 0;
for (Object o : cacheSpi.getInterceptorChain())
{
if (o instanceof CacheStoreInterceptor)
{
I have a configuration where I'm using JBoss Cache in local mode (with sticky
sessions) along with a JDBC cache loader. At startup, the JBoss Cache preloads
a node in the cache with mostly static data that had previously been persisted
to the database. Though mostly static, this data may occasio
Yes. I have set async = true but that doesn't prevent errors in the
asynchronous cache loader from throwing exceptions. If the database goes down,
so does the local cache. However, I was able to fix my problem by subclassing
JDBCCacheLoader and catching the exceptions thrown by its public method
I'm working on a caching solution that requires each server in the farm to
maintain its own local cache using sticky sessions. For fault tolerance, I'd
also like to asynchronously persist cached items to a JDBCCacheLoader. This
way, if one of the servers fail, another server can take over for it
23 matches
Mail list logo
