Resin Documentation

resin 4.0.33 release notes

We encourage people to report 4.0.33 bugs at http://bugs.caucho.com.

4.0.33 is a bug fix release. Please see changes.xtp for a list of changes.

The ServletContainerInitializer @HandlesTypes was not properly implemented in Resin 4.0. This has been fixed.

Resin's jCache implementation now supports tiered caching. The secondary tier can be used like memcache to support sharded, replicated, and persistent caching.

The example below shows an additional feature where the tiered cache loads itself through a read-through cache configuration. This improves cache miss efficiency by allowing the cache to fill itself once on every cache miss, without forcing multiple misses.

<resin xmlns="http://caucho.com/ns/resin"
       xmlns:resin="urn:java:com.caucho.resin"
       xmlns:wscache="urn:java:com.caucho.distcache.websocket"
       xmlns:test-cache="urn:java:test.cache">

<cluster id="app" root-directory="app">
  <server id="a"/>

  <host id="">
    <web-app id="">
    
      <resin:TieredCache name="t1">
        <address>localhost:6810</address>
      </resin:TieredCache>
      
    </web-app>
  </host>
</cluster>

<cluster id="cache" root-directory="cache">
  <server id="b" port="6810"/>

  <resin:TieredCacheServer/>

  <host id="">
    <web-app id="">
      <resin:ClusterCache name="t1">
        <cache-loader><test-cache:TestCacheLoader/></cache-loader>
        <read-through/>
      </resin:ClusterCache>
    </web-app>
  </host>
</cluster>

</resin>

JDBC-style caching and session replication now supported again with Resin 4.0. With Resin 4.0, the JDBC cache serves as a backing store. Resin's main cache acts like a side-cache.