Bug 1332936

Summary: If Infinispan is used as a provider for JCache using the remote approach it will not pick up the hotrod-client.properties
Product: [JBoss] JBoss Data Grid 6 Reporter: wfink
Component: unspecifiedAssignee: wfink
Status: CLOSED UPSTREAM QA Contact: Martin Gencur <mgencur>
Severity: high Docs Contact:
Priority: high    
Version: 6.5.0, 6.6.0, 6.5.1CC: jdg-bugs, vjuranek
Target Milestone: ER1   
Target Release: 6.6.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-02-10 03:48:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1309749, 1338942, 1357934    

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.

Comment 3 Red Hat Bugzilla 2025-02-10 03:48:59 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.