Bug 768975 - Cannot use ClusterCacheStore with EDG
Summary: Cannot use ClusterCacheStore with EDG
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: unspecified
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Tristan Tarrant
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-19 15:18 UTC by Martin Gencur
Modified: 2012-03-16 18:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-26 12:51:07 UTC
Type: Bug

Attachments (Terms of Use)
ClassCastException (2.35 KB, text/plain)
2011-12-19 15:18 UTC, Martin Gencur 		no flags Details
Infinispan subsystem definition (953 bytes, text/plain)
2011-12-19 15:19 UTC, Martin Gencur 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker AS7-3100 0 None None None Never

Description Martin Gencur 2011-12-19 15:18:10 UTC 
Created attachment 548618 [details]
ClassCastException

Description of problem:

When starting EDG server with ClusterCacheStore definition, getting a java.lang.ClassCastException: class org.infinispan.loaders.cluster.ClusterCacheLoader

(whole exception attached)

The problem is that Infinispan subsystem in JBossAS expects the cache store to be an implementation of CacheStore interface. However, ClusterCacheLoader does not implement it.

I used the following configuration snippet to configure Infinispan subsystem: (attached in a file).

There are tests for ClusterCacheStore in EDG: https://svn.devel.redhat.com/repos/jboss-qa/edg/edg-functional-tests/trunk/cluster-cache-store
Comment 1 Martin Gencur 2011-12-19 15:19:36 UTC 
Created attachment 548619 [details]
Infinispan subsystem definition
Comment 2 Martin Gencur 2012-01-26 12:51:07 UTC 
This was already resolved in related AS7-3100 and is working well in EDG now.
Note You need to log in before you can comment on or make changes to this bug.