October 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-12384) Design Guidelines for Console Text Strings

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-12384?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-12384: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8742 > Design Guidelines for Console Text Strings > ------------------------------------------ > > Key: ISPN-12384 > URL: https://issues.redhat.com/browse/ISPN-12384 > Project: Infinispan > Issue Type: Enhancement > Components: Console, Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > Add guidelines for console text strings to the Contributor's Guide. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (ISPN-12184) Implicit authentication config stomps on explicit config

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12184?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12184: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8745 > Implicit authentication config stomps on explicit config > -------------------------------------------------------- > > Key: ISPN-12184 > URL: https://issues.redhat.com/browse/ISPN-12184 > Project: Infinispan > Issue Type: Bug > Components: Configuration, Server > Affects Versions: 12.0.0.Dev01 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 12.0.0.Dev05 > > > The server overwrites any explicit security configuration set on the individual protocols, including realm and mechanisms. > If these are set explicitly, they should be respected. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (ISPN-12184) Implicit authentication config stomps on explicit config

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-12184?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-12184: ----------------------------------- Status: Open (was: New) > Implicit authentication config stomps on explicit config > -------------------------------------------------------- > > Key: ISPN-12184 > URL: https://issues.redhat.com/browse/ISPN-12184 > Project: Infinispan > Issue Type: Bug > Components: Configuration, Server > Affects Versions: 12.0.0.Dev01 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 12.0.0.Dev05 > > > The server overwrites any explicit security configuration set on the individual protocols, including realm and mechanisms. > If these are set explicitly, they should be respected. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (ISPN-12391) Allow settings for different path for conf/data/log directory for the infinispan-server

by Wolf-Dieter Fink (Jira)

Wolf-Dieter Fink created ISPN-12391: --------------------------------------- Summary: Allow settings for different path for conf/data/log directory for the infinispan-server Key: ISPN-12391 URL: https://issues.redhat.com/browse/ISPN-12391 Project: Infinispan Issue Type: Feature Request Components: Configuration Reporter: Wolf-Dieter Fink To start a server with a different loction it is only possible to use "-s --server-root". There is no way to set it different for configuration/logging/data. It should be possible to set each to a different location -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (ISPN-12390) Allow settings for different path for conf/data/log directory for the infinispan-server

by Wolf-Dieter Fink (Jira)

[ https://issues.redhat.com/browse/ISPN-12390?page=com.atlassian.jira.plugi... ] Wolf-Dieter Fink commented on ISPN-12390: ----------------------------------------- There are references inside the infinispan.xml and log4j2.xml files 'infinispan.server.log.path', 'infinispan.server.config.path', 'infinispan.server.data.path' but these are not reliable working to override the path > Allow settings for different path for conf/data/log directory for the infinispan-server > --------------------------------------------------------------------------------------- > > Key: ISPN-12390 > URL: https://issues.redhat.com/browse/ISPN-12390 > Project: Infinispan > Issue Type: Feature Request > Components: Configuration > Reporter: Wolf-Dieter Fink > Priority: Major > > To start a server with a different loction it is only possible to use "-s --server-root". > There is no way to set it different for configuration/logging/data. > It should be possible to set each to a different location -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (ISPN-12390) Allow settings for different path for conf/data/log directory for the infinispan-server

by Wolf-Dieter Fink (Jira)

[ https://issues.redhat.com/browse/ISPN-12390?page=com.atlassian.jira.plugi... ] Wolf-Dieter Fink updated ISPN-12390: ------------------------------------ Summary: Allow settings for different path for conf/data/log directory for the infinispan-server (was: Allow settings for different path for conf/data/log directory) > Allow settings for different path for conf/data/log directory for the infinispan-server > --------------------------------------------------------------------------------------- > > Key: ISPN-12390 > URL: https://issues.redhat.com/browse/ISPN-12390 > Project: Infinispan > Issue Type: Feature Request > Components: Configuration > Reporter: Wolf-Dieter Fink > Priority: Major > > To start a server with a different loction it is only possible to use "-s --server-root". > There is no way to set it different for configuration/logging/data. > It should be possible to set each to a different location -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (ISPN-12390) Allow settings for different path for conf/data/log directory

by Wolf-Dieter Fink (Jira)

Wolf-Dieter Fink created ISPN-12390: --------------------------------------- Summary: Allow settings for different path for conf/data/log directory Key: ISPN-12390 URL: https://issues.redhat.com/browse/ISPN-12390 Project: Infinispan Issue Type: Feature Request Components: Configuration Reporter: Wolf-Dieter Fink To start a server with a different loction it is only possible to use "-s --server-root". There is no way to set it different for configuration/logging/data. It should be possible to set each to a different location -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (ISPN-8160) ClusteredCacheWithAffinityIndexManagerTxTest random failures with trace logging enabled

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-8160?page=com.atlassian.jira.plugin... ] Nistor Adrian closed ISPN-8160. ------------------------------- Resolution: Won't Fix No longer relevant, as affinity index manager is gone. > ClusteredCacheWithAffinityIndexManagerTxTest random failures with trace logging enabled > --------------------------------------------------------------------------------------- > > Key: ISPN-8160 > URL: https://issues.redhat.com/browse/ISPN-8160 > Project: Infinispan > Issue Type: Bug > Components: Test Suite > Affects Versions: 9.1.0.Final > Reporter: Dan Berindei > Assignee: Gustavo Fernandes > Priority: Critical > Labels: testsuite_stability > > The test usually passes when run by itself, but when run in parallel with other tests often getting one or more failures. The failing test method is not always the same, e.g. > {noformat} > 13:10:28,264 ERROR (testng-Test:[]) [TestSuiteProgress] Test failed: org.infinispan.query.blackbox.ClusteredCacheWithAffinityIndexManagerTxTest.testCompute > org.hibernate.search.exception.SearchException: Unable to reopen IndexReader > at org.hibernate.search.indexes.impl.SharingBufferReaderProvider$PerDirectoryLatestReader.refreshAndGet(SharingBufferReaderProvider.java:242) ~[hibernate-search-engine-5.8.0.Beta4.jar:5.8.0.Beta4] > at org.hibernate.search.indexes.impl.SharingBufferReaderProvider.openIndexReader(SharingBufferReaderProvider.java:73) ~[hibernate-search-engine-5.8.0.Beta4.jar:5.8.0.Beta4] > at org.hibernate.search.indexes.impl.SharingBufferReaderProvider.openIndexReader(SharingBufferReaderProvider.java:35) ~[hibernate-search-engine-5.8.0.Beta4.jar:5.8.0.Beta4] > at org.hibernate.search.reader.impl.ManagedMultiReader.createInstance(ManagedMultiReader.java:69) ~[hibernate-search-engine-5.8.0.Beta4.jar:5.8.0.Beta4] > at org.hibernate.search.reader.impl.MultiReaderFactory.openReader(MultiReaderFactory.java:48) ~[hibernate-search-engine-5.8.0.Beta4.jar:5.8.0.Beta4] > at org.hibernate.search.query.engine.impl.LuceneHSQuery.buildSearcher(LuceneHSQuery.java:475) ~[hibernate-search-engine-5.8.0.Beta4.jar:5.8.0.Beta4] > at org.hibernate.search.query.engine.impl.LuceneHSQuery.buildSearcher(LuceneHSQuery.java:399) ~[hibernate-search-engine-5.8.0.Beta4.jar:5.8.0.Beta4] > at org.hibernate.search.query.engine.impl.LuceneHSQuery.queryEntityInfos(LuceneHSQuery.java:142) ~[hibernate-search-engine-5.8.0.Beta4.jar:5.8.0.Beta4] > at org.infinispan.query.impl.CacheQueryImpl.list(CacheQueryImpl.java:160) ~[classes/:?] > at org.infinispan.query.blackbox.ClusteredCacheTest.testCompute(ClusteredCacheTest.java:687) ~[test-classes/:?] > Caused by: org.apache.lucene.index.IndexNotFoundException: no segments* file found in InfinispanDirectory{indexName='person.194'}: files: [] > at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:726) ~[lucene-core-5.5.4.jar:5.5.4 31012120ebbd93744753eb37f1dbc5e654628291 - jpountz - 2017-02-08 19:08:03] > at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:683) ~[lucene-core-5.5.4.jar:5.5.4 31012120ebbd93744753eb37f1dbc5e654628291 - jpountz - 2017-02-08 19:08:03] > at org.apache.lucene.index.SegmentInfos.readLatestCommit(SegmentInfos.java:490) ~[lucene-core-5.5.4.jar:5.5.4 31012120ebbd93744753eb37f1dbc5e654628291 - jpountz - 2017-02-08 19:08:03] > at org.apache.lucene.index.StandardDirectoryReader.isCurrent(StandardDirectoryReader.java:344) ~[lucene-core-5.5.4.jar:5.5.4 31012120ebbd93744753eb37f1dbc5e654628291 - jpountz - 2017-02-08 19:08:03] > at org.apache.lucene.index.StandardDirectoryReader.doOpenNoWriter(StandardDirectoryReader.java:300) ~[lucene-core-5.5.4.jar:5.5.4 31012120ebbd93744753eb37f1dbc5e654628291 - jpountz - 2017-02-08 19:08:03] > at org.apache.lucene.index.StandardDirectoryReader.doOpenIfChanged(StandardDirectoryReader.java:263) ~[lucene-core-5.5.4.jar:5.5.4 31012120ebbd93744753eb37f1dbc5e654628291 - jpountz - 2017-02-08 19:08:03] > at org.apache.lucene.index.StandardDirectoryReader.doOpenIfChanged(StandardDirectoryReader.java:251) ~[lucene-core-5.5.4.jar:5.5.4 31012120ebbd93744753eb37f1dbc5e654628291 - jpountz - 2017-02-08 19:08:03] > at org.apache.lucene.index.DirectoryReader.openIfChanged(DirectoryReader.java:137) ~[lucene-core-5.5.4.jar:5.5.4 31012120ebbd93744753eb37f1dbc5e654628291 - jpountz - 2017-02-08 19:08:03] > at org.hibernate.search.indexes.impl.SharingBufferReaderProvider$PerDirectoryLatestReader.refreshAndGet(SharingBufferReaderProvider.java:239) ~[hibernate-search-engine-5.8.0.Beta4.jar:5.8.0.Beta4] > ... 35 more > {noformat} > I suspect the root problem is that trace logging makes everything slower. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (ISPN-12167) Remove the already deprecated ProtostreamSerializationContextInitializer

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-12167?page=com.atlassian.jira.plugi... ] Nistor Adrian updated ISPN-12167: --------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Remove the already deprecated ProtostreamSerializationContextInitializer > ------------------------------------------------------------------------ > > Key: ISPN-12167 > URL: https://issues.redhat.com/browse/ISPN-12167 > Project: Infinispan > Issue Type: Task > Components: Remote Querying > Affects Versions: 12.0.0.Dev01 > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 12.0.0.Final, 12.0.0.Dev05 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

[JBoss JIRA] (ISPN-12389) Configuration is not the same if defaults are used in programatic or declared configuration

by Wolf-Dieter Fink (Jira)

Wolf-Dieter Fink created ISPN-12389: --------------------------------------- Summary: Configuration is not the same if defaults are used in programatic or declared configuration Key: ISPN-12389 URL: https://issues.redhat.com/browse/ISPN-12389 Project: Infinispan Issue Type: Bug Components: Clustered Locks Affects Versions: 11.0.4.Final Reporter: Wolf-Dieter Fink If the LockManager is initialized with configuration the reliability is not the same (and different from the default shown in XSD ..CONSISTENT). Because of that the (default) behavior is different and unexpected -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues October 2020