[JBoss JIRA] (ISPN-11754) Console creates a local cache if no configuration is provided
by Katia Aresti (Jira)
[ https://issues.redhat.com/browse/ISPN-11754?page=com.atlassian.jira.plugi... ]
Katia Aresti updated ISPN-11754:
--------------------------------
Status: Open (was: New)
> Console creates a local cache if no configuration is provided
> -------------------------------------------------------------
>
> Key: ISPN-11754
> URL: https://issues.redhat.com/browse/ISPN-11754
> Project: Infinispan
> Issue Type: Bug
> Components: Console
> Affects Versions: 10.1.6.Final
> Reporter: Katia Aresti
> Assignee: Katia Aresti
> Priority: Minor
> Labels: console-ng
>
> 1) Login to console http://<server>:11222/console/
> 2) Click Create Cache button
> 3) Type in a cache name
> 4) Select the org.infinispan.DIST_ASYNC template
> 5) Click the Provide a configuration link, but leave the text box blank
> 6) Click the Create button
> Result: The cache is created and has a label of "local" and this message is displayed by the configuration box: "Please provide a cache config JSON or XML". If no configuration is provided, then no cache should be created.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years
[JBoss JIRA] (IPROTO-141) org.infinispan.protostream.DescriptorParserException: Failed to resolve type of field ... Type not found : string
by özlem istek (Jira)
[ https://issues.redhat.com/browse/IPROTO-141?page=com.atlassian.jira.plugi... ]
özlem istek resolved IPROTO-141.
--------------------------------
Resolution: Explained
In fact it was due to my platform encoding(cp1254). It did not happen when I change it to UTF-8
> org.infinispan.protostream.DescriptorParserException: Failed to resolve type of field ... Type not found : string
> ------------------------------------------------------------------------------------------------------------------
>
> Key: IPROTO-141
> URL: https://issues.redhat.com/browse/IPROTO-141
> Project: Infinispan ProtoStream
> Issue Type: Bug
> Affects Versions: 4.3.2.Final
> Reporter: özlem istek
> Priority: Major
> Attachments: image-2020-05-04-17-02-42-112.png
>
>
> As a newbee when I tried to run this tutorial:
> https://github.com/infinispan/infinispan-embedded-tutorial.git
> I got this error message:
> /D:/ideaProjects/infinispan/infinispan-embedded-tutorial/src/main/java/org/infinispan/tutorial/embedded/SerializationContextInitializer.java:[11,8] org.infinispan.protostream.DescriptorParserException: Failed to resolve type of field "org.infinispan.tutorial.embedded.LocationWeather.conditions". Type not found : string
> at org.infinispan.protostream.descriptors.FileDescriptor.resolveFieldTypes(FileDescriptor.java:307)
> at org.infinispan.protostream.descriptors.FileDescriptor.resolveDependencies(FileDescriptor.java:217)
> at org.infinispan.protostream.descriptors.FileDescriptor.resolveDependencies(FileDescriptor.java:173)
> at org.infinispan.protostream.descriptors.ResolutionContext.resolve(ResolutionContext.java:57)
> at org.infinispan.protostream.impl.SerializationContextImpl.registerProtoFiles(SerializationContextImpl.java:117)
> at org.infinispan.protostream.annotations.impl.BaseProtoSchemaGenerator.generateAndRegister(BaseProtoSchemaGenerator.java:172)
> 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.process(AutoProtoSchemaBuilderAnnotationProcessor.java:178)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:794)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:705)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment.access$1800(JavacProcessingEnvironment.java:91)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1035)
> at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1176)
> at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1170)
> at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:856)
> at com.sun.tools.javac.main.Main.compile(Main.java:523)
> at com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:129)
> at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:138)
> 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.CompilerMojo.execute(CompilerMojo.java:187)
> 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 sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> 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)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years
[JBoss JIRA] (ISPN-11714) Auto-enable XML config elements when the element is present but its 'enabled' attribute is omitted
by Nistor Adrian (Jira)
[ https://issues.redhat.com/browse/ISPN-11714?page=com.atlassian.jira.plugi... ]
Nistor Adrian updated ISPN-11714:
---------------------------------
Description:
This is a generic issue that applies to multiple config areas: stores, xsite, security, jmx, indexing, partition handling.... We do have an 'enabled' attribute in other areas also, like state transfer where it is enabled by default, but we are not concerned with those. This issue only touches the cases where the XSD default value is false requiring the user to explicitly put enabled="true" in the config element. Rather than doing that we should simplify things , for usability, and if the element is present and the attribute is omitted we should auto-enable it.
This touches strictly xml config. Programmatic config still requires an explicit enable call.
The xml parser will only have this behaviour for schemas starting with 11.
TBD: 1. what do we do for JSON based config or other possible text formats?
2. What do we do about programmatic auto-enable, like in AbstractGlobalConfigurationBuilder.globalState() ?
NOTE: The indexing case is handled separately as it stands better chance to be resolved by next major release, here: https://issues.redhat.com/browse/ISPN-11712
was:
This is a generic issue that applies to multiple config areas: stores, xsite, security, jmx, indexing, partition handling.... We do have an 'enabled' attribute in other areas also, like state transfer where it is enabled by default, but we are not concerned with those. This issue only touches the cases where the XSD default value is false requiring the user to explicitly put enabled="true" in the config element. Rather than doing that we should simplify things , for usability, and if the element is present and the attribute is omitted we should auto-enable it.
This touches strictly xml config. Programmatic config still requires and explicit enable call.
The xml parser will only have this behaviour for schemas starting with 11.
TBD: 1. what do we do for JSON based config or other possible text formats?
2. What do we do about programmatic auto-enable, like in AbstractGlobalConfigurationBuilder.globalState() ?
NOTE: The indexing case is handled separately as it stands better chance to be resolved by next major release, here: https://issues.redhat.com/browse/ISPN-11712
> Auto-enable XML config elements when the element is present but its 'enabled' attribute is omitted
> --------------------------------------------------------------------------------------------------
>
> Key: ISPN-11714
> URL: https://issues.redhat.com/browse/ISPN-11714
> Project: Infinispan
> Issue Type: Enhancement
> Affects Versions: 11.0.0.Alpha1
> Reporter: Nistor Adrian
> Assignee: Nistor Adrian
> Priority: Major
>
> This is a generic issue that applies to multiple config areas: stores, xsite, security, jmx, indexing, partition handling.... We do have an 'enabled' attribute in other areas also, like state transfer where it is enabled by default, but we are not concerned with those. This issue only touches the cases where the XSD default value is false requiring the user to explicitly put enabled="true" in the config element. Rather than doing that we should simplify things , for usability, and if the element is present and the attribute is omitted we should auto-enable it.
> This touches strictly xml config. Programmatic config still requires an explicit enable call.
> The xml parser will only have this behaviour for schemas starting with 11.
> TBD: 1. what do we do for JSON based config or other possible text formats?
> 2. What do we do about programmatic auto-enable, like in AbstractGlobalConfigurationBuilder.globalState() ?
> NOTE: The indexing case is handled separately as it stands better chance to be resolved by next major release, here: https://issues.redhat.com/browse/ISPN-11712
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years
[JBoss JIRA] (ISPN-11765) Add internal headers to CORS rules
by Gustavo Fernandes (Jira)
Gustavo Fernandes created ISPN-11765:
----------------------------------------
Summary: Add internal headers to CORS rules
Key: ISPN-11765
URL: https://issues.redhat.com/browse/ISPN-11765
Project: Infinispan
Issue Type: Enhancement
Components: REST
Reporter: Gustavo Fernandes
Assignee: Gustavo Fernandes
Currently, only content-type is allowed for localhost by default.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years
[JBoss JIRA] (IPROTO-141) org.infinispan.protostream.DescriptorParserException: Failed to resolve type of field ... Type not found : string
by özlem istek (Jira)
özlem istek created IPROTO-141:
----------------------------------
Summary: org.infinispan.protostream.DescriptorParserException: Failed to resolve type of field ... Type not found : string
Key: IPROTO-141
URL: https://issues.redhat.com/browse/IPROTO-141
Project: Infinispan ProtoStream
Issue Type: Bug
Affects Versions: 4.3.2.Final
Reporter: özlem istek
Attachments: image-2020-05-04-17-02-42-112.png
As a newbee when I tried to run this tutorial:
https://github.com/infinispan/infinispan-embedded-tutorial.git
I got this error message:
/D:/ideaProjects/infinispan/infinispan-embedded-tutorial/src/main/java/org/infinispan/tutorial/embedded/SerializationContextInitializer.java:[11,8] org.infinispan.protostream.DescriptorParserException: Failed to resolve type of field "org.infinispan.tutorial.embedded.LocationWeather.conditions". Type not found : string
at org.infinispan.protostream.descriptors.FileDescriptor.resolveFieldTypes(FileDescriptor.java:307)
at org.infinispan.protostream.descriptors.FileDescriptor.resolveDependencies(FileDescriptor.java:217)
at org.infinispan.protostream.descriptors.FileDescriptor.resolveDependencies(FileDescriptor.java:173)
at org.infinispan.protostream.descriptors.ResolutionContext.resolve(ResolutionContext.java:57)
at org.infinispan.protostream.impl.SerializationContextImpl.registerProtoFiles(SerializationContextImpl.java:117)
at org.infinispan.protostream.annotations.impl.BaseProtoSchemaGenerator.generateAndRegister(BaseProtoSchemaGenerator.java:172)
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.process(AutoProtoSchemaBuilderAnnotationProcessor.java:178)
at com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:794)
at com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:705)
at com.sun.tools.javac.processing.JavacProcessingEnvironment.access$1800(JavacProcessingEnvironment.java:91)
at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1035)
at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1176)
at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1170)
at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:856)
at com.sun.tools.javac.main.Main.compile(Main.java:523)
at com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:129)
at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:138)
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.CompilerMojo.execute(CompilerMojo.java:187)
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 sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
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)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years
[JBoss JIRA] (ISPN-11758) QueryCache is a global component but should scope all cached queries per cache
by Gustavo Fernandes (Jira)
[ https://issues.redhat.com/browse/ISPN-11758?page=com.atlassian.jira.plugi... ]
Gustavo Fernandes updated ISPN-11758:
-------------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> QueryCache is a global component but should scope all cached queries per cache
> ------------------------------------------------------------------------------
>
> Key: ISPN-11758
> URL: https://issues.redhat.com/browse/ISPN-11758
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying, Remote Querying
> Reporter: Nistor Adrian
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 11.0.0.CR1
>
>
> The query might execute differently depending on the configuration of each cache. This will be an issue starting with HSearch 6.
> All entries will be keyed also based on cache name. QueryCache must be cleared when a cache stops. Also, all caches must have a configured stop dependency on the QueryCache.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years