Thanks Alex, just a few more questions:
Sorry for taking so long, I wanted to have a look at the new container
1)I noticed that the their is no Cache Invalidation trigger for this container. Since
it is commit option C, how long does this cache live? Is it invalidated by the
InvalidationManage
1) yes, 3.2.6 will include a new container configuration
anonymous wrote :
|
|
| cmp2.x jdbc2 pm
|
This container is a new implementation and does not have all the features of the
current standard container. This was driven by SPECjAppServer2002 optimization wor
Sorry, one more thing... For #2, how do you configure optimistic+pessimistic at the
same time if only one locking policy is available per container?
-I
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3844740#3844740
Reply to the post :
http://www.jboss.org/in
Thanks Alex-
Read through the documentation(including paid docs) and have a few more clarifications:
1)AdminDevel_323.Page 302 anonymous wrote : The JBoss developers are currently
exploring ways to allow commit-option ÃÂÃÂAÃÂÃÂ as well (which would allow the
use of caching for this option).
Re
Check JBossCMP wiki for caching and locking.
You could use IPT for read-write container and standard container configuration with
commit option A and cache invalidation for read-only container.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3844215#3844215
Rep
