Skip to main content

Configure Oracle Coherence as a second level(L2) cache

It's republish of my blog from another domain. The post was published at May 13 2008.
A few weeks before Oracle corporation bought company tangosol, which have a caching framework for enterprise application. Coherence might be used as a second level cache or as Cache store in any enterprise solution. How to use coherence as a Cache store would be found in the following URL:http://www.oracle.com/technology/pub/articles/vohra-coherence.html  . In the current blog we will configure a coherence L2 cache using Hibernate (Hibernate - a well known ORM framework).

First, download oracle Coherence from the following URL http://www.oracle.com/technology/software/products/ias/htdocs/coherence.html

Using Coherence as L2 cache we only need 3 libraries out of others: coherence.jar, coherence-hibernate.jar, tangosol.jar.

Install them in local maven2 repositories. Now we have to configure hibernate.cfg.xml which should be in application classPath as follows:

By default Coherence will use configuration from coherence-hibernate.jar/coherence-config.xml. We may override the configuration by providing a new configuration file relaid in classpath named coherence-cache-config.xml. A simple coherence-cache-config provide in the following:

If logging is enable for the application, we would see log messages as follows:
2008-05-12 10:56:19,079 INFO [org.hibernate.cfg.SettingsFactory] -
2008-05-12 10:56:19,079 INFO [org.hibernate.cfg.SettingsFactory] -
2008-05-12 10:56:19,079 INFO [org.hibernate.cfg.SettingsFactory] -
2008-05-12 10:56:19,266 INFO [org.hibernate.cfg.SettingsFactory] -
2008-05-12 10:56:19,266 INFO [org.hibernate.cfg.SettingsFactory] -
2008-05-12 10:56:19,266 INFO [org.hibernate.cfg.SettingsFactory] -
2008-05-12 10:56:19,282 INFO [org.hibernate.cfg.SettingsFactory] -
2008-05-12 10:56:19,282 INFO [org.hibernate.cfg.SettingsFactory] -
2008-05-12 10:56:19,282 INFO [org.hibernate.cfg.SettingsFactory] -
2008-05-12 10:56:19,282 INFO [org.hibernate.cfg.SettingsFactory] -
2008-05-12 10:56:19,282 INFO [org.hibernate.cfg.SettingsFactory] -
2008-05-12 10:56:19,329 INFO [org.hibernate.impl.SessionFactoryImpl] -
2008-05-12 10:56:19.547 Oracle Coherence 3.3.1/389 (thread=main, member=n/a): Loaded operational configuration from resource "jar:file:/C:/Documents%20and%20Settings/sahmed/.m2/repository/com/tangosol/coherence/coherence/1.0/coherence-1.0.jar!/tangosol-coherence.xml"
2008-05-12 10:56:19.547 Oracle Coherence 3.3.1/389 (thread=main, member=n/a): Loaded operational overrides from resource "jar:file:/C:/Documents%20and%20Settings/sahmed/.m2/repository/com/tangosol/coherence/coherence/1.0/coherence-1.0.jar!/tangosol-coherence-override-dev.xml"
2008-05-12 10:56:19.547 Oracle Coherence 3.3.1/389 (thread=main, member=n/a): Optional configuration override "/tangosol-coherence-override.xml" is not specified

Oracle Coherence Version 3.3.1/389
Grid Edition: Development mode
Copyright (c) 2000-2007 Oracle. All rights reserved.

2008-05-12 10:56:20.954 Oracle Coherence GE 3.3.1/389 (thread=Cluster, member=n/a): Service Cluster joined the cluster with senior service member n/a
2008-05-12 10:56:24.204 Oracle Coherence GE 3.3.1/389 (thread=Cluster, member=n/a): Created a new cluster with Member(Id=1, Timestamp=2008-05-12 10:56:20.625, Address=172.24.11.226:8088, MachineId=49122, Location=process:3396@s-ahmed, Edition=Grid Edition, Mode=Development, CpuCount=2, SocketCount=1) UID=0xAC180BE200000119DBEA6091BFE21F98
2008-05-12 10:56:24.250 Oracle Coherence GE 3.3.1/389 (thread=main, member=1): Loaded cache configuration from resource "jar:file:/C:/Documents%20and%20Settings/sahmed/.m2/repository/com/tangosol/coherence/hibernate/coherence-hibernate/1.0/coherence-hibernate-1.0.jar!/config/hibernate-cache-config.xml"
2008-05-12 10:56:24.532 Oracle Coherence GE 3.3.1/389 (thread=ReplicatedCache:HibernateReplicatedCache, member=1): Service HibernateReplicatedCache joined the cluster with senior service member 1
2008-05-12 10:56:25,000 INFO [org.hibernate.impl.SessionFactoryObjectFactory] -
2008-05-12 10:56:25,016 INFO [org.hibernate.cache.UpdateTimestampsCache] -
2008-05-12 10:56:25,016 INFO [org.hibernate.cache.StandardQueryCache] -
2008-05-12 10:56:25.157 Oracle Coherence GE 3.3.1/389 (thread=main, member=1): Loaded cache configuration from resource "file:/E:/WorkSpace/MyProjects/Coherence/coherence-test/target/classes/coherence-cache-config.xml"
entity cache items:SafeNamedCache: CacheHandler

A much more configurations detailed in the user guide.
Labels:

Comments

Post a Comment

Popular posts from this blog

8 things every developer should know about the Apache Ignite caching

Any technology, no matter how advanced it is, will not be able to solve your problems if you implement it improperly. Caching, precisely when it comes to the use of a distributed caching, can only accelerate your application with the proper use and configurations of it. From this point of view, Apache Ignite is no different, and there are a few steps to consider before using it in the production environment. In this article, we describe various technics that can help you to plan and adequately use of Apache Ignite as cutting-edge caching technology. Do proper capacity planning before using Ignite cluster. Do paperwork for understanding the size of the cache, number of CPUs or how many JVMs will be required. Let’s assume that you are using Hibernate as an ORM in 10 application servers and wish to use Ignite as an L2 cache. Calculate the total memory usages and the number of Ignite nodes you have to need for maintaining your SLA. An incorrect number of the Ignite nodes can become a b...
Post a Comment
Read more

Analyse with ANT - a sonar way

After the Javaone conference in Moscow, i have found some free hours to play with Sonar . Here is a quick steps to start analyzing with ANT projects. Sonar provides Analyze with ANT document to play around with ANT, i have just modify some parts. Here is it. 1) Download the Sonar Ant Task and put it in your ${ANT_HOME}/lib directory 2) Modify your ANT build.xml as follows: <?xml version = '1.0' encoding = 'windows-1251'?> <project name="abc" default="build" basedir="."> <!-- Define the Sonar task if this hasn't been done in a common script --> <taskdef uri="antlib:org.sonar.ant" resource="org/sonar/ant/antlib.xml"> <classpath path="E:\java\ant\1.8\apache-ant-1.8.0\lib" /> </taskdef> <!-- Out-of-the-box those parameters are optional --> <property name="sonar.jdbc.url" value="jdbc:oracle:thin:@xyz/sirius.xyz" /> <property na...
Post a Comment
Read more

Apache Ignite Baseline Topology by Examples

Ignite Baseline Topology or BLT represents a set of server nodes in the cluster that persists data on disk. Where, N1-2 and N5 server nodes are the member of the Ignite clusters with native persistence which enable data to persist on disk. N3-4 and N6 server nodes are the member of the Ignite cluster but not a part of the baseline topology. The nodes from the baseline topology are a regular server node, that store's data in memory and on the disk, and also participates in computing tasks. Ignite clusters can have different nodes that are not a part of the baseline topology such as: Server nodes that are not used Ignite native persistence to persist data on disk. Usually, they store data in memory or persists data to a 3rd party database or NoSQL. In the above equitation, node N3 or N4 might be one of them. Client nodes that are not stored shared data. To better understand the baseline topology concept, let’s start at the beginning and try to understand its goal and what ...
Post a Comment
Read more