Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hazelcast 2.4 & Hibernate 3.6.6 #339

Closed
schdai opened this issue Oct 28, 2012 · 3 comments

Comments

Projects
None yet
2 participants
@schdai
Copy link

commented Oct 28, 2012

I'm usiing Hazelcast 2.4 as Hiberate 3.6.6's second cache. According to Hazelcast manual, I annotate an entity @Cache(usage =CacheConcurrencyStrategy.READ_WRITE,region="SSM") , an error occured "UnsupportedOperationException " when call getConfig() during startup in my webapp. But when I use NONSTRICT_READ_WRITE as CacheConcurrencyStrategy, it works. what's the problem?

@mdogan

This comment has been minimized.

Copy link
Member

commented Oct 30, 2012

Do you use native client (hibernate.cache.hazelcast.use_native_client =
true)?

@mmdogan

@schdai

This comment has been minimized.

Copy link
Author

commented Nov 4, 2012

yes. this is part of my conf. in /META-INF/persistence.xml about second level cache

< property name="hibernate.cache.use_second_level_cache" value="true"/>
<property name="hibernate.cache.use_query_cache" value="true" />
<property name="hibernate.cache.use_minimal_puts" value="true"/>
<property name="hibernate.cache.hazelcast.use_native_client" value="true"/>
<property name="hibernate.cache.hazelcast.native_client_address" value="192.168.12.201"/<
<property name="hibernate.cache.hazelcast.native_client_group" value="devdev"/>
<property name="hibernate.cache.hazelcast.native_client_password" value="dev-passpass"/>
<property name="hibernate.cache.region.factory_class" value="com.hazelcast.hibernate.HazelcastCacheRegionFactory"/>

and what's the problem? Anyone knows the solution ?

@ghost ghost assigned mdogan Nov 6, 2012

@mdogan

This comment has been minimized.

Copy link
Member

commented Nov 6, 2012

This is a bug while using native client. Module needs config of cluster to
decide timeout parameter but native client can't access config. We should
fix this.

@mmdogan

@mdogan mdogan closed this in 42292bb Nov 6, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.