[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-2522) Cache Provider implementation for IBM WebSphere's dynamic cache

[prasenjit B (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_28003 ] 

prasenjit B commented on HHH-2522:
----------------------------------

Hi ,
I have seen your post on Cache Provider implementation for IBM WebSphere's dynamic cache
I am new to hibernate and currently working on one engagement with WAS 6.1.

The enterprise application is built on WAS 6.1 cluster (horizontal) with two nodes and the Hibernate 3.2.5 is used for the persistence .We have tried CMTTransactionFactory and webSphereExtendedJTATransation factory initially but the save and update operations are throwing some challenges as the Container managed transaction is not been synchronized with the persistence layer and we are getting an error "Could not register synchronization for container transaction" from Hibernate.

However the following configuration is supported by the application environment.

<session-factory>
<property name="hibernate.session_factory_name">
   HibernateSessionFactory
  </property>
  <property name="hibernate.transaction.factory_class">
   org.hibernate.transaction.JTATransactionFactory
  </property>
  <property name="hibernate.transaction.flush_before_completion">true</property> 
  <property
   name="org.hibernate.transaction.JTATransactionFactory">
   org.hibernate.transaction.WebSphereTransactionManagerLookup
  </property>
  <property name="hibernate.transaction.manager_lookup_class">
   org.hibernate.transaction.WebSphereTransactionManagerLookup
  </property>

The configuration was OK in the stand-alone server in the development .But when we deploy the same in the cluster ,the application  started showing the old values/transaction details , although the  individual data elements are updated in the back-end Database without any problem.

According to me ,we might be facing some caching related issues as we have not configured the second level cache for Hibernate.

Your article has given me a pointer to resolve the issues.For this implementation I have changed the package from package org.hibernate.cache to com.ibm.hb.cache .would there be any problem?

I would therefore be grateful if you let me know what change do I need to do for the HBM and the CFG files.

> Cache Provider implementation for IBM WebSphere's dynamic cache
> ---------------------------------------------------------------
>
>                 Key: HHH-2522
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2522
>             Project: Hibernate3
>          Issue Type: New Feature
>          Components: core
>    Affects Versions: 3.2.3
>         Environment: Hibernate 3.2, IBM WebSphere Application Server version 5.x and 6.x
>            Reporter: Joris Kuipers
>            Priority: Minor
>         Attachments: WebSphereCache.java, WebSphereCacheProvider.java
>
>
> 2nd level cache implementation that uses WebSphere's dynamic cache feature as its backing implementation. 
> Using such an implementation is suggested by IBM in articles like http://www-128.ibm.com/developerworks/websphere/techjournal/0609_alcott/0609_alcott.html, but I couldn't find an existing implementation. Therefore, I wrote my own.
> I briefly documented the usage in the JavaDoc of the Provider implementation.
> Info in the dynamic cache itself can be found here:
> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/tdyn_distmap.html

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira