April 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7761) Caffeine is included in both infinispan-all and infinispan-query-all shaded jars

by Katia Aresti (JIRA)

[ https://issues.jboss.org/browse/ISPN-7761?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-7761: ------------------------------- Status: Open (was: New) > Caffeine is included in both infinispan-all and infinispan-query-all shaded jars > -------------------------------------------------------------------------------- > > Key: ISPN-7761 > URL: https://issues.jboss.org/browse/ISPN-7761 > Project: Infinispan > Issue Type: Bug > Reporter: Sanne Grinovero > Assignee: Katia Aresti > Fix For: 9.1.0.Final, 9.0.1.Final, 9.1.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7751) Infinispan Query should not impose a transitive dependency on Elasticsearch clients

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-7751?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-7751: ---------------------------------- Status: Open (was: New) > Infinispan Query should not impose a transitive dependency on Elasticsearch clients > ----------------------------------------------------------------------------------- > > Key: ISPN-7751 > URL: https://issues.jboss.org/browse/ISPN-7751 > Project: Infinispan > Issue Type: Task > Components: Build process, Embedded Querying > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 9.0.1.Final, 9.1.0.Alpha1 > > > Besides being an unnecessary transitive dependency, it is causing the {{infinispan-embedded-query}} module to include it in the shaded jars. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7751) Infinispan Query should not impose a transitive dependency on Elasticsearch clients

by Sanne Grinovero (JIRA)

[ https://issues.jboss.org/browse/ISPN-7751?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-7751: ---------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5102 > Infinispan Query should not impose a transitive dependency on Elasticsearch clients > ----------------------------------------------------------------------------------- > > Key: ISPN-7751 > URL: https://issues.jboss.org/browse/ISPN-7751 > Project: Infinispan > Issue Type: Task > Components: Build process, Embedded Querying > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 9.0.1.Final, 9.1.0.Alpha1 > > > Besides being an unnecessary transitive dependency, it is causing the {{infinispan-embedded-query}} module to include it in the shaded jars. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7765) Allow HotRodDecoder to be shared between Netty pipelines

by Sebastian Łaskawiec (JIRA)

Sebastian Łaskawiec created ISPN-7765: ----------------------------------------- Summary: Allow HotRodDecoder to be shared between Netty pipelines Key: ISPN-7765 URL: https://issues.jboss.org/browse/ISPN-7765 Project: Infinispan Issue Type: Enhancement Reporter: Sebastian Łaskawiec Assignee: William Burns Currently {{HotRodDecoder}} instance can not be shared between Netty pipelines as {{HotRodEncoder}}. Currently each pipeline creates its own instance by calling: {code} server.getDecoder() {code} in {{NettyChannelInitializer#initializeChannel}}. We could probably make it a bit more efficient (or limit allocation rate at least) if we allow sharing single instance between pipelines. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7144) Cross-Site Replication: inconsistent data with multiple site masters

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-7144?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-7144: ------------------------------ Workaround Description: Set RELAY2.max_site_master=1 in JGroups configuration. Workaround: Workaround Exists > Cross-Site Replication: inconsistent data with multiple site masters > -------------------------------------------------------------------- > > Key: ISPN-7144 > URL: https://issues.jboss.org/browse/ISPN-7144 > Project: Infinispan > Issue Type: Bug > Components: Cross-Site Replication > Affects Versions: 9.0.0.Alpha4 > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 9.0.1.Final > > > Cross-Site replication with multiple site masters may not work properly when configured asynchronously. > It relies on the deliver order of the updates to the remote site but, with multiple site masters, it is possible an update to go through one of the possible routes. Having commands going through different routes violates the FIFO order needed leading to inconsistent data between sites. > Note: it doesn't happen in synchronous mode. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6250) The keys/values in TaskContext.getCache() are serialized in Server Task

by Michał Szynkiewicz (JIRA)

[ https://issues.jboss.org/browse/ISPN-6250?page=com.atlassian.jira.plugin.... ] Michał Szynkiewicz commented on ISPN-6250: ------------------------------------------ Thanks > The keys/values in TaskContext.getCache() are serialized in Server Task > ----------------------------------------------------------------------- > > Key: ISPN-6250 > URL: https://issues.jboss.org/browse/ISPN-6250 > Project: Infinispan > Issue Type: Bug > Components: Server, Test Suite - Server > Reporter: Anna Manukyan > Assignee: Michał Szynkiewicz > Attachments: LocalServerTaskIT.java, LocalTestServerTask.java > > > While trying to access cache entries in Server task, marshaller is required for unmarshalling them. > The test is running on the https://github.com/infinispan/infinispan/blob/master/server/integration/t... configuration. > Please find the sources attached. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7753) Compute, ComputeIfPresent, ComputeIfAbsent

by Katia Aresti (JIRA)

[ https://issues.jboss.org/browse/ISPN-7753?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-7753: ------------------------------- Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/5046 > Compute, ComputeIfPresent, ComputeIfAbsent > ------------------------------------------ > > Key: ISPN-7753 > URL: https://issues.jboss.org/browse/ISPN-7753 > Project: Infinispan > Issue Type: Sub-task > Reporter: Katia Aresti > Assignee: Katia Aresti > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7691) infinispan.client.hotrod.protocol_version ignored

by Katia Aresti (JIRA)

[ https://issues.jboss.org/browse/ISPN-7691?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-7691: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/5104 > infinispan.client.hotrod.protocol_version ignored > ------------------------------------------------- > > Key: ISPN-7691 > URL: https://issues.jboss.org/browse/ISPN-7691 > Project: Infinispan > Issue Type: Bug > Reporter: Gustavo Fernandes > Assignee: Katia Aresti > > Setting {{infinispan.client.hotrod.protocol_version}} via properties will not take effect due to a parsing error -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7691) infinispan.client.hotrod.protocol_version ignored

by Katia Aresti (JIRA)

[ https://issues.jboss.org/browse/ISPN-7691?page=com.atlassian.jira.plugin.... ] Katia Aresti commented on ISPN-7691: ------------------------------------ I managed to reproduce the code in TU. I didn't see the stack before because the code fails just logging the stack trace and I had a missing assertion. The pb is that some code has been modified to use an Enumeration for this particular property. So in order to map from String to Enum, Enum.valueOf(enumClass, value); is called. But the ProtocolVersion enumeration names are "PROTOCOL_VERSION_25" etc not "2.5", so it fails and returns the default Protocol Version. Unit test was missing for this property in the ConfigurationTest so nobody could see the pb before ! I'm doing a PR today that fixes the pb Katia > infinispan.client.hotrod.protocol_version ignored > ------------------------------------------------- > > Key: ISPN-7691 > URL: https://issues.jboss.org/browse/ISPN-7691 > Project: Infinispan > Issue Type: Bug > Reporter: Gustavo Fernandes > Assignee: Katia Aresti > > Setting {{infinispan.client.hotrod.protocol_version}} via properties will not take effect due to a parsing error -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7579) SimpleDateFormat is not thread safe

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-7579?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-7579: ----------------------------------------------- Jakub Senko <jsenko(a)redhat.com> changed the Status of [bug 1431965|https://bugzilla.redhat.com/show_bug.cgi?id=1431965] from POST to MODIFIED > SimpleDateFormat is not thread safe > ----------------------------------- > > Key: ISPN-7579 > URL: https://issues.jboss.org/browse/ISPN-7579 > Project: Infinispan > Issue Type: Bug > Components: Remote Protocols > Affects Versions: 9.0.0.CR2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.0.0.CR4 > > > {{org.infinispan.rest.Server}} has a static field of {{DatePatternRfc1123LocaleUS}}, wihich is an instance of {{SimpleDateFormat}}, and is causing the following error during a load test. > {code} > 2017-03-03 15:57:55,939 ERROR [org.jboss.resteasy.plugins.server.netty.i18n] (nioEventLoopGroup-6-8) RESTEASY018525: Unexpected: org.jboss.resteasy.spi.UnhandledException: java.lang.ArrayIndexOutOfBoundsException: -2147483648 > 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:54) > at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105) > at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:292) > at io.netty.channel.AbstractChannelHandlerContext.access$600(AbstractChannelHandlerContext.java:32) > at io.netty.channel.AbstractChannelHandlerContext$7.run(AbstractChannelHandlerContext.java:283) > at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:358) > at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:374) > at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112) > at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.ArrayIndexOutOfBoundsException: -2147483648 > at java.util.Calendar.getDisplayName(Calendar.java:2114) > at java.text.SimpleDateFormat.subFormat(SimpleDateFormat.java:1125) > at java.text.SimpleDateFormat.format(SimpleDateFormat.java:966) > at java.text.SimpleDateFormat.format(SimpleDateFormat.java:936) > at java.text.DateFormat.format(DateFormat.java:345) > at org.infinispan.rest.Server.org$infinispan$rest$Server$$formatDate(Server.scala:222) > at org.infinispan.rest.Server.org$infinispan$rest$Server$$getMimeEntry(Server.scala:140) > at org.infinispan.rest.Server$$anonfun$getEntry$1$$anonfun$apply$10.apply(Server.scala:98) > at org.infinispan.rest.Server$$anonfun$getEntry$1$$anonfun$apply$10.apply(Server.scala:96) > at org.infinispan.rest.Server.org$infinispan$rest$Server$$ensureFreshEnoughEntry(Server.scala:111) > at org.infinispan.rest.Server$$anonfun$getEntry$1.apply(Server.scala:95) > at org.infinispan.rest.Server$$anonfun$getEntry$1.apply(Server.scala:89) > at org.infinispan.rest.Server.protectCacheNotFound(Server.scala:498) > at org.infinispan.rest.Server.getEntry(Server.scala:89) > at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > 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 > {code} > A similar issue is found here: > https://github.com/rhuss/jolokia/issues/184 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 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 April 2017