April 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6563) If Infinispan is used as a provider for JCache using the remote approach it will not pick up the hotrod-client.properties

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6563?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6563: ----------------------------------- Fix Version/s: 9.0.0.Alpha2 9.0.0.Final > If Infinispan is used as a provider for JCache using the remote approach it will not pick up the hotrod-client.properties > ------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-6563 > URL: https://issues.jboss.org/browse/ISPN-6563 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 8.2.1.Final, 9.0.0.Alpha1 > Reporter: Wolf-Dieter Fink > Assignee: Galder Zamarreño > Fix For: 9.0.0.Alpha2, 9.0.0.Final > > > 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. > 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. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6563) If Infinispan is used as a provider for JCache using the remote approach it will not pick up the hotrod-client.properties

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6563?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6563: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4284 > If Infinispan is used as a provider for JCache using the remote approach it will not pick up the hotrod-client.properties > ------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-6563 > URL: https://issues.jboss.org/browse/ISPN-6563 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 8.2.1.Final, 9.0.0.Alpha1 > Reporter: Wolf-Dieter Fink > Assignee: Galder Zamarreño > Fix For: 9.0.0.Alpha2, 9.0.0.Final > > > 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. > 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. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6563) If Infinispan is used as a provider for JCache using the remote approach it will not pick up the hotrod-client.properties

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6563?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6563: ----------------------------------- Status: Open (was: New) > If Infinispan is used as a provider for JCache using the remote approach it will not pick up the hotrod-client.properties > ------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-6563 > URL: https://issues.jboss.org/browse/ISPN-6563 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 8.2.1.Final, 9.0.0.Alpha1 > Reporter: Wolf-Dieter Fink > Assignee: Galder Zamarreño > Fix For: 9.0.0.Alpha2, 9.0.0.Final > > > 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. > 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. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6563) If Infinispan is used as a provider for JCache using the remote approach it will not pick up the hotrod-client.properties

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-6563?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-6563: ----------------------------------- Affects Version/s: 8.2.1.Final > If Infinispan is used as a provider for JCache using the remote approach it will not pick up the hotrod-client.properties > ------------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-6563 > URL: https://issues.jboss.org/browse/ISPN-6563 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 8.2.1.Final, 9.0.0.Alpha1 > Reporter: Wolf-Dieter Fink > Assignee: Galder Zamarreño > Fix For: 9.0.0.Alpha2, 9.0.0.Final > > > 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. > 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. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6563) If Infinispan is used as a provider for JCache using the remote approach it will not pick up the hotrod-client.properties

by Wolf-Dieter Fink (JIRA)

Wolf-Dieter Fink created ISPN-6563: -------------------------------------- Summary: If Infinispan is used as a provider for JCache using the remote approach it will not pick up the hotrod-client.properties Key: ISPN-6563 URL: https://issues.jboss.org/browse/ISPN-6563 Project: Infinispan Issue Type: Bug Components: Remote Protocols Affects Versions: 9.0.0.Alpha1 Reporter: Wolf-Dieter Fink Assignee: Galder Zamarreño 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. 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. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6562) CLI remoting doesn't work with WildFly 10

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6562?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6562: ---------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/4282, https://github.com/infinispan/infinispan/pull/4283 (was: https://github.com/infinispan/infinispan/pull/4282) > CLI remoting doesn't work with WildFly 10 > ----------------------------------------- > > Key: ISPN-6562 > URL: https://issues.jboss.org/browse/ISPN-6562 > Project: Infinispan > Issue Type: Bug > Components: CLI > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 8.2.2.Final, 9.0.0.Final > > > To connect to WildFly 10 we need to use the http variants of the service jmx urls. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6516) Update aesh to 0.66.4

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6516?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6516: ---------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/4282, https://github.com/infinispan/infinispan/pull/4283 (was: https://github.com/infinispan/infinispan/pull/4282) > Update aesh to 0.66.4 > --------------------- > > Key: ISPN-6516 > URL: https://issues.jboss.org/browse/ISPN-6516 > Project: Infinispan > Issue Type: Bug > Reporter: Vaclav Dedik > Assignee: Tristan Tarrant > > I believe this package (aesh) needs to be aligned to wildfly 10/eap 7, which uses 0.66.4/0.66.4.redhat-1. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6562) CLI remoting doesn't work with WildFly 10

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6562?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6562: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4282 > CLI remoting doesn't work with WildFly 10 > ----------------------------------------- > > Key: ISPN-6562 > URL: https://issues.jboss.org/browse/ISPN-6562 > Project: Infinispan > Issue Type: Bug > Components: CLI > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 8.2.2.Final, 9.0.0.Final > > > To connect to WildFly 10 we need to use the http variants of the service jmx urls. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6516) Update aesh to 0.66.4

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6516?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6516: ---------------------------------- Status: Open (was: New) > Update aesh to 0.66.4 > --------------------- > > Key: ISPN-6516 > URL: https://issues.jboss.org/browse/ISPN-6516 > Project: Infinispan > Issue Type: Bug > Reporter: Vaclav Dedik > Assignee: Tristan Tarrant > > I believe this package (aesh) needs to be aligned to wildfly 10/eap 7, which uses 0.66.4/0.66.4.redhat-1. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6516) Update aesh to 0.66.4

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-6516?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-6516: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4282 > Update aesh to 0.66.4 > --------------------- > > Key: ISPN-6516 > URL: https://issues.jboss.org/browse/ISPN-6516 > Project: Infinispan > Issue Type: Bug > Reporter: Vaclav Dedik > Assignee: Tristan Tarrant > > I believe this package (aesh) needs to be aligned to wildfly 10/eap 7, which uses 0.66.4/0.66.4.redhat-1. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2016