March 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6401) Improve stability of ClientListenerLeakTest.testNoLeaksAfterShutdown

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6401?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6401: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Final 9.0.0.Alpha1 8.2.1.Final Resolution: Done Integrated in master and 8.2.x. Thanks [~sebastian.laskawiec]! > Improve stability of ClientListenerLeakTest.testNoLeaksAfterShutdown > -------------------------------------------------------------------- > > Key: ISPN-6401 > URL: https://issues.jboss.org/browse/ISPN-6401 > Project: Infinispan > Issue Type: Enhancement > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > Priority: Trivial > Fix For: 9.0.0.Final, 9.0.0.Alpha1, 8.2.1.Final > > > http://ci.infinispan.org/viewLog.html?buildId=37621&tab=buildResultsDiv&b... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6436) Overriding the name of an indexed property is not supported with DSL query

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6436?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6436: -------------------------------- Fix Version/s: 9.0.0.Final 9.0.0.Alpha1 8.2.1.Final > Overriding the name of an indexed property is not supported with DSL query > -------------------------------------------------------------------------- > > Key: ISPN-6436 > URL: https://issues.jboss.org/browse/ISPN-6436 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 8.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Final, 9.0.0.Alpha1, 8.2.1.Final > > > If @Field(name="xyz") is used on an object property this will lead to the property not being found by the parser. The parser still looks for it using java-beans naming conventions -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6436) Overriding the name of an indexed property is not supported with DSL query

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6436?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6436: -------------------------------- Affects Version/s: 8.0.0.Final > Overriding the name of an indexed property is not supported with DSL query > -------------------------------------------------------------------------- > > Key: ISPN-6436 > URL: https://issues.jboss.org/browse/ISPN-6436 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 8.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Final, 9.0.0.Alpha1, 8.2.1.Final > > > If @Field(name="xyz") is used on an object property this will lead to the property not being found by the parser. The parser still looks for it using java-beans naming conventions -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6436) Overriding the name of an indexed property is not supported with DSL query

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6436?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6436: -------------------------------- Description: If @Field(name="xyz") is used on an object property this will lead to the property not being found by the parser. The parser still looks for it using java-beans naming conventions > Overriding the name of an indexed property is not supported with DSL query > -------------------------------------------------------------------------- > > Key: ISPN-6436 > URL: https://issues.jboss.org/browse/ISPN-6436 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > > If @Field(name="xyz") is used on an object property this will lead to the property not being found by the parser. The parser still looks for it using java-beans naming conventions -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6436) Overriding the name of an indexed property is not supported with DSL query

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6436?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6436: -------------------------------- Status: Open (was: New) > Overriding the name of an indexed property is not supported with DSL query > -------------------------------------------------------------------------- > > Key: ISPN-6436 > URL: https://issues.jboss.org/browse/ISPN-6436 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Reporter: Adrian Nistor > Assignee: Adrian Nistor > > If @Field(name="xyz") is used on an object property this will lead to the property not being found by the parser. The parser still looks for it using java-beans naming conventions -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6436) Overriding the name of an indexed property is not supported with DSL query

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-6436: ----------------------------------- Summary: Overriding the name of an indexed property is not supported with DSL query Key: ISPN-6436 URL: https://issues.jboss.org/browse/ISPN-6436 Project: Infinispan Issue Type: Bug Components: Embedded Querying Reporter: Adrian Nistor Assignee: Adrian Nistor -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6430) Remote Queries do not allow per-entity index configurations

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6430?page=com.atlassian.jira.plugin.... ] Adrian Nistor commented on ISPN-6430: ------------------------------------- I'm not against it but we should find a good reason to have it. ATM all protobuf entities live in the same index and this spares us from the problems generated by creating indexes dynamically. We'll have to declare all indexed protobuf types at startup in the spirit of ISPN-6178 if we really want to split de indexes. I don't think that's nice for server mode. > Remote Queries do not allow per-entity index configurations > ----------------------------------------------------------- > > Key: ISPN-6430 > URL: https://issues.jboss.org/browse/ISPN-6430 > Project: Infinispan > Issue Type: Bug > Components: Remote Querying > Reporter: Gustavo Fernandes > > When using Infinispan in library mode, it's possible to define a per-entity index configuration, so this is possible: > {code:java} > cacheCfg.indexing().index(Index.ALL) > .addIndexedEntity(Car.class) > .addIndexedEntity(Person.class) > .addProperty("hibernate.search.person.directory_provider", "ram") > .addProperty("hibernate.search.car.indexmanager","org.infinispan.query.indexmanager.InfinispanIndexManager") > {code} > Different entities can live in different indexes, with a complete different storage and index manager. > Since when using remote queries there is a synthetic entity being created, this capability is lost. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-3037) Failing test: MixedModeTest.testMixedMode:72 NullPointer

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3037?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3037: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4182 > Failing test: MixedModeTest.testMixedMode:72 NullPointer > -------------------------------------------------------- > > Key: ISPN-3037 > URL: https://issues.jboss.org/browse/ISPN-3037 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 8.2.0.Final > Reporter: Sanne Grinovero > Assignee: Dan Berindei > Labels: testsuite_stability > Fix For: 9.0.0.Alpha1 > > > ~~~~~~~~~~~~~~~~~~~~~~~~~ ENVIRONMENT INFO ~~~~~~~~~~~~~~~~~~~~~~~~~~ > jgroups.bind_addr = 127.0.0.1 > java.runtime.version = 1.6.0_43-b01 > java.runtime.name =Java(TM) SE Runtime Environment > java.vm.version = 20.14-b01 > java.vm.vendor = Sun Microsystems Inc. > os.name = Linux > os.version = 3.8.8-202.fc18.x86_64 > sun.arch.data.model = 64 > sun.cpu.endian = little > protocol.stack = null > infinispan.test.jgroups.protocol = tcp > infinispan.unsafe.allow_jdk8_chm = true > java.net.preferIPv4Stack = true > java.net.preferIPv6Stack = null > log4.configuration = null > MAVEN_OPTS = null > ~~~~~~~~~~~~~~~~~~~~~~~~~ ENVIRONMENT INFO ~~~~~~~~~~~~~~~~~~~~~~~~~~ > Tests run: 2911, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 212.448 sec <<< FAILURE! > testMixedMode(org.infinispan.api.MixedModeTest) Time elapsed: 0.03 sec <<< FAILURE! > java.lang.NullPointerException > at org.infinispan.api.MixedModeTest.testMixedMode(MixedModeTest.java:72) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) > 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:334) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:37) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368) > at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) > at java.lang.Thread.run(Thread.java:662) > Results : > Failed tests: > MixedModeTest.testMixedMode:72 NullPointer > Tests run: 2911, Failures: 1, Errors: 0, Skipped: 0 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6435) Delete from non-exiting cache vie REST throws an error

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6435?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-6435: -------------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Final 9.0.0.Alpha1 Resolution: Done > Delete from non-exiting cache vie REST throws an error > ------------------------------------------------------ > > Key: ISPN-6435 > URL: https://issues.jboss.org/browse/ISPN-6435 > Project: Infinispan > Issue Type: Bug > Components: Server > Reporter: Vojtech Juranek > Assignee: Vojtech Juranek > Fix For: 9.0.0.Final, 9.0.0.Alpha1 > > > When removing an entry from non-exiting cache vie REST, server throws following error instead of returning HTTP 404: > {noformat} > 22:49:28,079 SEVERE [org.jboss.resteasy.plugins.server.netty.RequestHandler] (nioEventLoopGroup-9-1) Unexpected: org.jboss.resteasy.spi.UnhandledException: org.infinispan.rest.CacheNotFoundException: Cache with name 'nonexisting' not found amongst the configured caches > at org.jboss.resteasy.core.ExceptionHandler.handleApplicationException(ExceptionHandler.java:76) > at org.jboss.resteasy.core.ExceptionHandler.handleException(ExceptionHandler.java:212) > at org.jboss.resteasy.core.SynchronousDispatcher.writeException(SynchronousDispatcher.java:168) > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:411) > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:202) > at org.jboss.resteasy.plugins.server.netty.RequestDispatcher.service(RequestDispatcher.java:83) > at org.jboss.resteasy.plugins.server.netty.RequestHandler.channelRead0(RequestHandler.java:53) > at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105) > at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:308) > at io.netty.channel.AbstractChannelHandlerContext.access$600(AbstractChannelHandlerContext.java:32) > at io.netty.channel.AbstractChannelHandlerContext$7.run(AbstractChannelHandlerContext.java:299) > at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:380) > at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:357) > at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116) > at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137) > at java.lang.Thread.run(Thread.java:745) > Caused by: org.infinispan.rest.CacheNotFoundException: Cache with name 'nonexisting' not found amongst the configured caches > at org.infinispan.rest.RestCacheManager.getCache(RestCacheManager.scala:26) > at org.infinispan.rest.RestCacheManager.getInternalEntry(RestCacheManager.scala:47) > at org.infinispan.rest.Server.removeEntry(Server.scala:433) > 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:497) > at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:139) > at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:295) > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:249) > at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:236) > at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:395) > ... 12 more > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ISPN-6426) HotRodOperationsAuthzIT.testSupervisorStats always fails after ISPN-6333 fix

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6426?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-6426: -------------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Final Resolution: Done > HotRodOperationsAuthzIT.testSupervisorStats always fails after ISPN-6333 fix > ----------------------------------------------------------------------------- > > Key: ISPN-6426 > URL: https://issues.jboss.org/browse/ISPN-6426 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Reporter: Dan Berindei > Assignee: Anna Manukyan > Labels: testsuite_stability > Fix For: 9.0.0.Final, 9.0.0.Alpha1 > > > {noformat} > java.lang.AssertionError: Expected exception: org.infinispan.client.hotrod.exceptions.HotRodClientException > {noformat} > http://ci.infinispan.org/project.html?tab=testDetails&testNameId=57258273... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 2016