January 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-10161) ThreadLeakChecker is blocking PolarionJUnitXMLReporter to generate the reports

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-10161?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-10161: ------------------------------------------ Sprint: DataGrid Sprint #30, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #30, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38) > ThreadLeakChecker is blocking PolarionJUnitXMLReporter to generate the reports > ------------------------------------------------------------------------------ > > Key: ISPN-10161 > URL: https://issues.redhat.com/browse/ISPN-10161 > Project: Infinispan > Issue Type: Bug > Affects Versions: 9.4.12.Final, 10.0.0.Final > Reporter: Diego Lovison > Assignee: Dan Berindei > Priority: Critical > Fix For: 10.0.0.CR3 > > > When we have Leaked threads we are throwing a new RuntimeException that is preventing the next listener to be running. > From `master` execute `rm -rf hibernate/cache-v51/target/surefire-reports/ && rm -rf hibernate/cache-v53/target/surefire-reports/ && mvn verify -pl hibernate/cache-v51,hibernate/cache-v53 -Dtest=MultiTenancyTest -fae` > After that, check the hibernate/cache-v53/target/surefire-reports/ folder, you will see no reports there. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-102) Support java.util.Optional for property getters

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/IPROTO-102?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated IPROTO-102: ------------------------------------------ Sprint: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38) > Support java.util.Optional for property getters > ----------------------------------------------- > > Key: IPROTO-102 > URL: https://issues.redhat.com/browse/IPROTO-102 > Project: Infinispan ProtoStream > Issue Type: Enhancement > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.3.0.Alpha9, 4.3.0.Final > > > Support for Optional<> used with getter return type. No support for fields or for setter param. Also, no support for OptionalDouble, OptionalInt or OptionalLong. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (IPROTO-106) OriginatingClasses annotation should be located in a runtime jar, not in the annotation processor jar

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/IPROTO-106?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated IPROTO-106: ------------------------------------------ Sprint: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38) > OriginatingClasses annotation should be located in a runtime jar, not in the annotation processor jar > ------------------------------------------------------------------------------------------------------ > > Key: IPROTO-106 > URL: https://issues.redhat.com/browse/IPROTO-106 > Project: Infinispan ProtoStream > Issue Type: Bug > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 4.3.0.Alpha9 > > > The annotation processor is a compile time dependency, so OriginatingClasses annotation is not loadable at runtime, but this does not create a classloading issue because the retention of the annotation is CLASS, so not actually needed at runtime. All good at runtime. But javadoc generation does not work, failing due to missing dependency unless we add it explicitly, which is cumbersome. > This is already leading to failures in Infinispan https://ci.infinispan.org/job/Infinispan/job/master/1304/consoleFull#1277... -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11106) Export 'base' and 'vendor' microprofile metric registries

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-11106?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-11106: ------------------------------------------ Sprint: DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #38) > Export 'base' and 'vendor' microprofile metric registries > --------------------------------------------------------- > > Key: ISPN-11106 > URL: https://issues.redhat.com/browse/ISPN-11106 > Project: Infinispan > Issue Type: Enhancement > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.0.Final > > > These registries were not populated and smallrye metrics has a little utility that could populate them cheaply (few lines of code) with information extracted from various java.lang.management.PlatformManagedObject implementations. This is achieved by scraping the platform mbeans. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9599) DefaultCacheManager.getGlobalComponentRegistry should require ADMIN permission

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-9599?page=com.atlassian.jira.plugin... ] Pedro Zapata Fernandez updated ISPN-9599: ----------------------------------------- Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Alpha0, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Alpha0, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38) > DefaultCacheManager.getGlobalComponentRegistry should require ADMIN permission > ------------------------------------------------------------------------------ > > Key: ISPN-9599 > URL: https://issues.redhat.com/browse/ISPN-9599 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.3.3.Final, 9.4.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.0.0.Final, 9.4.17.Final > > > {{DefaultCacheManager.getGlobalComponentRegistry()}} allows invoking any component without additional permission checks, so it needs ADMIN permission. > {{DefaultCacheManager.getCacheManagerConfiguration()}} also allows access to some internal components, so it also needs ADMIN permission. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9322) Remove all usages of @IndexedField protostream annotation

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-9322?page=com.atlassian.jira.plugin... ] Pedro Zapata Fernandez updated ISPN-9322: ----------------------------------------- Sprint: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38) > Remove all usages of @IndexedField protostream annotation > --------------------------------------------------------- > > Key: ISPN-9322 > URL: https://issues.redhat.com/browse/ISPN-9322 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.0.0.Final > > > This annotation is deprecated and should be replaced with @Field but we still have several usages in our test suite. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9083) Remove support for 'indexed_by_default' option in protobuf schemas

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-9083?page=com.atlassian.jira.plugin... ] Pedro Zapata Fernandez updated ISPN-9083: ----------------------------------------- Sprint: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38) > Remove support for 'indexed_by_default' option in protobuf schemas > ------------------------------------------------------------------ > > Key: ISPN-9083 > URL: https://issues.redhat.com/browse/ISPN-9083 > Project: Infinispan > Issue Type: Task > Components: Remote Querying > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Labels: SearchNG > Fix For: 10.0.0.Final > > > All the behaviour around this option must be removed and the option must be documented as no longer supported in Infinispan 10. > Usage of this option must trigger a warning. Should be entirely removed in 10.1 or some later version right after 10 - usages will be ignored after this point. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11066) Deprecate QueryBuilder DSL

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-11066?page=com.atlassian.jira.plugi... ] Pedro Zapata Fernandez updated ISPN-11066: ------------------------------------------ Sprint: DataGrid Sprint #38, DataGrid Sprint #39 (was: DataGrid Sprint #38) > Deprecate QueryBuilder DSL > -------------------------- > > Key: ISPN-11066 > URL: https://issues.redhat.com/browse/ISPN-11066 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying, Remote Querying > Affects Versions: 10.1.0.CR1 > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.0.Final > > > Ickle will replace it. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9699) Cluster member owning no data

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-9699?page=com.atlassian.jira.plugin... ] Pedro Zapata Fernandez updated ISPN-9699: ----------------------------------------- Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38) > Cluster member owning no data > ----------------------------- > > Key: ISPN-9699 > URL: https://issues.redhat.com/browse/ISPN-9699 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 9.4.1.Final > Reporter: Thomas Segismont > Assignee: Katia Aresti > Priority: Major > Fix For: 9.4.7.Final, 10.0.0.Beta1 > > > Currently, you can set {{capacity-factor}} to zero on a cache if you don't want a node to own any segment. > If you want a node to own no data at all, you could set this property on all declared caches. But this wouldn't work for internal caches anyway (locks, counters). > It would be nice to have a global switch. > This would be useful when your app needs to be a cluster member for discovery/membership but is deployed mostly for processing. Indeed, when such nodes are added/removed from the cluster: > * there would be no data loss > * the cluster would be back in healthy state faster as no data would be moved around. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9660) Histogram stats

by Pedro Zapata Fernandez (Jira)

[ https://issues.redhat.com/browse/ISPN-9660?page=com.atlassian.jira.plugin... ] Pedro Zapata Fernandez updated ISPN-9660: ----------------------------------------- Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38, DataGrid Sprint #39 (was: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33, DataGrid Sprint #34, DataGrid Sprint #35, DataGrid Sprint #36, DataGrid Sprint #37, DataGrid Sprint #38) > Histogram stats > --------------- > > Key: ISPN-9660 > URL: https://issues.redhat.com/browse/ISPN-9660 > Project: Infinispan > Issue Type: Feature Request > Components: JMX, reporting and management > Affects Versions: 9.4.0.Final > Reporter: Tristan Tarrant > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.0.CR1, 10.1.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2020