"[EMAIL PROTECTED]" wrote :
| A cache is not a database. A database is, by definition, persistent
storage so such behaviour is nonsensical for a db. And this is why caches
delegate persistence to dbs - in JBC's case using a cache loader.
Umm, persistence is a relative term, valid within a c
"Brian Stansberry in jbosscache-dev" wrote :
| Basically, the state transfer semantics imply that the in-memory state
| is "consistent" with the cluster when start returns. Either its
| "consistent" because it's been transferred, or it's "consistent" because
| it's empty and waiting to
anonymous wrote : When a cache stops, you are meant to lose this in-memory
state.
I disagree. When a cache stops, you should lose the ability to operate on the
data through the cache interface. I've never seen a database deleting tables
when you stop the db server/agent. I would agree with you i
"[EMAIL PROTECTED]" wrote : "[EMAIL PROTECTED]" wrote : This problem has been
fixed, try the latest cvs HEAD checkout if you want to verify it works for you.
|
| Thank a lot, Jason! Works perfectly so far.
|
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&
Hi,
I am trying to get remote invocation working in AS 4.0.5. I've started with RC9
and patched the IsLocalInterceptor that used to call the local bean instead of
the remote one.
But now I am getting this exception:
| Caused by: java.lang.Exception: Can not make remoting client invocation du
We tried to migrage from RC1 to RC3 and are quite disappointed. IMO, there are
a bunch of things that can happen in alpha or beta state, but really shouldn't
happen between candidate releases.
1) API changes
There's already a thread about this regarding listener notification.
2) Behavior change
"FredrikJ" wrote :
| 1. Wouldn't this be considered a major api change(?) and as such should not
go in between two cr releases?
|
I totally agree. We will have to go into production with a patched cr2.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067
Our application uses multiple caches, each of which having an "owner" node,
which is the authority on cache data and also the only node that can provide
state for a particular cache.
We used to do this (years ago) by ensuring that owner == JGroups coordinator,
but are now looking for a solution
I am having the same problem. It also isn't possible to configure everything in
3.2 and then switch to 3.3. It's not possible to start the server (list of
available runtimes/server types is empty).
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4036842#403684
Oh, I quickly tested it before posting and now the code contains some of my
external variables :(, "_cache.getCache()" is just the pojo cache I used and
should read "cache_".
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4036116#4036116
Reply to the post :
"[EMAIL PROTECTED]" wrote :
| Also, there is a known design flaw, where notifications are only dispatched
locally.
| http://jira.jboss.com/jira/browse/JBCACHE-774
|
Yes, I realized this too. Unfortunately, I need to have it now, so I'm trying
to do everything from the outside by convertin
Hey everybody,
I'm experimenting with Habanero b2, and with POJO listener notification in
particular. I have a couple of questions:
- I am getting "attach" and "detach" notifications, but no "modify" calls. Do I
have to configure something to make this work?
- Will there be an API to query the
Hello,
We are currently considering using JBossCache in one of our projects. It should
be able to do the following:
--
There are several producer nodes. Each node collects data that it keeps in
memory. Producers read, update, write their own data. They don't need to know
(and shouldn't) about
13 matches
Mail list logo
