June 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11964) WARN about unknown cache encoding

by Gustavo Fernandes (Jira)

Gustavo Fernandes created ISPN-11964: ---------------------------------------- Summary: WARN about unknown cache encoding Key: ISPN-11964 URL: https://issues.redhat.com/browse/ISPN-11964 Project: Infinispan Issue Type: Bug Components: Core, Server Affects Versions: 11.0.0.CR1 Reporter: Gustavo Fernandes Assignee: Gustavo Fernandes Fix For: 11.0.0.Final A special MediaType ''application/unknown" is used when the cache hasn't an <encoding> configuration and its encoding cannot be guessed. For 11.0.0.Final, this should result in a WARNING since conversions with unknown format depends on user marshaller and can be done in a best effort basis -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11963) Scattered cache putMap should use batch method instead of per key

by Will Burns (Jira)

Will Burns created ISPN-11963: --------------------------------- Summary: Scattered cache putMap should use batch method instead of per key Key: ISPN-11963 URL: https://issues.redhat.com/browse/ISPN-11963 Project: Infinispan Issue Type: Bug Affects Versions: 10.1.8.Final Reporter: Will Burns The scattered cache ScatteredCacheWriterInterceptor invokes the PersistenceManager writeToAllNonTxStores for each key. We should instead use the batch operations, which should be more efficient and properly support updating the write count. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11951) Component annotation processor should use javax.annotation.processing.Generated

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-11951?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-11951: -------------------------------- Fix Version/s: (was: 11.0.0.Final) > Component annotation processor should use javax.annotation.processing.Generated > ------------------------------------------------------------------------------- > > Key: ISPN-11951 > URL: https://issues.redhat.com/browse/ISPN-11951 > Project: Infinispan > Issue Type: Task > Affects Versions: 11.0.0.CR1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > > The component annotation processor currently uses {{javax.annotation.Generated}} in the source files. Since the annotation only has source retention, we can switch to the JDK 9+ {{javax.annotation.processing.Generated}} annotation and remove the {{javax.annotation-api-1.3.1}} dependency. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11951) Component annotation processor should use javax.annotation.processing.Generated

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-11951?page=com.atlassian.jira.plugi... ] Dan Berindei commented on ISPN-11951: ------------------------------------- I gave it a try, but the Maven compiler can't find the new {{Generated}} class, presumably because of {code:xml} <release>8</release> {code} Looks like we'll have to postpone this until we stop supporting Java 8. > Component annotation processor should use javax.annotation.processing.Generated > ------------------------------------------------------------------------------- > > Key: ISPN-11951 > URL: https://issues.redhat.com/browse/ISPN-11951 > Project: Infinispan > Issue Type: Task > Affects Versions: 11.0.0.CR1 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > > The component annotation processor currently uses {{javax.annotation.Generated}} in the source files. Since the annotation only has source retention, we can switch to the JDK 9+ {{javax.annotation.processing.Generated}} annotation and remove the {{javax.annotation-api-1.3.1}} dependency. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11962) Remove unused encoders

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/ISPN-11962?page=com.atlassian.jira.plugi... ] Dan Berindei updated ISPN-11962: -------------------------------- Component/s: Core > Remove unused encoders > ---------------------- > > Key: ISPN-11962 > URL: https://issues.redhat.com/browse/ISPN-11962 > Project: Infinispan > Issue Type: Sub-task > Components: Core > Reporter: Dan Berindei > Priority: Major > > Marshaller-based encoders are no longer used, and have been deprecated with ISPN-11901. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11962) Remove unused encoders

by Dan Berindei (Jira)

Dan Berindei created ISPN-11962: ----------------------------------- Summary: Remove unused encoders Key: ISPN-11962 URL: https://issues.redhat.com/browse/ISPN-11962 Project: Infinispan Issue Type: Sub-task Reporter: Dan Berindei Marshaller-based encoders are no longer used, and have been deprecated with ISPN-11901. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11961) DefaultIracManager should handle ImmutableSet

by Pedro Ruivo (Jira)

Pedro Ruivo created ISPN-11961: ---------------------------------- Summary: DefaultIracManager should handle ImmutableSet Key: ISPN-11961 URL: https://issues.redhat.com/browse/ISPN-11961 Project: Infinispan Issue Type: Bug Components: Cross-Site Replication Affects Versions: 11.0.0.CR1 Reporter: Pedro Ruivo Assignee: Pedro Ruivo Fix For: 11.0.0.Final I forgot there are immutable {{Intset}} implementation and {{IntSet.from()}} can return one of those instances. If that is the case, bad things happen... {code} Caused by: java.lang.UnsupportedOperationException: RangeSet is immutable at org.infinispan.commons.util.RangeSet.removeAll(RangeSet.java:156) at org.infinispan.xsite.irac.DefaultIracManager.onTopologyUpdate(DefaultIracManager.java:211) at org.infinispan.statetransfer.StateTransferManagerImpl.doTopologyUpdate(StateTransferManagerImpl.java:189) {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11642) Remote JCacheManager doesn't apply configuration from URI

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11642?page=com.atlassian.jira.plugi... ] Tristan Tarrant commented on ISPN-11642: ---------------------------------------- [~nmittles] I've just created a pull-request for ISPN-11960 which allows the use of wildcard globbing, {{.}} in cache names and externalizing the XML to a separate file. I hope this satisfies your requirements. > Remote JCacheManager doesn't apply configuration from URI > --------------------------------------------------------- > > Key: ISPN-11642 > URL: https://issues.redhat.com/browse/ISPN-11642 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 10.1.6.Final > Reporter: Nathan Mittlestat > Assignee: Tristan Tarrant > Priority: Major > Fix For: 11.0.0.Dev05, 10.1.7.Final > > > Our project is using JCache API's backed by Infinspan. This is a client-server scenario where we are configuring the Hot Rod Java Client to connect to an Infinispan server. > We are using _javax.cache.spi.CachingProvider.getCacheManager(URI, ClassLoader, Properties)_ to obtain a _CacheManager_. The URI passed points to an infinispan XML that specifies replicated-cache-configuration as part of the configuration. However the cache created from _CacheManager.createCache()_ ends up being a local cache. This proves to be a problem when connecting to a cluster of Infinispan servers, as when other connections attempt to utilize the cached data, they connect to a different Infinispn sever that doesn't have the cached data. We have verified the XML file pointed to by the URI is on the ClassLoader passed to the _CacheManager_, and still see the same results. > When we attempt this same scenario using embedded mode instead of client server mode, the configuration in the URI is applied correctly. We have even been able to create a cluster of embedded Infinispan servers via JGroups and confirmed the caches are replicated and not local. > We have also attempted this scenario using Infinispan's proprietary APIs: > _RemoteCacheManager.administration().getOrCreateCache(String name, BasicConfiguration configuration)_ > The configuration object passed to _RemoteCacheManagerAdmin.getOrCreateCache()_ loads the same Infinispan XML configuration used in the failing remote JCache scenario (as a _XMlStringConfiguration_ object). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11960) RemoteCache configuration enhancements (wildcards, . in name, URI for config)

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11960?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11960: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8424 > RemoteCache configuration enhancements (wildcards, . in name, URI for config) > ----------------------------------------------------------------------------- > > Key: ISPN-11960 > URL: https://issues.redhat.com/browse/ISPN-11960 > Project: Infinispan > Issue Type: Enhancement > Components: Hot Rod > Affects Versions: 11.0.0.CR1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 11.0.0.Final > > > It should be possible to define remote cache names using wildcard globbing {{*}} so that configuration apply to all cache names which match. > Additionally we should be able to support cache names containing {{.}} characters in the declarative configuration. In this case names should be enclosed in square brackets, e.g {{[example.MyCache]}} > Since passing a cache configuration in XML is cumbersome, we should support passing a URI pointing to a separate file. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11960) RemoteCache configuration enhancements (wildcards, . in name, URI for config)

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11960?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11960: ----------------------------------- Status: Open (was: New) > RemoteCache configuration enhancements (wildcards, . in name, URI for config) > ----------------------------------------------------------------------------- > > Key: ISPN-11960 > URL: https://issues.redhat.com/browse/ISPN-11960 > Project: Infinispan > Issue Type: Enhancement > Components: Hot Rod > Affects Versions: 11.0.0.CR1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 11.0.0.Final > > > It should be possible to define remote cache names using wildcard globbing {{*}} so that configuration apply to all cache names which match. > Additionally we should be able to support cache names containing {{.}} characters in the declarative configuration. In this case names should be enclosed in square brackets, e.g {{[example.MyCache]}} > Since passing a cache configuration in XML is cumbersome, we should support passing a URI pointing to a separate file. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2020