I have deployed JBossCache 1.2.1 via a treecache-service.xml in my deploy 
directoty (JBoss 3.2.6) but I always get NameNotFoundException when I try and 
look it up in my web app. The JMX Console and the log are telling me the cache 
is deployed properly.

treecache-service.xml:

  | <?xml version="1.0" encoding="UTF-8"?>
  | <!-- 
  |   Copyright (C) 2005 LAMS Foundation (http://lamsfoundation.org)
  | 
  |   This program is free software; you can redistribute it and/or modify
  |   it under the terms of the GNU General Public License as published by
  |   the Free Software Foundation; either version 2 of the License, or
  |   (at your option) any later version.
  | 
  |   This program is distributed in the hope that it will be useful,
  |   but WITHOUT ANY WARRANTY; without even the implied warranty of
  |   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  |   GNU General Public License for more details.
  | 
  |   You should have received a copy of the GNU General Public License
  |   along with this program; if not, write to the Free Software
  |   Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307
  |   USA
  | 
  |   http://www.gnu.org/licenses/gpl.txt 
  | -->
  | 
  | 
  | <!-- ===================================================================== 
-->
  | <!--                                                                       
-->
  | <!--  Sample TreeCache Service Configuration                               
-->
  | <!--                                                                       
-->
  | <!-- ===================================================================== 
-->
  | 
  | <server>
  | 
  |     <classpath codebase="./lib" archives="jboss-cache.jar, jgroups.jar"/>
  | 
  | 
  |     <!-- 
==================================================================== -->
  |     <!-- Defines TreeCache configuration                                    
  -->
  |     <!-- 
==================================================================== -->
  | 
  |     <mbean code="org.jboss.cache.TreeCache"
  |         name="jboss.cache:service=TreeCache">
  | 
  |         <depends>jboss:service=Naming</depends>
  |         <depends>jboss:service=TransactionManager</depends>
  | 
  | 
  |     <!-- Use DefaultCache to bind the cache into JNDI. The proxy returned 
as part of the lookup can be used both
  |             by local (e.g. servlet) and remote (e.g. RMI) clients -->
  |        <attribute name="JndiName">
  |            name=MyTreeCache
  |        locatorURI=socket://:5555
  |        </attribute>
  | 
  |         <!-- Configure the TransactionManager -->
  |         <attribute 
name="TransactionManagerLookupClass">org.jboss.cache.JBossTransactionManagerLookup</attribute>
  | 
  | 
  |         <!--
  |             Node locking level : SERIALIZABLE
  |                                  REPEATABLE_READ (default)
  |                                  READ_COMMITTED
  |                                  READ_UNCOMMITTED
  |                                  NONE
  |         -->
  |         <attribute name="IsolationLevel">READ_COMMITTED</attribute>
  | 
  |         <!--
  |              Valid modes are LOCAL
  |                              REPL_ASYNC
  |                              REPL_SYNC
  |         -->
  |         <attribute name="CacheMode">LOCAL</attribute>
  | 
  |         <!-- Name of cluster. Needs to be the same for all clusters, in 
order
  |              to find each other
  |         -->
  |         <!--attribute name="ClusterName">TreeCache-Cluster</attribute-->
  | 
  |         <!-- JGroups protocol stack properties. Can also be a URL,
  |              e.g. file:/home/bela/default.xml
  |            <attribute name="ClusterProperties"></attribute>
  |         -->
  | 
  |         <!--attribute name="ClusterConfig">
  |             <config-->
  |                 <!-- UDP: if you have a multihomed machine,
  |                 set the bind_addr attribute to the appropriate NIC IP 
address -->
  |                 <!-- UDP: On Windows machines, because of the media sense 
feature
  |                  being broken with multicast (even after disabling media 
sense)
  |                  set the loopback attribute to true -->
  |                 <!--UDP mcast_addr="228.1.2.3" mcast_port="48866"
  |                     ip_ttl="64" ip_mcast="true"
  |                     mcast_send_buf_size="150000" mcast_recv_buf_size="80000"
  |                     ucast_send_buf_size="150000" ucast_recv_buf_size="80000"
  |                     loopback="true"/>
  |                 <PING timeout="2000" num_initial_members="3"
  |                     up_thread="false" down_thread="false"/>
  |                 <MERGE2 min_interval="10000" max_interval="20000"/>
  |                 <FD shun="true" up_thread="true" down_thread="true"/>
  |                 <VERIFY_SUSPECT timeout="1500"
  |                     up_thread="false" down_thread="false"/>
  |                 <pbcast.NAKACK gc_lag="50" 
retransmit_timeout="600,1200,2400,4800"
  |                     max_xmit_size="8192" up_thread="false" 
down_thread="false"/>
  |                 <UNICAST timeout="600,1200,2400" window_size="100" 
min_threshold="10"
  |                     down_thread="false"/>
  |                 <pbcast.STABLE desired_avg_gossip="20000"
  |                     up_thread="false" down_thread="false"/>
  |                 <FRAG frag_size="8192"
  |                     down_thread="false" up_thread="false"/>
  |                 <pbcast.GMS join_timeout="5000" join_retry_timeout="2000"
  |                     shun="true" print_local_addr="true"/>
  |                 <pbcast.STATE_TRANSFER up_thread="false" 
down_thread="false"/>
  |             </config>
  |         </attribute-->
  | 
  | 
  |         <!--
  |             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
  |         -->
  |         <attribute name="InitialStateRetrievalTimeout">5000</attribute>
  | 
  |         <!--
  |             Number of milliseconds to wait until all responses for a
  |             synchronous call have been received.
  |         -->
  |         <attribute name="SyncReplTimeout">10000</attribute>
  | 
  |         <!-- Max number of milliseconds to wait for a lock acquisition -->
  |         <attribute name="LockAcquisitionTimeout">15000</attribute>
  | 
  | 
  |         <!-- Name of the eviction policy class. -->
  |         <attribute 
name="EvictionPolicyClass">org.jboss.cache.eviction.LRUPolicy</attribute>
  | 
  |         <!-- Specific eviction policy configurations. This is LRU -->
  |         <attribute name="EvictionPolicyConfig">
  |            <config>
  |               <attribute name="wakeUpIntervalSeconds">5</attribute>
  |               <!-- Cache wide default -->
  |               <region name="/_default_">
  |                   <attribute name="maxNodes">5000</attribute>
  |                   <attribute name="timeToLiveSeconds">1000</attribute>
  |               </region>
  |               <region name="/org/lamsfoundation/lams/contentrepository">
  |                             <attribute name="maxNodes">200</attribute>
  |                 <attribute name="timeToLiveSeconds">900</attribute>
  |               </region>
  |            </config>
  |         </attribute>
  |     </mbean>
  | 
  | 
  | </server>
  | 

the lookup code (hard coded jndi name for testing):

  | Context ctx =  new InitialContext();
  | TreeCache cache = (org.jboss.cache.TreeCache) 
ctx.lookup("java:MyTreeCache");
  | 

Similar code works for looking up datasources I have deployed using a *-ds.xml 
in the same webapp. Has anybody any idea why this doesn't work?

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3869648#3869648

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3869648


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to