October 2018 - infinispan-issues - Jboss List Archives

[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.2.Final (was: 9.4.1.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.2.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9161) Description of StateTransferManager attributes does not match the behaviour or show wrong content

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9161?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9161: ---------------------------------- Fix Version/s: 9.4.2.Final (was: 9.4.1.Final) > Description of StateTransferManager attributes does not match the behaviour or show wrong content > ------------------------------------------------------------------------------------------------- > > Key: ISPN-9161 > URL: https://issues.jboss.org/browse/ISPN-9161 > Project: Infinispan > Issue Type: Bug > Components: Core, Documentation-Core > Reporter: Wolf-Dieter Fink > Assignee: Dan Berindei > Priority: Major > Fix For: 9.4.2.Final > > Attachments: Screenshot from 2018-05-16 10-01-28.png > > > Current description is: > If true, the node has successfully joined the grid and is considered to hold state. If false, the join process is still in progress.. > But the behaviour is: > It doesn't wait for the initial state transfer, it just waits for the coordinator to send it a topology before joinComplete is set to TRUE -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 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.2.Final (was: 9.4.1.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.2.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, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9112) getCache() should not wait for the initial state transfer by default

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9112?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9112: ---------------------------------- Fix Version/s: 9.4.2.Final (was: 9.4.1.Final) > getCache() should not wait for the initial state transfer by default > -------------------------------------------------------------------- > > Key: ISPN-9112 > URL: https://issues.jboss.org/browse/ISPN-9112 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration, Core > Affects Versions: 9.2.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 9.4.2.Final > > > {{DefaultCacheManager.getCache(name)}} normally blocks until the local node becomes a full member of the consistent hash and the rebalance has finished. This can cause problems when rebalancing is disabled, either explicitly by the administrator, or implicitly because the cache is in degraded mode. > Blocking can be disabled with {{builder.clustering().stateTransfer().awaitInitialTransfer(false)}} ({{await-initial-transfer="false"}} in XML}}, but we should make the non-blocking behaviour the default. We should also deprecate the method and attribute to enable the blocking behaviour, and instead add a method to {{AdvancedCache}} to wait for the initial state transfer. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 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.2.Final (was: 9.4.1.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.2.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, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9101) EncryptProtocolIT.testEncryptProtocolRegistered random failures

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9101?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9101: ---------------------------------- Fix Version/s: 9.4.2.Final (was: 9.4.1.Final) > EncryptProtocolIT.testEncryptProtocolRegistered random failures > --------------------------------------------------------------- > > Key: ISPN-9101 > URL: https://issues.jboss.org/browse/ISPN-9101 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 9.2.1.Final > Reporter: Dan Berindei > Priority: Critical > Labels: testsuite_stability > Fix For: 9.4.2.Final > > > {noformat} > java.lang.RuntimeException: Could not retrieve HotRod host > at org.infinispan.server.test.security.jgroups.encrypt.EncryptProtocolIT.testEncryptProtocolRegistered(EncryptProtocolIT.java:63) > Caused by: java.lang.IllegalArgumentException: Could not retrieve attribute HostName on MBean jboss.datagrid-infinispan:type=Server,name=HotRod,component=Transport > at org.infinispan.server.test.security.jgroups.encrypt.EncryptProtocolIT.testEncryptProtocolRegistered(EncryptProtocolIT.java:63) > Caused by: javax.management.InstanceNotFoundException: jboss.datagrid-infinispan:type=Server,name=HotRod,component=Transport > {noformat} > The log shows this exception: > {noformat} > &amp#27;[0m&amp#27;[31m13:36:29,258 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.datagrid-jgroups.channel.cluster: org.jboss.msc.service.StartException in service jboss.datagrid-jgroups.channel.cluster: java.security.PrivilegedActionException: java.io.IOException: Invalid secret key format > at org.infinispan.server.jgroups.spi.service.ChannelBuilder.start(ChannelBuilder.java:79) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1714) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1693) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1540) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.security.PrivilegedActionException: java.io.IOException: Invalid secret key format > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:623) > at org.infinispan.server.jgroups.JChannelFactory.createChannel(JChannelFactory.java:104) > at org.infinispan.server.jgroups.spi.service.ChannelBuilder.start(ChannelBuilder.java:77) > ... 8 more > Caused by: java.io.IOException: Invalid secret key format > at com.sun.crypto.provider.JceKeyStore.engineLoad(JceKeyStore.java:856) > at java.security.KeyStore.load(KeyStore.java:1445) > at org.jgroups.protocols.SYM_ENCRYPT.readSecretKeyFromKeystore(SYM_ENCRYPT.java:97) > at org.jgroups.protocols.SYM_ENCRYPT.init(SYM_ENCRYPT.java:78) > at org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:840) > at org.jgroups.stack.ProtocolStack.setup(ProtocolStack.java:479) > at org.jgroups.JChannel.init(JChannel.java:992) > at org.jgroups.JChannel.<init>(JChannel.java:148) > at org.infinispan.server.jgroups.JChannelFactory.lambda$createChannel$0(JChannelFactory.java:103) > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:619) > ... 10 more > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 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.2.Final (was: 9.4.1.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.2.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, 5 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.2.Final (was: 9.4.1.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.2.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, 5 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.2.Final (was: 9.4.1.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.2.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 5 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.2.Final (was: 9.4.1.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.2.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, 5 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 October 2018