March 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11472) Doc Fixes: Hot Rod Java Client

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-11472?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-11472: ------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/8060 > Doc Fixes: Hot Rod Java Client > ------------------------------ > > Key: ISPN-11472 > URL: https://issues.redhat.com/browse/ISPN-11472 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > > Several issues reported for the Hot Rod Java Client Guide. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11474) RecoveryManager API should be non blocking

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11474?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11474: ------------------------------ Fix Version/s: 11.0.0.Dev03 > RecoveryManager API should be non blocking > ------------------------------------------ > > Key: ISPN-11474 > URL: https://issues.redhat.com/browse/ISPN-11474 > Project: Infinispan > Issue Type: Sub-task > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 11.0.0.Dev03 > > > RecoverManager, which is internal only, has a blocking API which can pass a sync parameter. Instead we should change the API to be non blocking and let callers decide if they want to wait or not on it. This allows us to clean up callers who may be able to use this in a non blocking fashion. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11474) RecoveryManager API should be non blocking

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11474?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11474: ------------------------------ Status: Open (was: New) > RecoveryManager API should be non blocking > ------------------------------------------ > > Key: ISPN-11474 > URL: https://issues.redhat.com/browse/ISPN-11474 > Project: Infinispan > Issue Type: Sub-task > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > > RecoverManager, which is internal only, has a blocking API which can pass a sync parameter. Instead we should change the API to be non blocking and let callers decide if they want to wait or not on it. This allows us to clean up callers who may be able to use this in a non blocking fashion. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11474) RecoveryManager API should be non blocking

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11474?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11474: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8064 > RecoveryManager API should be non blocking > ------------------------------------------ > > Key: ISPN-11474 > URL: https://issues.redhat.com/browse/ISPN-11474 > Project: Infinispan > Issue Type: Sub-task > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > > RecoverManager, which is internal only, has a blocking API which can pass a sync parameter. Instead we should change the API to be non blocking and let callers decide if they want to wait or not on it. This allows us to clean up callers who may be able to use this in a non blocking fashion. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11473) InvocationHelper should commit or rollback the transaction on a blocking thread

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11473?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11473: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8062 > InvocationHelper should commit or rollback the transaction on a blocking thread > ------------------------------------------------------------------------------- > > Key: ISPN-11473 > URL: https://issues.redhat.com/browse/ISPN-11473 > Project: Infinispan > Issue Type: Sub-task > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 11.0.0.Dev03 > > > We should make sure to commit/rollback on the blocking thread as the Transaction API is blocking but requires remote invocations. InvocationHelper currently handles this in a handle but should be handleAsync, so it should pretty easy to swap in. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11473) InvocationHelper should commit or rollback the transaction on a blocking thread

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11473?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11473: ------------------------------ Fix Version/s: 11.0.0.Dev03 > InvocationHelper should commit or rollback the transaction on a blocking thread > ------------------------------------------------------------------------------- > > Key: ISPN-11473 > URL: https://issues.redhat.com/browse/ISPN-11473 > Project: Infinispan > Issue Type: Sub-task > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 11.0.0.Dev03 > > > We should make sure to commit/rollback on the blocking thread as the Transaction API is blocking but requires remote invocations. InvocationHelper currently handles this in a handle but should be handleAsync, so it should pretty easy to swap in. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11126) Health check fails when authz is enabled and cache is not yet started

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11126?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-11126: ------------------------------ Comment: was deleted (was: Integrated into master for 11.0..0.Dev3. Waiting before integrating 10.1.x.) > Health check fails when authz is enabled and cache is not yet started > --------------------------------------------------------------------- > > Key: ISPN-11126 > URL: https://issues.redhat.com/browse/ISPN-11126 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management, REST > Affects Versions: 10.1.0.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 11.0.0.Dev03, 10.1.6.Final > > > When using predefined caches on a container with authorization, and the caches have not been started, the health handler for the cachemanager resource fails with an authorization error. > The call should be wrapped in a SecurityAction. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11126) Health check fails when authz is enabled and cache is not yet started

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11126?page=com.atlassian.jira.plugi... ] Will Burns commented on ISPN-11126: ----------------------------------- Integrated into master for 11.0..0.Dev3. Waiting before integrating 10.1.x. > Health check fails when authz is enabled and cache is not yet started > --------------------------------------------------------------------- > > Key: ISPN-11126 > URL: https://issues.redhat.com/browse/ISPN-11126 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management, REST > Affects Versions: 10.1.0.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 11.0.0.Dev03, 10.1.6.Final > > > When using predefined caches on a container with authorization, and the caches have not been started, the health handler for the cachemanager resource fails with an authorization error. > The call should be wrapped in a SecurityAction. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (ISPN-11440) Allow use of config sub-elements in XIncluded fragments

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-11440?page=com.atlassian.jira.plugi... ] Will Burns commented on ISPN-11440: ----------------------------------- Integrated into master for 11.0..0.Dev3. Waiting before integrating 10.1.x. > Allow use of config sub-elements in XIncluded fragments > ------------------------------------------------------- > > Key: ISPN-11440 > URL: https://issues.redhat.com/browse/ISPN-11440 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration > Affects Versions: 11.0.0.Alpha2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 11.0.0.Dev03, 10.1.6.Final > > > The infinispan-config XSD only allows the {{infinispan}} element as a top-level element. However, when using XInclude, it would be useful to be able to have other kinds of top-level elements: > jgroups > threads > cache-container > transport > security > *-cache-* -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

[JBoss JIRA] (IPROTO-132) Enum classes with abstract methods don't compile

by Ryan Emerson (Jira)

[ https://issues.redhat.com/browse/IPROTO-132?page=com.atlassian.jira.plugi... ] Ryan Emerson closed IPROTO-132. ------------------------------- > Enum classes with abstract methods don't compile > ------------------------------------------------ > > Key: IPROTO-132 > URL: https://issues.redhat.com/browse/IPROTO-132 > Project: Infinispan ProtoStream > Issue Type: Bug > Affects Versions: 4.3.2.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 4.2.6.Final, 4.3.3.Final > > > {{ProtoMessageTypeMetadata}} checks fail when an Enum implementation relies on the enum instances implementing one or more abstract methods. For example, the {{org.infinispan.commands.write.ValueMatcher}} class. > {code:java} > org.infinispan.protostream.annotations.ProtoSchemaBuilderException: The type org.infinispan.commands.write.ValueMatcher of field 'valueMatcher' of org.infinispan.commands.write.ReplaceCommand should not be abstract. > at org.infinispan.protostream.annotations.impl.ProtoMessageTypeMetadata.discoverFields(ProtoMessageTypeMetadata.java:343) > at org.infinispan.protostream.annotations.impl.ProtoMessageTypeMetadata.scanMemberAnnotations(ProtoMessageTypeMetadata.java:178) > at org.infinispan.protostream.annotations.impl.BaseProtoSchemaGenerator.generateAndRegister(BaseProtoSchemaGenerator.java:116) > at org.infinispan.protostream.annotations.impl.processor.AutoProtoSchemaBuilderAnnotationProcessor.processClass(AutoProtoSchemaBuilderAnnotationProcessor.java:320) > at org.infinispan.protostream.annotations.impl.processor.AutoProtoSchemaBuilderAnnotationProcessor.processElement(AutoProtoSchemaBuilderAnnotationProcessor.java:251) > at org.infinispan.protostream.annotations.impl.processor.AutoProtoSchemaBuilderAnnotationProcessor.processDependencies(AutoProtoSchemaBuilderAnnotationProcessor.java:380) > at org.infinispan.protostream.annotations.impl.processor.AutoProtoSchemaBuilderAnnotationProcessor.processClass(AutoProtoSchemaBuilderAnnotationProcessor.java:312) > at org.infinispan.protostream.annotations.impl.processor.AutoProtoSchemaBuilderAnnotationProcessor.processElement(AutoProtoSchemaBuilderAnnotationProcessor.java:251) > at org.infinispan.protostream.annotations.impl.processor.AutoProtoSchemaBuilderAnnotationProcessor.process(AutoProtoSchemaBuilderAnnotationProcessor.java:178) > at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:980) > at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:896) > at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1222) > at jdk.compiler/com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1334) > at jdk.compiler/com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1258) > at jdk.compiler/com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:936) > 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) > at org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:126) > at org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile(JavacCompiler.java:174) > at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:1134) > at org.apache.maven.plugin.compiler.TestCompilerMojo.execute(TestCompilerMojo.java:180) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81) > at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:56) > at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:305) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:192) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:105) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:956) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:192) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:282) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:225) > at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:406) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:347) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2020