Bug 1332936 - If Infinispan is used as a provider for JCache using the remote approach it will not pick up the hotrod-client.properties
Summary: If Infinispan is used as a provider for JCache using the remote approach it w...
Keywords:
Status: VERIFIED
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: unspecified
Version: 6.5.0,6.6.0,6.5.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ER1
: 6.6.1
Assignee: wfink
QA Contact: Martin Gencur
URL:
Whiteboard:
Depends On:
Blocks: 1309749 1338942 1357934
TreeView+ depends on / blocked
 
Reported: 2016-05-04 11:57 UTC by wfink
Modified: 2018-01-29 16:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ISPN-6563 0 Major Resolved If Infinispan is used as a provider for JCache using the remote approach it will not pick up the hotrod-client.propertie... 2017-06-01 22:04:29 UTC
Red Hat Knowledge Base (Solution) 2303381 0 None None None 2016-05-09 18:09:41 UTC

Description wfink 2016-05-04 11:57:58 UTC
f an application use the javax.cache JCache API together with the infinispan-jcache-remote library the CacheManager is created with defaults.
But it is expected that the hotrod-client.properties are used to configure the remote connection.

The code is like this:
{
 import javax.cache.*;
 ...
 CachingProvider jcacheProvider = Caching.getCachingProvider();
 CacheManager cacheManager = jcacheProvider.getCacheManager();
}

The org.infinispan.jcache.AbstractJCachingProvider use the org.infinispan.jcache.remote.CacheManger but does not provide properties.

Therefor the CacheManager is constructed with the default of localhost:11222 as the configuration is not loaded from the properties file.


Note You need to log in before you can comment on or make changes to this bug.