[JBoss JIRA] (IPROTO-132) Enum classes with abstract methods don't compile
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/IPROTO-132?page=com.atlassian.jira.plugi... ]
Pedro Zapata Fernandez updated IPROTO-132:
------------------------------------------
Sprint: DataGrid Sprint #41
> 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
> Priority: Major
> Fix For: 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 month
[JBoss JIRA] (ISPN-6162) Drop Query.getResultSize() method
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-6162?page=com.atlassian.jira.plugin... ]
Pedro Zapata Fernandez updated ISPN-6162:
-----------------------------------------
Sprint: DataGrid Sprint #41
> Drop Query.getResultSize() method
> ---------------------------------
>
> Key: ISPN-6162
> URL: https://issues.redhat.com/browse/ISPN-6162
> Project: Infinispan
> Issue Type: Task
> Components: Embedded Querying, Remote Querying
> Reporter: Tristan Tarrant
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 11.0.0.Final
>
>
> Do we keep org.infinispan.query.dsl.Query.getResultSize? Does it return int or long? Return -1 if actual figure unknown/hard to compute? Result size might be non-trivial for non-indexed or hybrid case and will require full scan even for queries with limit. Deprecate it now, remove in ispn 9.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (ISPN-6162) Drop Query.getResultSize() method
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-6162?page=com.atlassian.jira.plugin... ]
Pedro Zapata Fernandez updated ISPN-6162:
-----------------------------------------
Sprint: (was: DataGrid Sprint #41)
> Drop Query.getResultSize() method
> ---------------------------------
>
> Key: ISPN-6162
> URL: https://issues.redhat.com/browse/ISPN-6162
> Project: Infinispan
> Issue Type: Task
> Components: Embedded Querying, Remote Querying
> Reporter: Tristan Tarrant
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 11.0.0.Final
>
>
> Do we keep org.infinispan.query.dsl.Query.getResultSize? Does it return int or long? Return -1 if actual figure unknown/hard to compute? Result size might be non-trivial for non-indexed or hybrid case and will require full scan even for queries with limit. Deprecate it now, remove in ispn 9.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (ISPN-9405) Cluster failover not always working when first node not available
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-9405?page=com.atlassian.jira.plugin... ]
Pedro Zapata Fernandez closed ISPN-9405.
----------------------------------------
Resolution: Out of Date
> Cluster failover not always working when first node not available
> -----------------------------------------------------------------
>
> Key: ISPN-9405
> URL: https://issues.redhat.com/browse/ISPN-9405
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Protocols
> Affects Versions: 9.1.7.Final
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Priority: Major
> Fix For: 9.1.8.Final
>
> Attachments: NonExistentNodeSiteDownFailoverTest.java
>
>
> If a client configures a main cluster with the first node unavailable and a backup cluster, ping-pong failover ends up failing with the first unavailable node failing. E.g.
> {code}
> 19:16:29,491 ERROR (testng-NonExistentNodeSiteDownFailoverTest) [RetryOnFailureOperation] ISPN004007: Exception encountered. Retry 3 out of 3
> org.infinispan.client.hotrod.exceptions.TransportException:: Could not fetch transport
> at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory.borrowTransportFromPool(TcpTransportFactory.java:426)
> at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory.getTransport(TcpTransportFactory.java:258)
> at org.infinispan.client.hotrod.impl.operations.AbstractKeyOperation.getTransport(AbstractKeyOperation.java:40)
> at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:55)
> at org.infinispan.client.hotrod.impl.RemoteCacheImpl.get(RemoteCacheImpl.java:366)
> at org.infinispan.client.hotrod.xsite.NonExistentNodeSiteDownFailoverTest.testRotateSiteDownFailover(NonExistentNodeSiteDownFailoverTest.java:51)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> org.infinispan.client.hotrod.exceptions.TransportException:: Could not fetch transport
> at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory.borrowTransportFromPool(TcpTransportFactory.java:426)
> at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory.getTransport(TcpTransportFactory.java:258)
> at org.infinispan.client.hotrod.impl.operations.AbstractKeyOperation.getTransport(AbstractKeyOperation.java:40)
> at org.infinispan.client.hotrod.impl.operations.RetryOnFailureOperation.execute(RetryOnFailureOperation.java:55)
> at org.infinispan.client.hotrod.impl.RemoteCacheImpl.get(RemoteCacheImpl.java:366)
> at org.infinispan.client.hotrod.xsite.NonExistentNodeSiteDownFailoverTest.testRotateSiteDownFailover(NonExistentNodeSiteDownFailoverTest.java:51)
> 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:498)
> at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84)
> at org.testng.internal.Invoker.invokeMethod(Invoker.java:714)
> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
> at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
> at org.testng.TestRunner.privateRun(TestRunner.java:767)
> at org.testng.TestRunner.run(TestRunner.java:617)
> at org.testng.SuiteRunner.runTest(SuiteRunner.java:348)
> at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:343)
> at org.testng.SuiteRunner.privateRun(SuiteRunner.java:305)
> at org.testng.SuiteRunner.run(SuiteRunner.java:254)
> at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
> at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
> at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224)
> at org.testng.TestNG.runSuitesLocally(TestNG.java:1149)
> at org.testng.TestNG.run(TestNG.java:1057)
> at org.testng.IDEARemoteTestNG.run(IDEARemoteTestNG.java:72)
> at org.testng.RemoteTestNGStarter.main(RemoteTestNGStarter.java:123)
> Caused by: org.infinispan.client.hotrod.exceptions.TransportException:: Could not connect to server: localhost:1234
> at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransport.<init>(TcpTransport.java:95)
> at org.infinispan.client.hotrod.impl.transport.tcp.TransportObjectFactory.makeObject(TransportObjectFactory.java:38)
> at org.infinispan.client.hotrod.impl.transport.tcp.TransportObjectFactory.makeObject(TransportObjectFactory.java:17)
> at org.apache.commons.pool.impl.GenericKeyedObjectPool.borrowObject(GenericKeyedObjectPool.java:1220)
> at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransportFactory.borrowTransportFromPool(TcpTransportFactory.java:420)
> ... 28 more
> Caused by: java.net.ConnectException: Connection refused
> at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
> at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
> at sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:111)
> at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransport.connectSocket(TcpTransport.java:107)
> at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransport.<init>(TcpTransport.java:84)
> ... 32 more
> {code}
> This issue only affects 9.1.x, master works fine.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (ISPN-6162) Drop Query.getResultSize() method
by Pedro Zapata Fernandez (Jira)
[ https://issues.redhat.com/browse/ISPN-6162?page=com.atlassian.jira.plugin... ]
Pedro Zapata Fernandez updated ISPN-6162:
-----------------------------------------
Sprint: DataGrid Sprint #41
> Drop Query.getResultSize() method
> ---------------------------------
>
> Key: ISPN-6162
> URL: https://issues.redhat.com/browse/ISPN-6162
> Project: Infinispan
> Issue Type: Task
> Components: Embedded Querying, Remote Querying
> Reporter: Tristan Tarrant
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 11.0.0.Final
>
>
> Do we keep org.infinispan.query.dsl.Query.getResultSize? Does it return int or long? Return -1 if actual figure unknown/hard to compute? Result size might be non-trivial for non-indexed or hybrid case and will require full scan even for queries with limit. Deprecate it now, remove in ispn 9.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month