January 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7350) InfinispanIndexProvider should provide sensible defaults for index caches

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-7350?page=com.atlassian.jira.plugin.... ] Galder Zamarreño resolved ISPN-7350. ------------------------------------ Fix Version/s: 9.0.0.Beta2 Resolution: Done > InfinispanIndexProvider should provide sensible defaults for index caches > ------------------------------------------------------------------------- > > Key: ISPN-7350 > URL: https://issues.jboss.org/browse/ISPN-7350 > Project: Infinispan > Issue Type: Enhancement > Components: Lucene Directory > Affects Versions: 9.0.0.Beta1 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.Beta2, 9.0.0.Final > > > InfinispanIndexProvider should provide sensible defaults for index caches when they haven't been provided by the user. A warning should also be logged when doing so, so that the user knows about this. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7066) The default cache configuration should not be applied to other caches

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-7066?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-7066: ----------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Beta2 Resolution: Done > The default cache configuration should not be applied to other caches > --------------------------------------------------------------------- > > Key: ISPN-7066 > URL: https://issues.jboss.org/browse/ISPN-7066 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Affects Versions: 8.2.3.Final, 8.2.4.Final > Reporter: Vladimir Dzhuvinov > Assignee: Tristan Tarrant > Fix For: 9.0.0.Beta2, 9.0.0.Final > > > Hi guys, > We noticed a weird behaviour of the Infinispan config where caches that are configured with no persistence assume the persistence configuration of the default cache for the cache container. This can potentially lead to some serious errors as data put into the other caches is getting written into the store of the default cache. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPRK-41) Update to Spark 2.1.0

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPRK-41?page=com.atlassian.jira.plugin.s... ] Gustavo Fernandes updated ISPRK-41: ----------------------------------- Status: Open (was: New) > Update to Spark 2.1.0 > --------------------- > > Key: ISPRK-41 > URL: https://issues.jboss.org/browse/ISPRK-41 > Project: Infinispan Spark > Issue Type: Component Upgrade > Affects Versions: 0.4 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 0.5 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPRK-41) Update to Spark 2.1.0

by Gustavo Fernandes (JIRA)

[ https://issues.jboss.org/browse/ISPRK-41?page=com.atlassian.jira.plugin.s... ] Gustavo Fernandes updated ISPRK-41: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan-spark/pull/45 > Update to Spark 2.1.0 > --------------------- > > Key: ISPRK-41 > URL: https://issues.jboss.org/browse/ISPRK-41 > Project: Infinispan Spark > Issue Type: Component Upgrade > Affects Versions: 0.4 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 0.5 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7384) org.infinispan.rest.TwoServerTest fail on Solaris Sparc

by Roman Macor (JIRA)

Roman Macor created ISPN-7384: --------------------------------- Summary: org.infinispan.rest.TwoServerTest fail on Solaris Sparc Key: ISPN-7384 URL: https://issues.jboss.org/browse/ISPN-7384 Project: Infinispan Issue Type: Bug Components: Server Affects Versions: 9.0.0.Beta1 Reporter: Roman Macor 03:45:36,742 ERROR (nioEventLoopGroup-3-1) [i18n] RESTEASY002010: Failed to execute javax.ws.rs.NotAllowedException: RESTEASY003650: No resource method found for v1PUT, return 405 with Allow header at org.jboss.resteasy.core.registry.SegmentNode.match(SegmentNode.java:382) at org.jboss.resteasy.core.registry.SegmentNode.match(SegmentNode.java:121) at org.jboss.resteasy.core.registry.RootNode.match(RootNode.java:43) at org.jboss.resteasy.core.registry.RootClassNode.match(RootClassNode.java:48) at org.jboss.resteasy.core.ResourceMethodRegistry.getResourceInvoker(ResourceMethodRegistry.java:445) at org.jboss.resteasy.core.SynchronousDispatcher.getInvoker(SynchronousDispatcher.java:264) at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:201) at org.jboss.resteasy.plugins.server.netty.RequestDispatcher.service(RequestDispatcher.java:83) at org.jboss.resteasy.plugins.server.netty.RequestHandler.channelRead0(RequestHandler.java:55)[UnitTestTestNGListener] Test testExtendedHeaders(org.infinispan.rest.TwoServerTest) failed. 03:45:36,747 ERROR (testng-TwoServerTest) [UnitTestTestNGListener] Test testExtendedHeaders(org.infinispan.rest.TwoServerTest) failed. java.lang.AssertionError: expected:<405> but was:<200> at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:743) at org.junit.Assert.assertEquals(Assert.java:118) at org.junit.Assert.assertEquals(Assert.java:555) at org.junit.Assert.assertEquals(Assert.java:542) at org.infinispan.rest.TwoServerTest.testExtendedHeaders(TwoServerTest.java:113) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)[UnitTestTestNGListener] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7383) Tests org.infinispan.server.test.client.rest.REST* fail on Solaris Sparc

by Roman Macor (JIRA)

Roman Macor created ISPN-7383: --------------------------------- Summary: Tests org.infinispan.server.test.client.rest.REST* fail on Solaris Sparc Key: ISPN-7383 URL: https://issues.jboss.org/browse/ISPN-7383 Project: Infinispan Issue Type: Bug Components: Server Affects Versions: 9.0.0.Beta1 Reporter: Roman Macor org.infinispan.server.test.client.rest.RESTAsyncClusteredIT(distmode-tcp).testDeleteOperation Error Message expected:<200> but was:<400> Stacktrace java.lang.AssertionError: expected:<200> but was:<400> ... Standard Output &amp#27;[31m14:34:06,092 ERROR [org.jboss.resteasy.resteasy_jaxrs.i18n] (nioEventLoopGroup-7-1) RESTEASY002005: Failed executing PUT /rest/testCache/0: org.jboss.resteasy.spi.ReaderException: java.lang.NullPointerException at org.jboss.resteasy.core.MessageBodyParameterInjector.inject(MessageBodyParameterInjector.java:184) at org.jboss.resteasy.core.MethodInjectorImpl.injectArguments(MethodInjectorImpl.java:91) at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:114) 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:402) at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:209) at org.jboss.resteasy.plugins.server.netty.RequestDispatcher.service(RequestDispatcher.java:83) at org.jboss.resteasy.plugins.server.netty.RequestHandler.channelRead0(RequestHandler.java:55) at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105) at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:372) at io.netty.channel.AbstractChannelHandlerContext.access$600(AbstractChannelHandlerContext.java:38) at io.netty.channel.AbstractChannelHandlerContext$7.run(AbstractChannelHandlerContext.java:363) at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163) at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:418) at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:440) at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:873) at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:144) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.NullPointerException at org.jboss.resteasy.util.ReadFromStream.readFromStream(ReadFromStream.java:30) at org.jboss.resteasy.plugins.providers.ByteArrayProvider.readFrom(ByteArrayProvider.java:35) at org.jboss.resteasy.plugins.providers.ByteArrayProvider.readFrom(ByteArrayProvider.java:23) at org.jboss.resteasy.core.interception.AbstractReaderInterceptorContext.readFrom(AbstractReaderInterceptorContext.java:61) at org.jboss.resteasy.core.interception.ServerReaderInterceptorContext.readFrom(ServerReaderInterceptorContext.java:60) at org.jboss.resteasy.core.interception.AbstractReaderInterceptorContext.proceed(AbstractReaderInterceptorContext.java:53) at org.jboss.resteasy.plugins.interceptors.encoding.GZIPDecodingInterceptor.aroundReadFrom(GZIPDecodingInterceptor.java:59) at org.jboss.resteasy.core.interception.AbstractReaderInterceptorContext.proceed(AbstractReaderInterceptorContext.java:55) at org.jboss.resteasy.core.MessageBodyParameterInjector.inject(MessageBodyParameterInjector.java:151) ... 19 more -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7378) Elasticsearch tests fail with 'Timed out while waiting for for index'

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-7378?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-7378: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Beta2 Resolution: Done > Elasticsearch tests fail with 'Timed out while waiting for for index' > --------------------------------------------------------------------- > > Key: ISPN-7378 > URL: https://issues.jboss.org/browse/ISPN-7378 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Query > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 9.0.0.Beta2 > > > Sometimes an Elasticsearch node fails to communicate with its peer, and the default retry is too long (5s) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7311) CacheJmxRegistration retains a lot of memory even though the JmxStatstics is turned off

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7311?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-7311: -------------------------------------- Priority: Minor (was: Major) > CacheJmxRegistration retains a lot of memory even though the JmxStatstics is turned off > --------------------------------------------------------------------------------------- > > Key: ISPN-7311 > URL: https://issues.jboss.org/browse/ISPN-7311 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 7.0.3.Final > Environment: Production > Reporter: Senthil Kumar Balakrishnan > Priority: Minor > Attachments: Screen Shot 2016-12-12 at 10.21.06 AM.png > > > In production environment we see a lot of JmxObjects getting created for each cache created in infinispan, it's very expensive in terms of memory usage. Is there a possibility to disable or not create these JmxObjects when the JmxStatistics are turned off ? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7353) Administration console - additional information in new script dialog is not displayed

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7353?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic reassigned ISPN-7353: ----------------------------------------- Assignee: Vladimir Blagojevic > Administration console - additional information in new script dialog is not displayed > ------------------------------------------------------------------------------------- > > Key: ISPN-7353 > URL: https://issues.jboss.org/browse/ISPN-7353 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Beta1 > Reporter: Roman Macor > Assignee: Vladimir Blagojevic > Priority: Minor > > Cache container -> Configuration -> Tasks -> Create new script -> hover over parameters information icon. > Result: > Information is not displayed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7353) Administration console - additional information in new script dialog is not displayed

by Vladimir Blagojevic (JIRA)

[ https://issues.jboss.org/browse/ISPN-7353?page=com.atlassian.jira.plugin.... ] Vladimir Blagojevic updated ISPN-7353: -------------------------------------- Priority: Minor (was: Major) > Administration console - additional information in new script dialog is not displayed > ------------------------------------------------------------------------------------- > > Key: ISPN-7353 > URL: https://issues.jboss.org/browse/ISPN-7353 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 9.0.0.Beta1 > Reporter: Roman Macor > Priority: Minor > > Cache container -> Configuration -> Tasks -> Create new script -> hover over parameters information icon. > Result: > Information is not displayed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2017