November 2018 - infinispan-issues

[JBoss JIRA] (ISPN-9132) Migrate from the security vault to credential store

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9132?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9132: ---------------------------------- Fix Version/s: 9.4.4.Final (was: 9.4.3.Final) > Migrate from the security vault to credential store > --------------------------------------------------- > > Key: ISPN-9132 > URL: https://issues.jboss.org/browse/ISPN-9132 > Project: Infinispan > Issue Type: Enhancement > Components: Test Suite - Server > Affects Versions: 9.3.0.Alpha1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 9.4.4.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9131) Migrate all tests to PKCS#12

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9131?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9131: ---------------------------------- Fix Version/s: 9.4.4.Final (was: 9.4.3.Final) > Migrate all tests to PKCS#12 > ---------------------------- > > Key: ISPN-9131 > URL: https://issues.jboss.org/browse/ISPN-9131 > Project: Infinispan > Issue Type: Enhancement > Components: Test Suite - Server > Affects Versions: 9.3.0.Alpha1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 9.4.4.Final > > > We should migrate our ssl configurations from the legacy security-realm to Elytron key-stores and ssl-contexts. https://docs.jboss.org/author/display/WFLY/Simple+SSL+Migration -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9124) Uncaught exception in CounterConfigurationManager.startCounterCache

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9124?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9124: ---------------------------------- Fix Version/s: 9.4.4.Final (was: 9.4.3.Final) > Uncaught exception in CounterConfigurationManager.startCounterCache > ------------------------------------------------------------------- > > Key: ISPN-9124 > URL: https://issues.jboss.org/browse/ISPN-9124 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Core > Affects Versions: 9.2.2.Final > Reporter: Dan Berindei > Priority: Major > Fix For: 9.4.4.Final > > > {{CounterConfigurationManager.startCounterCache}} starts the cache asynchronously, but a short test may stop the cache manager before the worker thread got to do anything. The worker thread doesn't catch the exception, so it's just logged on the console: > {noformat} > Exception in thread "async-thread--p132-t1" org.infinispan.IllegalLifecycleStateException: Cache container has been stopped and cannot be reused. Recreate the cache container. > at org.infinispan.manager.DefaultCacheManager.assertIsNotTerminated(DefaultCacheManager.java:951) > at org.infinispan.manager.DefaultCacheManager.internalGetCache(DefaultCacheManager.java:465) > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:461) > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:447) > at org.infinispan.counter.impl.manager.CounterConfigurationManager.lambda$startCounterCache$5(CounterConfigurationManager.java:230) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9587) Key Transformer registration via config

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9587?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9587: ---------------------------------- Fix Version/s: 9.4.4.Final (was: 9.4.3.Final) > Key Transformer registration via config > --------------------------------------- > > Key: ISPN-9587 > URL: https://issues.jboss.org/browse/ISPN-9587 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying, Remote Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Major > Fix For: 9.4.4.Final > > > Under indexing config element: > {code} > <key-transformers> > <key-transformer key="org.infinispan.query.test.CustomKey" transformer="org.infinispan.query.test.CustomTransformer"/> > </key-transformers> > {code} > and also via the config builder API. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9582) Lifespan/MaxIdle = 0 from Hot Rod behaviour is inconsistent with embedded

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9582?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9582: ---------------------------------- Fix Version/s: 9.4.4.Final (was: 9.4.3.Final) > Lifespan/MaxIdle = 0 from Hot Rod behaviour is inconsistent with embedded > ------------------------------------------------------------------------- > > Key: ISPN-9582 > URL: https://issues.jboss.org/browse/ISPN-9582 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.4.0.CR3 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 9.4.4.Final > > > In embedded mode, specifying 0 for lifespan or maxIdle results in immediate expiration. > In Hot Rod, however, 0 results in the entry using the default server-side expiration. This was done in order to not introduce a protocol change at the time. > The 2.2 protocol introduced timeunit support with special values for default and infinity. > We should therefore not override a user-specified value of 0 with "default". -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9578) Move HR wire docs to contributing guide

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9578?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9578: ---------------------------------- Fix Version/s: 9.4.4.Final (was: 9.4.3.Final) > Move HR wire docs to contributing guide > --------------------------------------- > > Key: ISPN-9578 > URL: https://issues.jboss.org/browse/ISPN-9578 > Project: Infinispan > Issue Type: Task > Components: Documentation-Core > Affects Versions: 9.4.0.CR3 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 9.4.4.Final > > > The Hot Rod wire protocol has no place in the user guide. It should be moved to the contributing guide. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9564) Align pom.xml order and versions

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9564?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9564: ---------------------------------- Fix Version/s: 9.4.4.Final (was: 9.4.3.Final) > Align pom.xml order and versions > -------------------------------- > > Key: ISPN-9564 > URL: https://issues.jboss.org/browse/ISPN-9564 > Project: Infinispan > Issue Type: Enhancement > Components: Build > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 9.4.4.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9555) ComponentRegistry should enforce that registered components implement the interface/contract

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9555?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9555: ---------------------------------- Fix Version/s: 9.4.4.Final (was: 9.4.3.Final) > ComponentRegistry should enforce that registered components implement the interface/contract > -------------------------------------------------------------------------------------------- > > Key: ISPN-9555 > URL: https://issues.jboss.org/browse/ISPN-9555 > Project: Infinispan > Issue Type: Bug > Components: Core > Reporter: Adrian Nistor > Assignee: Dan Berindei > Priority: Major > Fix For: 9.4.4.Final > > > ComponentRegistry.registerComponent(impl, interface) does not currently check that the impl really is assignable to the interface. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9513) Transformers registered via SearchManagerImplementor.registerKeyTransformer should be propagated in the cluster

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9513?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9513: ---------------------------------- Fix Version/s: 9.4.4.Final (was: 9.4.3.Final) > Transformers registered via SearchManagerImplementor.registerKeyTransformer should be propagated in the cluster > --------------------------------------------------------------------------------------------------------------- > > Key: ISPN-9513 > URL: https://issues.jboss.org/browse/ISPN-9513 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 5.2.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Priority: Major > Fix For: 9.4.4.Final > > > This can be achieved in a similar manner QueryKnownClasses is used to propagate indexed entities to other nodes. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9541) Module initialization is not thread-safe

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9541?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9541: ---------------------------------- Fix Version/s: 9.4.4.Final (was: 9.4.3.Final) > Module initialization is not thread-safe > ---------------------------------------- > > Key: ISPN-9541 > URL: https://issues.jboss.org/browse/ISPN-9541 > Project: Infinispan > Issue Type: Bug > Components: Core, Server > Affects Versions: 9.4.0.CR3 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 9.4.4.Final > > > In my ISPN-9127 fix I created a {{BasicComponentRegistry}} interface that represents a mostly-read-only collection of components. It has {{replaceComponent()}} method and a {{rewire()}} method for testing purposes, but it turns out modules were also relying on the ability to replace existing components in order to work. > Replacing global components is normally safe during the {{ModuleLifecycle.cacheManagerStarting()}}, because none of the components are started yet, so when a component starts later we can still start its dependencies first. But because some modules starts some global components, e.g. by calling {{manager.getCache(name)}}, that assumption breaks. > The {{infinispan-server-event-logger}} module is a bit more sneaky: it doesn't replace a component, instead it replaces the actual implementation of the event logger in the {{EventLogManager}} component. Events that happen before the module's {{cacheManagerStarting()}} or after {{cacheManagerStopping()}} will be silently dropped from the persistent event log. > I am investigating making the module a factory of factories. Instead of having a monolitic {{cacheManagerStarting()}} method, it could define a set of components that it can create, and a set of components that should be started before the cache manager is "running". We probably need a way to depend on other modules as well, maybe reusing the {{@Inject}} and {{@ComponentName}} annotations. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2018