Well, good / bad news here...
The good news is that by upgrading to Hibernate 3.2 CR 1 and using the
OptimisticTreeCacheProvider instead of the default TreeCacheProvider, we were
able to get past the basic issue of puts not taking effect in the cache (which
was the root of issue #2 described be
We're still working on testing 1.3 with Hibernate. I have a couple of
questions, if anyone can help with, I'd appreciate it.
1) Is it okay to use optimistic node locking with REPLICATION_ASYNC, or is
optimistic node locking only meant for use with INVALIDATION_ASYNC?
2) Is there anything with
Hi Manik,
We are using Hibernate 3.0.5. The load test isn't specific to JBossCache -- it
is a full load test of our application; we aren't going out of our way to
create transactions on the same object to induce concurrency, but it probably
happens as a 'side effect' of our test.
As best as w
I tried increasing the timeout from 15000 to 15. Similar results.
However, I noticed that there's a new option with 1.3, in addition to the new
INVALIDATION_ASYNC option...
| OPTIMISTIC
|
Setting this caused all of the lock exceptions to go away!
I'm now getting OutOfMemory
Perhaps I'm missing a setting? None of my timeouts are set to 0, as seen below.
I can re-run a test, but which timeouts should I increase?
Thanks!
Aaron
|
|
|
|
|
|
|
| jboss:service=Naming
| jboss:service=TransactionManager
|
|
|
|
Perhaps I'm missing a setting? None of my timeouts are set to 0, as seen below:
|
|
|
|
|
|
|
| jboss:service=Naming
| jboss:service=TransactionManager
|
|
|
| org.jboss.cache.DummyTransactionManagerLookup
|
|
| READ_COM
Under a substantial amount of load, it was not uncommon to get
TimeoutException's and IdentityLock's in 1.2.4.SP2 with REPL_ASYNC
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3931654#3931654
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=p
We have run a load test against our application swapping in the JBossCache 1.3
Beta 2 jars, using INVALIDATION_ASYNC as the CacheMode and READ_COMMITTED as
the IsolationLevel. Approximately 5 minutes into the test, we start to receive
many IdentityLock errors on various objects. Is there anyth
I am very intrigued at the new features coming in version 1.3. I would like to
help out in alpha / beta testing when it becomes available. We have a
performance automation suite I can run it through with our application. What
is the expected timeframe of a alpha or beta release becoming avail
