April 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11556) SFS file location not relative to global persistent-location

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-11556?page=com.atlassian.jira.plugi... ] Ryan Emerson updated ISPN-11556: -------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/8122, https://github.com/infinispan/infinispan/pull/8215, https://github.com/infinispan/infinispan/pull/8217 (was: https://github.com/infinispan/infinispan/pull/8122, https://github.com/infinispan/infinispan/pull/8215) > SFS file location not relative to global persistent-location > ------------------------------------------------------------ > > Key: ISPN-11556 > URL: https://issues.redhat.com/browse/ISPN-11556 > Project: Infinispan > Issue Type: Bug > Components: Configuration, Core > Affects Versions: 10.1.5.Final, 11.0.0.Dev03 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.1.7.Final, 11.0.0.Dev05 > > > Currently if a user specifies the location `/blah` in the SFS configuration, this location will be used regardless of the configure `persistent-location`. Instead, we should create the file location using `PersistenceUtil#getQualifiedLocation` and an exception will be thrown if `/blah` is not the root of the configure `persistent-location`. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11675) ComponentAnnotationProcessor exception hides compilation error

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11675?page=com.atlassian.jira.plugi... ] Nistor Adrian commented on ISPN-11675: -------------------------------------- I think I saw similar issues with protostream's AP. Will take these precautions there also. > ComponentAnnotationProcessor exception hides compilation error > -------------------------------------------------------------- > > Key: ISPN-11675 > URL: https://issues.redhat.com/browse/ISPN-11675 > Project: Infinispan > Issue Type: Bug > Components: Build, Core > Affects Versions: 11.0.0.Dev04, 10.1.6.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 11.0.0.Dev05 > > > When a source file has a component annotation with an invalid value, e.g. {{@DefaultFactoryFor(classes = \{NonExistentClass.class\})}}, {{ComponentAnnotationProcessor}} hits a {{ClassCastException}}: > {noformat} > Error:java: ComponentAnnotationProcessor unexpected error: java.lang.ClassCastException: class com.sun.tools.javac.code.Attribute$UnresolvedClass cannot be cast to class com.sun.tools.javac.code.Attribute$Class (com.sun.tools.javac.code.Attribute$UnresolvedClass and com.sun.tools.javac.code.Attribute$Class are in module jdk.compiler of loader 'app') > at jdk.compiler/com.sun.tools.javac.model.AnnotationProxyMaker$ValueVisitor.visitArray(AnnotationProxyMaker.java:192) > at jdk.compiler/com.sun.tools.javac.code.Attribute$Array.accept(Attribute.java:327) > at jdk.compiler/com.sun.tools.javac.model.AnnotationProxyMaker$ValueVisitor.getValue(AnnotationProxyMaker.java:167) > at jdk.compiler/com.sun.tools.javac.model.AnnotationProxyMaker.generateValue(AnnotationProxyMaker.java:145) > at jdk.compiler/com.sun.tools.javac.model.AnnotationProxyMaker.getAllReflectedValues(AnnotationProxyMaker.java:104) > at jdk.compiler/com.sun.tools.javac.model.AnnotationProxyMaker.generateAnnotation(AnnotationProxyMaker.java:90) > at jdk.compiler/com.sun.tools.javac.model.AnnotationProxyMaker.generateAnnotation(AnnotationProxyMaker.java:81) > at jdk.compiler/com.sun.tools.javac.code.AnnoConstruct.getAnnotation(AnnoConstruct.java:185) > at org.infinispan.component.processor.ComponentAnnotationProcessor$ModelBuilder.getFactoryComponentNames(ComponentAnnotationProcessor.java:606) > at org.infinispan.component.processor.ComponentAnnotationProcessor$ModelBuilder.visitType(ComponentAnnotationProcessor.java:318) > at org.infinispan.component.processor.ComponentAnnotationProcessor$ModelBuilder.visitType(ComponentAnnotationProcessor.java:281) > at jdk.compiler/com.sun.tools.javac.code.Symbol$ClassSymbol.accept(Symbol.java:1477) > at java.compiler@13.0.1/javax.lang.model.util.ElementScanner6.scan(ElementScanner6.java:153) > at java.compiler@13.0.1/javax.lang.model.util.ElementScanner6.scan(ElementScanner6.java:140) > at org.infinispan.component.processor.ComponentAnnotationProcessor.process(ComponentAnnotationProcessor.java:122) > at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:1023) > at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:939) > at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1267) > at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1381) > at jdk.compiler/com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1263) > at jdk.compiler/com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:935) > at jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.lambda$doCall$0(JavacTaskImpl.java:104) > at jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.handleExceptions(JavacTaskImpl.java:147) > at jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:100) > at jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:94) > {noformat} > IntelliJ shows the annotation processor error first, hiding the compilation error, while Maven only says > {noformat} > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project infinispan-core: Fatal error compiling: CompilerException: NullPointerException > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11675) ComponentAnnotationProcessor exception hides compilation error

by Nistor Adrian (Jira)

[ https://issues.redhat.com/browse/ISPN-11675?page=com.atlassian.jira.plugi... ] Nistor Adrian updated ISPN-11675: --------------------------------- Fix Version/s: 11.0.0.Dev05 (was: 11.0.0.CR1) > ComponentAnnotationProcessor exception hides compilation error > -------------------------------------------------------------- > > Key: ISPN-11675 > URL: https://issues.redhat.com/browse/ISPN-11675 > Project: Infinispan > Issue Type: Bug > Components: Build, Core > Affects Versions: 11.0.0.Dev04, 10.1.6.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 11.0.0.Dev05 > > > When a source file has a component annotation with an invalid value, e.g. {{@DefaultFactoryFor(classes = \{NonExistentClass.class\})}}, {{ComponentAnnotationProcessor}} hits a {{ClassCastException}}: > {noformat} > Error:java: ComponentAnnotationProcessor unexpected error: java.lang.ClassCastException: class com.sun.tools.javac.code.Attribute$UnresolvedClass cannot be cast to class com.sun.tools.javac.code.Attribute$Class (com.sun.tools.javac.code.Attribute$UnresolvedClass and com.sun.tools.javac.code.Attribute$Class are in module jdk.compiler of loader 'app') > at jdk.compiler/com.sun.tools.javac.model.AnnotationProxyMaker$ValueVisitor.visitArray(AnnotationProxyMaker.java:192) > at jdk.compiler/com.sun.tools.javac.code.Attribute$Array.accept(Attribute.java:327) > at jdk.compiler/com.sun.tools.javac.model.AnnotationProxyMaker$ValueVisitor.getValue(AnnotationProxyMaker.java:167) > at jdk.compiler/com.sun.tools.javac.model.AnnotationProxyMaker.generateValue(AnnotationProxyMaker.java:145) > at jdk.compiler/com.sun.tools.javac.model.AnnotationProxyMaker.getAllReflectedValues(AnnotationProxyMaker.java:104) > at jdk.compiler/com.sun.tools.javac.model.AnnotationProxyMaker.generateAnnotation(AnnotationProxyMaker.java:90) > at jdk.compiler/com.sun.tools.javac.model.AnnotationProxyMaker.generateAnnotation(AnnotationProxyMaker.java:81) > at jdk.compiler/com.sun.tools.javac.code.AnnoConstruct.getAnnotation(AnnoConstruct.java:185) > at org.infinispan.component.processor.ComponentAnnotationProcessor$ModelBuilder.getFactoryComponentNames(ComponentAnnotationProcessor.java:606) > at org.infinispan.component.processor.ComponentAnnotationProcessor$ModelBuilder.visitType(ComponentAnnotationProcessor.java:318) > at org.infinispan.component.processor.ComponentAnnotationProcessor$ModelBuilder.visitType(ComponentAnnotationProcessor.java:281) > at jdk.compiler/com.sun.tools.javac.code.Symbol$ClassSymbol.accept(Symbol.java:1477) > at java.compiler@13.0.1/javax.lang.model.util.ElementScanner6.scan(ElementScanner6.java:153) > at java.compiler@13.0.1/javax.lang.model.util.ElementScanner6.scan(ElementScanner6.java:140) > at org.infinispan.component.processor.ComponentAnnotationProcessor.process(ComponentAnnotationProcessor.java:122) > at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:1023) > at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:939) > at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1267) > at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1381) > at jdk.compiler/com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1263) > at jdk.compiler/com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:935) > at jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.lambda$doCall$0(JavacTaskImpl.java:104) > at jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.handleExceptions(JavacTaskImpl.java:147) > at jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:100) > at jdk.compiler/com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:94) > {noformat} > IntelliJ shows the annotation processor error first, hiding the compilation error, while Maven only says > {noformat} > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project infinispan-core: Fatal error compiling: CompilerException: NullPointerException > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11674) Clean up RemoteCache method overrides

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11674?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11674: ------------------------------ Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/8216 > Clean up RemoteCache method overrides > ------------------------------------- > > Key: ISPN-11674 > URL: https://issues.redhat.com/browse/ISPN-11674 > Project: Infinispan > Issue Type: Enhancement > Components: Hot Rod > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 11.0.0.Dev05 > > > There are a lot of various method overrides in the RemoteCache. This is because of async, versions and expiration overrides bloating almost all methods by eight times. We should consolidate these so they are simpler to handle and harder to mess up. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11674) Clean up RemoteCache method overrides

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11674?page=com.atlassian.jira.plugi... ] Work on ISPN-11674 started by Will Burns. ----------------------------------------- > Clean up RemoteCache method overrides > ------------------------------------- > > Key: ISPN-11674 > URL: https://issues.redhat.com/browse/ISPN-11674 > Project: Infinispan > Issue Type: Enhancement > Components: Hot Rod > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 11.0.0.Dev05 > > > There are a lot of various method overrides in the RemoteCache. This is because of async, versions and expiration overrides bloating almost all methods by eight times. We should consolidate these so they are simpler to handle and harder to mess up. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11674) Clean up RemoteCache method overrides

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11674?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11674: ------------------------------ Status: Open (was: New) > Clean up RemoteCache method overrides > ------------------------------------- > > Key: ISPN-11674 > URL: https://issues.redhat.com/browse/ISPN-11674 > Project: Infinispan > Issue Type: Enhancement > Components: Hot Rod > Reporter: Will Burns > Priority: Major > Fix For: 11.0.0.Dev05 > > > There are a lot of various method overrides in the RemoteCache. This is because of async, versions and expiration overrides bloating almost all methods by eight times. We should consolidate these so they are simpler to handle and harder to mess up. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11537) Add StatefulSet rolling upgrade server integration test

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-11537?page=com.atlassian.jira.plugi... ] Ryan Emerson resolved ISPN-11537. --------------------------------- Resolution: Done > Add StatefulSet rolling upgrade server integration test > ------------------------------------------------------- > > Key: ISPN-11537 > URL: https://issues.redhat.com/browse/ISPN-11537 > Project: Infinispan > Issue Type: Enhancement > Components: Test Suite > Affects Versions: 10.1.5.Final, 11.0.0.Dev03 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.1.7.Final, 11.0.0.Dev05 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11485) No Server logs after shutdownHook has been called

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-11485?page=com.atlassian.jira.plugi... ] Ryan Emerson resolved ISPN-11485. --------------------------------- Resolution: Done > No Server logs after shutdownHook has been called > ------------------------------------------------- > > Key: ISPN-11485 > URL: https://issues.redhat.com/browse/ISPN-11485 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 11.0.0.Alpha2, 10.1.5.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.1.7.Final, 11.0.0.Dev05 > > > When a server process receives a SIGTERM it simply logs the following, regardless of the log configuration: > {code} > INFO (Thread-0) [org.infinispan.SERVER] ISPN080002: Infinispan Server stopping > INFO (Thread-0) [org.infinispan.SERVER] ISPN080002: Infinispan Server stopped > {code} > This is because Log4j registers a shutdownHook with the runtime in order to cleanup log resources. In order to aid server debugging, we should [disable this shutdownHook|https://logging.apache.org/log4j/2.x/manual/configuration.html] and manually shutdown the Log4j LogManager. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11556) SFS file location not relative to global persistent-location

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/ISPN-11556?page=com.atlassian.jira.plugi... ] Ryan Emerson updated ISPN-11556: -------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/8122, https://github.com/infinispan/infinispan/pull/8215 (was: https://github.com/infinispan/infinispan/pull/8122) > SFS file location not relative to global persistent-location > ------------------------------------------------------------ > > Key: ISPN-11556 > URL: https://issues.redhat.com/browse/ISPN-11556 > Project: Infinispan > Issue Type: Bug > Components: Configuration, Core > Affects Versions: 10.1.5.Final, 11.0.0.Dev03 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.1.7.Final, 11.0.0.Dev05 > > > Currently if a user specifies the location `/blah` in the SFS configuration, this location will be used regardless of the configure `persistent-location`. Instead, we should create the file location using `PersistenceUtil#getQualifiedLocation` and an exception will be thrown if `/blah` is not the root of the configure `persistent-location`. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11676) Per-cache Hot Rod client configuration

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11676?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11676: ----------------------------------- Status: Open (was: New) > Per-cache Hot Rod client configuration > -------------------------------------- > > Key: ISPN-11676 > URL: https://issues.redhat.com/browse/ISPN-11676 > Project: Infinispan > Issue Type: Enhancement > Components: Hot Rod > Affects Versions: 11.0.0.Dev04, 10.1.6.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.1.7.Final, 11.0.0.Dev05 > > > Currently some configuration in the Hot Rod client is global (tx mode, force return values, near cache). We should introduce per-cache configuration. Additionally we should also be able to specify a server-side template/configuration to use if a cache doesn't exist. > {code:java} > builder > .remoteCache(cacheName) > .templateName("template") > .nearCacheMode(NearCacheMode.INVALIDATED) > .nearCacheMaxEntries(100) > .forceReturnValues(true); > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 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 April 2020