November 2019 - infinispan-issues

[JBoss JIRA] (ISPN-10848) Change site status only after failures

by Pedro Ruivo (Jira)

[ https://issues.jboss.org/browse/ISPN-10848?page=com.atlassian.jira.plugin... ] Pedro Ruivo closed ISPN-10848. ------------------------------ > Change site status only after failures > --------------------------------------- > > Key: ISPN-10848 > URL: https://issues.jboss.org/browse/ISPN-10848 > Project: Infinispan > Issue Type: Enhancement > Components: Cross-Site Replication > Affects Versions: 9.4.16.Final, 10.0.0.CR3 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 10.1.0.Beta1 > > > Currently, the site status is checked and updates before sending each write request. > However, it would be better to update the site's status only after a failure. > If the cluster becomes idle and the last cross-site requests fail, the site will be taken offline. Changing this, will keep the site online and only updates the status after it sent the request. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9163) RemoteCacheManagerAdmin#getOrCreateCache(...) fails to return an existing cache in case the template does not exist

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/ISPN-9163?page=com.atlassian.jira.plugin.... ] Work on ISPN-9163 stopped by Radoslav Husar. -------------------------------------------- > RemoteCacheManagerAdmin#getOrCreateCache(...) fails to return an existing cache in case the template does not exist > ------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-9163 > URL: https://issues.jboss.org/browse/ISPN-9163 > Project: Infinispan > Issue Type: Bug > Components: Hot Rod > Affects Versions: 9.2.3.Final, 9.3.0.Beta1 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > {{RemoteCacheManagerAdmin#getOrCreateCache(...)}} fails to return an existing cache in case the template does not exist. This is because {{org.infinispan.globalstate.impl.GlobalConfigurationManagerImpl#getOrCreateCache}} first obtains the cache configuration and only then gets the cache. > While it could be argued, that this is by design, this does not seem practical but mainly violates the API contract defined by JavaDoc: > {code:java} > /** > * Retrieves a an existing cache on the remote server cluster. If it doesn't exist, it will be created using the > * specified template. > * > * @param name the name of the cache to create > * @param template the template to use for the cache. If null, the configuration marked as default on the server > * will be used > * @return the cache > * @throws HotRodClientException > */ > @Override > <K, V> RemoteCache<K, V> getOrCreateCache(String name, String template) throws HotRodClientException; > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9167) RemoteCacheManagerAdmin#getOrCreateCache(..., null) on a cache container which does not have default cache should fail

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/ISPN-9167?page=com.atlassian.jira.plugin.... ] Work on ISPN-9167 stopped by Radoslav Husar. -------------------------------------------- > RemoteCacheManagerAdmin#getOrCreateCache(..., null) on a cache container which does not have default cache should fail > ---------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-9167 > URL: https://issues.jboss.org/browse/ISPN-9167 > Project: Infinispan > Issue Type: Bug > Components: Hot Rod, Server > Affects Versions: 9.2.3.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > > The current code defaults to a local cache if the default cache is not defined > {code:java} > configuration = cacheManager.getDefaultCacheConfiguration(); > if (configuration == null) { > configuration = new ConfigurationBuilder().build(); > } > {code} > which is very unlikely it would be the intended configuration. This should rather fail fast. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10826) Fix GlobalXSiteAdminOpsTest failures

by Pedro Ruivo (Jira)

[ https://issues.jboss.org/browse/ISPN-10826?page=com.atlassian.jira.plugin... ] Pedro Ruivo closed ISPN-10826. ------------------------------ > Fix GlobalXSiteAdminOpsTest failures > ------------------------------------ > > Key: ISPN-10826 > URL: https://issues.jboss.org/browse/ISPN-10826 > Project: Infinispan > Issue Type: Bug > Components: Cross-Site Replication > Affects Versions: 9.4.16.Final > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 9.4.17.Final > > > Note. it only affects 9.4.x -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9167) RemoteCacheManagerAdmin#getOrCreateCache(..., null) on a cache container which does not have default cache should fail

by Radoslav Husar (Jira)

[ https://issues.jboss.org/browse/ISPN-9167?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated ISPN-9167: --------------------------------- Affects Version/s: 9.2.3.Final > RemoteCacheManagerAdmin#getOrCreateCache(..., null) on a cache container which does not have default cache should fail > ---------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-9167 > URL: https://issues.jboss.org/browse/ISPN-9167 > Project: Infinispan > Issue Type: Bug > Components: Hot Rod, Server > Affects Versions: 9.2.3.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > > The current code defaults to a local cache if the default cache is not defined > {code:java} > configuration = cacheManager.getDefaultCacheConfiguration(); > if (configuration == null) { > configuration = new ConfigurationBuilder().build(); > } > {code} > which is very unlikely it would be the intended configuration. This should rather fail fast. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10972) REST caches list order should be stable

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10972?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10972: ----------------------------------- Sprint: DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #36) > REST caches list order should be stable > --------------------------------------- > > Key: ISPN-10972 > URL: https://issues.jboss.org/browse/ISPN-10972 > Project: Infinispan > Issue Type: Enhancement > Components: REST > Affects Versions: 10.1.0.Beta1 > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Major > Labels: console, rest > Fix For: 10.1.0.Final > > > Today the caches resource displays the list of caches and the result is not ordered so it's not stable. Display ordered by name -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10960) Add SerializationContextInitializer lookup to Server Extensions

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10960?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10960: ----------------------------------- Sprint: DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #36) > Add SerializationContextInitializer lookup to Server Extensions > --------------------------------------------------------------- > > Key: ISPN-10960 > URL: https://issues.jboss.org/browse/ISPN-10960 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Affects Versions: 10.0.1.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.1.0.Final > > > To utilise a SerializationContextInitializer on the server it's necessary for the implementation to be specified via the xml configuration. However, it should be possible to utilise the Server's Extensions to automatically load and configure any {{SerializationContextInitializer}} implementations that are placed on the servers classpath by the user. This will remove a configuration step when utilising the normal server, but will have the bigggest impact on the server image, as it will be possible for users to mount a volume with the jar(s) containing the desired {{SerializationContextInitializer}} implementations without changing the xml. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10966) StateTransferLockImpl.topologyFuture should complete exceptionally after stop

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10966?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10966: ----------------------------------- Sprint: DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #36) > StateTransferLockImpl.topologyFuture should complete exceptionally after stop > ----------------------------------------------------------------------------- > > Key: ISPN-10966 > URL: https://issues.jboss.org/browse/ISPN-10966 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 10.1.0.Beta1 > Reporter: dan.berindei > Assignee: dan.berindei > Priority: Major > Fix For: 10.1.0.CR1 > > > When a cache is shutting down, the topology id is increased to {{Integer.MAX_VALUE}}. > If a component uses {{StateTransferLock.topologyUpdate()}} to retry in the next topology and doesn't explicitly check if the cache is running, it could retry 2^^31 times before giving up. > This causes {{StreamDistPartitionHandlingTest.clearContent}} to hang randomly: > {noformat} > 11:58:14,655 TRACE (testng-Test:[]) [StateTransferLockImpl] Signalling topology 2147483647 is installed > 11:58:14,655 TRACE (testng-Test:[]) [ClusterPublisherManagerImpl] Segments {0-3 8 12 21-22 25-26 29 31 35 37-39 41-42 47 52-54 56-58 73-75 77 85 93-95 97-99 104-105 107 118 121-122 126-129 133 140 145 149 151-154 161 167-168 170-171 177-178 186 189-190 195-196 199-205 212-214 216-217 221-222 224 226-227 232-233 243-244} not completed - retrying > 11:58:14,655 TRACE (testng-Test:[]) [ClusterPublisherManagerImpl] Retrying segments {0-3 8 12 21-22 25-26 29 31 35 37-39 41-42 47 52-54 56-58 73-75 77 85 93-95 97-99 104-105 107 118 121-122 126-129 133 140 145 149 151-154 161 167-168 170-171 177-178 186 189-190 195-196 199-205 212-214 216-217 221-222 224 226-227 232-233 243-244} after 16 is installed for Test-NodeA-12596#7046 > ... > 12:03:16,127 TRACE (testng-Test:[]) [ClusterPublisherManagerImpl] Segments {0-3 8 12 21-22 25-26 29 31 35 37-39 41-42 47 52-54 56-58 73-75 77 85 93-95 97-99 104-105 107 118 121-122 126-129 133 140 145 149 151-154 161 167-168 170-171 177-178 186 189-190 195-196 199-205 212-214 216-217 221-222 224 226-227 232-233 243-244} not completed - retrying > 12:03:16,127 TRACE (testng-Test:[]) [ClusterPublisherManagerImpl] Retrying segments {0-3 8 12 21-22 25-26 29 31 35 37-39 41-42 47 52-54 56-58 73-75 77 85 93-95 97-99 104-105 107 118 121-122 126-129 133 140 145 149 151-154 161 167-168 170-171 177-178 186 189-190 195-196 199-205 212-214 216-217 221-222 224 226-227 232-233 243-244} after 16 is installed for Test-NodeA-12596#7046 > ... > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10952) InfinispanExtenionIT fails

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10952?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10952: ----------------------------------- Sprint: DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #36) > InfinispanExtenionIT fails > --------------------------- > > Key: ISPN-10952 > URL: https://issues.jboss.org/browse/ISPN-10952 > Project: Infinispan > Issue Type: Bug > Components: Integration , Test Suite > Reporter: Tristan Tarrant > Assignee: Will Burns > Priority: Major > Fix For: 10.1.0.Beta1 > > > {{ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.datagrid-infinispan.infinispan_container: org.jboss.msc.service.StartException in service jboss.datagrid-infinispan.infinispan_container: Failed to start service > at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1731) > at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559) > at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) > at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) > at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) > at java.base/java.lang.Thread.run(Thread.java:834) > Caused by: org.infinispan.commons.CacheException: Unable to construct a GlobalComponentRegistry! > at org.infinispan.core:ispn-10.0@10.1.0-SNAPSHOT//org.infinispan.factories.GlobalComponentRegistry.<init>(GlobalComponentRegistry.java:170) > at org.infinispan.core:ispn-10.0@10.1.0-SNAPSHOT//org.infinispan.manager.DefaultCacheManager.<init>(DefaultCacheManager.java:267) > at org.infinispan.extension:ispn-10.0@10.1.0-SNAPSHOT//org.jboss.as.clustering.infinispan.DefaultCacheContainer.<init>(DefaultCacheContainer.java:47) > at org.infinispan.extension:ispn-10.0@10.1.0-SNAPSHOT//org.jboss.as.clustering.infinispan.subsystem.CacheContainerBuilder.start(CacheContainerBuilder.java:97) > at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739) > at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701) > ... 6 more > Caused by: org.infinispan.commons.CacheConfigurationException: Failed to construct component org.infinispan.executors.async, path org.infinispan.executors.async > << org.infinispan.notifications.cachemanagerlistener.CacheManagerNotifier > at org.infinispan.core:ispn-10.0@10.1.0-SNAPSHOT//org.infinispan.factories.impl.BasicComponentRegistryImpl.doInstantiateWrapper(BasicComponentRegistryImpl.java:189) > at org.infinispan.core:ispn-10.0@10.1.0-SNAPSHOT//org.infinispan.factories.impl.BasicComponentRegistryImpl.instantiateWrapper(BasicComponentRegistryImpl.java:176) > at org.infinispan.core:ispn-10.0@10.1.0-SNAPSHOT//org.infinispan.factories.impl.BasicComponentRegistryImpl.getComponent0(BasicComponentRegistryImpl.java:141) > at org.infinispan.core:ispn-10.0@10.1.0-SNAPSHOT//org.infinispan.factories.impl.WireContext.get(WireContext.java:20) > at org.infinispan.core:ispn-10.0@10.1.0-SNAPSHOT//org.infinispan.notifications.impl.CorePackageImpl$1.wire(CorePackageImpl.java:27) > at org.infinispan.core:ispn-10.0@10.1.0-SNAPSHOT//org.infinispan.notifications.impl.CorePackageImpl$1.wire(CorePackageImpl.java:24) > at org.infinispan.core:ispn-10.0@10.1.0-SNAPSHOT//org.infinispan.factories.impl.BasicComponentRegistryImpl.invokeInjection(BasicComponentRegistryImpl.java:334) > at org.infinispan.core:ispn-10.0@10.1.0-SNAPSHOT//org.infinispan.factories.impl.BasicComponentRegistryImpl.invokeInjection(BasicComponentRegistryImpl.java:342) > at org.infinispan.core:ispn-10.0@10.1.0-SNAPSHOT//org.infinispan.factories.impl.BasicComponentRegistryImpl.doWireWrapper(BasicComponentRegistryImpl.java:231) > at org.infinispan.core:ispn-10.0@10.1.0-SNAPSHOT//org.infinispan.factories.impl.BasicComponentRegistryImpl.wireWrapper(BasicComponentRegistryImpl.java:212) > at org.infinispan.core:ispn-10.0@10.1.0-SNAPSHOT//org.infinispan.factories.impl.BasicComponentRegistryImpl.registerComponent(BasicComponentRegistryImpl.java:371) > at org.infinispan.core:ispn-10.0@10.1.0-SNAPSHOT//org.infinispan.factories.GlobalComponentRegistry.<init>(GlobalComponentRegistry.java:123) > ... 11 more > Caused by: org.infinispan.commons.CacheConfigurationException: ISPN000566: Thread Pool Factory org.infinispan.executors.async is blocking, but this pool requires non blocking threads > at org.infinispan.core:ispn-10.0@10.1.0-SNAPSHOT//org.infinispan.factories.NamedExecutorsFactory.createExecutorService(NamedExecutorsFactory.java:104) > at org.infinispan.core:ispn-10.0@10.1.0-SNAPSHOT//org.infinispan.factories.NamedExecutorsFactory.construct(NamedExecutorsFactory.java:75) > at org.infinispan.core:ispn-10.0@10.1.0-SNAPSHOT//org.infinispan.factories.impl.BasicComponentRegistryImpl.doInstantiateWrapper(BasicComponentRegistryImpl.java:186) > ... 22 more > }} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10956) GlobalConfigurationBuilder.addModule() should be idempotent

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10956?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10956: ----------------------------------- Sprint: DataGrid Sprint #36, DataGrid Sprint #37 (was: DataGrid Sprint #36) > GlobalConfigurationBuilder.addModule() should be idempotent > ----------------------------------------------------------- > > Key: ISPN-10956 > URL: https://issues.jboss.org/browse/ISPN-10956 > Project: Infinispan > Issue Type: Bug > Components: Configuration, Core > Affects Versions: 10.0.1.Final > Reporter: dan.berindei > Assignee: dan.berindei > Priority: Major > Fix For: 10.1.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2019