[jboss-user] [JBossCache] - Re: Jboss Caching issue
bhavranjan
do-not-reply at jboss.com
Thu Feb 1 07:16:08 EST 2007
I got one solution as TreeCache is not registered in jboss.cache so its
not possible to access this . here is fine
Now i am trying to register TreeCache Mbean by these steps
I copied jboss-cache.jar and jgroups.jar in ${jboss.home}/lib dir
and copied the tree-service.xml in ${jboss.home}/server/all/deploy dir
but i am not able to register the Mbean
this is my tree-service.xml file
<?xml version="1.0" encoding="UTF-8"?>
<!-- ===================================================================== -->
<!-- -->
<!-- Sample TreeCache Service Configuration -->
<!-- -->
<!-- ===================================================================== -->
<!-- ==================================================================== -->
<!-- Defines TreeCache configuration -->
<!-- ==================================================================== -->
jboss:service=Naming
jboss:service=TransactionManager
<!--
Configure the TransactionManager
-->
org.jboss.cache.JBossTransactionManagerLookup
<!--
Node locking level : SERIALIZABLE
REPEATABLE_READ (default)
READ_COMMITTED
READ_UNCOMMITTED
NONE
-->
REPEATABLE_READ
<!--
Valid modes are LOCAL
REPL_ASYNC
REPL_SYNC
INVALIDATION_ASYNC
INVALIDATION_SYNC
-->
LOCAL
<!-- New 1.3.x cache loader config block -->
<!-- if passivation is true, only the first cache loader is used; the rest are ignored -->
false
/demo
false
<!-- we can now have multiple cache loaders, which get chained -->
org.jboss.cache.loader.FileCacheLoader
<!-- same as the old CacheLoaderConfig attribute -->
location=/tmp/bhavFileStore
<!-- only one cache loader in the chain may set fetchPersistentState to true.
An exception is thrown if more than one cache loader sets this to true. -->
true
<!-- determines whether this cache loader ignores writes - defaults to false. -->
false
<!-- if set to true, purges the contents of this cache loader when the cache starts up.
Defaults to false. -->
false
<!--
The max amount of time (in milliseconds) we wait until the
initial state (ie. the contents of the cache) are retrieved from
existing members in a clustered environment
-->
20000
<!--
Number of milliseconds to wait until all responses for a
synchronous call have been received.
-->
15000
<!-- Max number of milliseconds to wait for a lock acquisition -->
10000
<!-- Name of the eviction policy class. Not supported now. -->
jboss:service=invoker,type=jrmp
jboss.cache:service=TreeCache
TreeCache true org.jboss.cache.TreeCacheMBean
org.jboss.proxy.ClientMethodInterceptor
org.jboss.proxy.SecurityInterceptor
org.jboss.invocation.InvokerInterceptor
jboss:service=invoker,type=jrmp
jboss.cache:service=TreeCache
should i put this file in default/deploy dir
any help would be appreciated
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4009364#4009364
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4009364
More information about the jboss-user
mailing list