[JBoss JIRA] (IPROTO-132) Enum classes with abstract methods don't compile
by Ryan Emerson (Jira)
Ryan Emerson created IPROTO-132:
-----------------------------------
Summary: 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
Reporter: Ryan Emerson
{{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 month
[JBoss JIRA] (ISPN-11423) Dump information in panic scenarios
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-11423?page=com.atlassian.jira.plugi... ]
Dan Berindei commented on ISPN-11423:
-------------------------------------
We might want to treat any {{TimeoutException}} as a panic situation, but we need special handling for {{ZERO_LOCK_ACQUISITION_TIMEOUT}}.
> Dump information in panic scenarios
> -----------------------------------
>
> Key: ISPN-11423
> URL: https://issues.redhat.com/browse/ISPN-11423
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core, Server
> Affects Versions: 10.1.3.Final, 11.0.0.Alpha2
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 11.0.0.Dev03
>
>
> When there is a panic situation (e.g. thread pool exhausted), dump information (e.g. including a thread dump) to a file at FATAL level.
> The server should dump the most important information to another log (file) periodically (e.g. every 15 minutes). This log should be enabled by default.
> These files can be sent to support via an SOS report.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (ISPN-11427) RestMetricsResource#testMicroprofileMetricsMetadata can timeout
by Will Burns (Jira)
[ https://issues.redhat.com/browse/ISPN-11427?page=com.atlassian.jira.plugi... ]
Will Burns updated ISPN-11427:
------------------------------
Description: The testMicroprofileMetricsMetadata method times out trying to invoke a rest command. This appears to be due to scalability issues in small rye metrics with json exporter with a few thousand metrics. (was: The testMicroprofileMetricsMetadata method times out trying to invoke a rest command. This might be related to the thread pool changes.)
> RestMetricsResource#testMicroprofileMetricsMetadata can timeout
> ---------------------------------------------------------------
>
> Key: ISPN-11427
> URL: https://issues.redhat.com/browse/ISPN-11427
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 11.0.0.Alpha2
> Reporter: Will Burns
> Assignee: Will Burns
> Priority: Major
> Fix For: 11.0.0.Dev03
>
>
> The testMicroprofileMetricsMetadata method times out trying to invoke a rest command. This appears to be due to scalability issues in small rye metrics with json exporter with a few thousand metrics.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (ISPN-11238) Server Logging management via CLI
by Tristan Tarrant (Jira)
[ https://issues.redhat.com/browse/ISPN-11238?page=com.atlassian.jira.plugi... ]
Tristan Tarrant updated ISPN-11238:
-----------------------------------
Fix Version/s: 11.0.0.Dev03
> Server Logging management via CLI
> ---------------------------------
>
> Key: ISPN-11238
> URL: https://issues.redhat.com/browse/ISPN-11238
> Project: Infinispan
> Issue Type: Feature Request
> Components: CLI, JMX, reporting and management, Server
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Labels: supportability
> Fix For: 11.0.0.Dev03, 11.0.0.Final
>
>
> The CLI should be extended with commands to view/alter the server logging configuration.
> The CLI commands should reflect the REST API that is to be implemented by ISPN-10539:
> * logging list-loggers
> * logging list-appenders
> * logging set --level=[level] --appenders=[appender] [category]
> * logging remove [category]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month