Uploaded image for project: 'Red Hat Data Grid'
  1. Red Hat Data Grid
  2. JDG-282

If Infinispan is used as a provider for JCache using the remote approach it will not pick up the hotrod-client.properties

XMLWordPrintable

    • Hide

      A simple class which access a remote server via JCache API.

      import javax.cache.*;
      ...
      public void main(String[] args) {
      CachingProvider jcacheProvider = Caching.getCachingProvider();
      CacheManager cacheManager = jcacheProvider.getCacheManager();
      ...
      }

      If no server is started it will fail to connect localhost:11222 even if a hotrod-client.properties is added with a different list of servers, i.e.
      infinispan.client.hotrod.server_list = localhost:11221

      Show
      A simple class which access a remote server via JCache API. import javax.cache.*; ... public void main(String[] args) { CachingProvider jcacheProvider = Caching.getCachingProvider(); CacheManager cacheManager = jcacheProvider.getCacheManager(); ... } If no server is started it will fail to connect localhost:11222 even if a hotrod-client.properties is added with a different list of servers, i.e. infinispan.client.hotrod.server_list = localhost:11221

      If 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.

              rhn-support-wfink Wolf Fink
              rhn-support-wfink Wolf Fink
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: