Terracotta Discussion Forums

Hi,

Trying to set up a server array and ehcache to connect to it. I'm using version 3.7.0 and have downloaded the enterprise version and trial license.

My server array seems to start up fine, however the client starts up with the following error:
Code:

 012-07-25 11:20:26,524 INFO - Terracotta 3.7.0, as of 20120718-055216 (Revision 18930-20453 by cruise@su10mo128 from 3.7.0)
 2012-07-25 11:20:27,254 INFO - Successfully loaded base configuration from server at 'w2-gst-m3k-02:9510'.
 2012-07-25 11:20:27,438 INFO - Successfully loaded base configuration from file at '/var/tmp/tc-config1515344586748239931.xml'.
 2012-07-25 11:20:27,482 INFO - Log file: '/tmp/terracotta/client-logs/terracotta-client.log'.
 2012-07-25 11:20:28,766 FATAL - An attempt to start a Terracotta server array with more than one active server failed. \
     This feature is not available in the currently installed Terracotta platform. For more information on supported features \
     for Terracotta platforms, please see this link http://www.terracotta.org/sadne

The ehcache.xml is as follows:

Code:

 <?xml version="1.0" encoding="UTF-8"?>
 
 <ehcache name="YCSB">
   <defaultCache
       maxElementsInMemory="10000"
       eternal="false"
       timeToIdleSeconds="120"
       timeToLiveSeconds="120"
       overflowToDisk="false"
       diskSpoolBufferSizeMB="30"
       maxElementsOnDisk="10000000"
       diskPersistent="false"
       diskExpiryThreadIntervalSeconds="120"
       memoryStoreEvictionPolicy="LRU"/>
   <cache name="terraCache"
          maxElementsInMemory="10"
          maxElementsOnDisk="0"
          eternal="true"
          memoryStoreEvictionPolicy="LFU">
     <terracotta/>
   </cache>
   <terracottaConfig url="w2-gst-m3k-02:9510"/>
 </ehcache>

FWIW I've trussed the process and can see that it does read both ehcache.xml as well as terracotta-license.xml from disk.

Thanks for any help

perhaps we've got an error in our new release, but from the terracotta server output there, it looks like you're not running the Enterprise edition

It would say "Terracotta Enterprise 3.7.0 ..." instead

Hi Tim

Thanks for the reply.

The message I posted initially is from the client. The server reports the following:
Code:

 2012-07-25 08:35:33,137 INFO - Terracotta Enterprise 3.7.0, as of 20120718-061707 (Revision 18930-20453 by cruise@su10vmo104 from 3.7.0)

I'm creating the client-side cache simply by calling CacheManager.newInstance(). Should I be doing something differently?

--Jens

Sorry I didn't read that correctly. On the client side perhaps you're not using the "-ee" versions of the client jars (ehcache-core-ee, ehcache-terracotta-ee and terracotta-toolkit-1.6-runtime-ee). There are versions of each of those jars w/o an "-ee" in the artifact name. The toolkit-runtime jar in particular is the one I suspect in this case

Yes, I'm building my client using maven and was using this snippet in my pom.xml:
Code:

    <dependency>
       <groupId>net.sf.ehcache</groupId>
       <artifactId>ehcache</artifactId>
       <version>2.6.0</version>
       <type>pom</type>
     </dependency>
 ...
   <repositories>
     <repository>
       <id>terracotta-releases</id>
       <url>http://www.terracotta.org/download/reflector/releases</url>
       <releases><enabled>true</enabled></releases>
       <snapshots><enabled>false</enabled></snapshots>
     </repository>
   </repositories>

However, if I change the artifactId to ehcache-ee it isn't found by maven.

The solution that worked for me was to, instead use these artifacts:
Code:

     <dependency>
       <groupId>net.sf.ehcache</groupId>
       <artifactId>ehcache-core-ee</artifactId>
       <version>2.6.0</version>
     </dependency>
     <dependency>
       <groupId>net.sf.ehcache</groupId>
       <artifactId>ehcache-terracotta-ee</artifactId>
       <version>2.6.0</version>
     </dependency>

Thanks for your help!

sounds good. I'd have to go hunt down whether an ehcache-ee exists for 2.6.0, but the combination of the two artifacts you've shown is appropriate.

For 2.7.x I know ehcache-ee will exist and will actually be a jar (as opposed to a pom that declares the two dependencies)