September 2018 - infinispan-issues

[JBoss JIRA] (ISPN-9557) Third-party component alignment (compile/test-time deps only)

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9557?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9557: ---------------------------------- Sprint: Sprint 9.4.0.Final > Third-party component alignment (compile/test-time deps only) > ------------------------------------------------------------- > > Key: ISPN-9557 > URL: https://issues.jboss.org/browse/ISPN-9557 > Project: Infinispan > Issue Type: Component Upgrade > Components: Build > Affects Versions: 9.4.0.CR3 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.4.0.Final > > > We must align a number of 3rd party dependencies (not shipped) to reduce changes applied by the PME -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9557) Third-party component alignment (compile/test-time deps only)

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9557?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9557: ---------------------------------- Status: Open (was: New) > Third-party component alignment (compile/test-time deps only) > ------------------------------------------------------------- > > Key: ISPN-9557 > URL: https://issues.jboss.org/browse/ISPN-9557 > Project: Infinispan > Issue Type: Component Upgrade > Components: Build > Affects Versions: 9.4.0.CR3 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.4.0.Final > > > We must align a number of 3rd party dependencies (not shipped) to reduce changes applied by the PME -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9557) Third-party component alignment (compile/test-time deps only)

by Tristan Tarrant (JIRA)

Tristan Tarrant created ISPN-9557: ------------------------------------- Summary: Third-party component alignment (compile/test-time deps only) Key: ISPN-9557 URL: https://issues.jboss.org/browse/ISPN-9557 Project: Infinispan Issue Type: Component Upgrade Components: Build Affects Versions: 9.4.0.CR3 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 9.4.0.Final We must align a number of 3rd party dependencies (not shipped) to reduce changes applied by the PME -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9556) NoClassDefFoundError Log4J2Logger when running the fat-server in Openshift

by Diego Lovison (JIRA)

[ https://issues.jboss.org/browse/ISPN-9556?page=com.atlassian.jira.plugin.... ] Diego Lovison commented on ISPN-9556: ------------------------------------- It is impacting not only Openshift. This is from bare metal {noformat} [0m[0m19:45:45,846 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-6) DGISPN0001: Started rest cache from clustered container [0m[0m19:45:45,850 INFO [org.infinispan.server.endpoint] (MSC service thread 1-3) DGENDPT10000: MemcachedServer starting [0m[0m19:45:45,863 INFO [org.infinispan.server.endpoint] (MSC service thread 1-3) DGENDPT10001: MemcachedServer listening on 172.18.1.13:11211 [0m[33m19:45:45,884 WARN [org.jboss.modules.define] (MSC service thread 1-8) Failed to define class io.netty.util.internal.logging.Log4J2Logger in Module "io.netty:ispn-9.4" version 4.1.28.Final from local module loader @3796751b (finder: local module finder @67b64c45 (roots: /home_local/regression/servers/server6/modules,/home_local/regression/servers/server6/modules/system/layers/base,/home_local/regression/servers/server6/modules/system/add-ons/ispn)): java.lang.NoClassDefFoundError: Failed to link io/netty/util/internal/logging/Log4J2Logger (Module "io.netty:ispn-9.4" version 4.1.28.Final from local module loader @3796751b (finder: local module finder @67b64c45 (roots: /home_local/regression/servers/server6/modules,/home_local/regression/servers/server6/modules/system/layers/base,/home_local/regression/servers/server6/modules/system/add-ons/ispn))): org/apache/logging/log4j/spi/ExtendedLoggerWrapper at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:763) at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:423) at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:519) at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:339) at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:126) at org.jboss.modules.Module.loadModuleClass(Module.java:731) at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:247) at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:410) at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116) at io.netty.util.internal.logging.Log4J2LoggerFactory.newInstance(Log4J2LoggerFactory.java:33) at io.netty.util.internal.logging.InternalLoggerFactory.newDefaultFactory(InternalLoggerFactory.java:51) at io.netty.util.internal.logging.InternalLoggerFactory.getDefaultFactory(InternalLoggerFactory.java:67) at io.netty.util.internal.logging.InternalLoggerFactory.getInstance(InternalLoggerFactory.java:93) at io.netty.util.internal.logging.InternalLoggerFactory.getInstance(InternalLoggerFactory.java:86) at io.netty.util.internal.PlatformDependent.<clinit>(PlatformDependent.java:69) at io.netty.util.AsciiString.hashCode(AsciiString.java:1130) at java.util.HashMap.hash(HashMap.java:339) at java.util.HashMap.put(HashMap.java:612) at io.netty.handler.codec.http.cors.CorsConfigBuilder.build(CorsConfigBuilder.java:360) at org.infinispan.rest.configuration.RestServerConfigurationBuilder.corsAllowForLocalhost(RestServerConfigurationBuilder.java:75) at org.infinispan.server.endpoint.subsystem.RestService.start(RestService.java:119) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736) at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698) at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) at java.lang.Thread.run(Thread.java:748) [0m[0m19:45:46,137 INFO [org.jboss.as.clustering.infinispan] (MSC service thread 1-1) DGISPN0001: Started hotrodDist cache from clustered container {noformat} > NoClassDefFoundError Log4J2Logger when running the fat-server in Openshift > -------------------------------------------------------------------------- > > Key: ISPN-9556 > URL: https://issues.jboss.org/browse/ISPN-9556 > Project: Infinispan > Issue Type: Bug > Components: Server > Reporter: Diego Lovison > Assignee: Tristan Tarrant > Priority: Critical > Fix For: 9.4.0.Final > > > When running Infinispan server in Openshift it is failing due: > {noformat} > 18:25:53,529 WARN [org.jboss.modules.define] (MSC service thread 1-6) Failed to define class io.netty.util.internal.logging.Log4J2Logger in Module "io.netty:ispn-9.4" version 4.1.28.Final from local module loader @79b4d0f (finder: local module finder @6b2fad11 (roots: /opt/jboss/infinispan-server/modules,/opt/jboss/infinispan-server/modules/system/layers/base,/opt/jboss/infinispan-server/modules/system/add-ons/ispn)): java.lang.NoClassDefFoundError: Failed to link io/netty/util/internal/logging/Log4J2Logger (Module "io.netty:ispn-9.4" version 4.1.28.Final from local module loader @79b4d0f (finder: local module finder @6b2fad11 (roots: /opt/jboss/infinispan-server/modules,/opt/jboss/infinispan-server/modules/system/layers/base,/opt/jboss/infinispan-server/modules/system/add-ons/ispn))): org/apache/logging/log4j/spi/ExtendedLoggerWrapper > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8213) Functional commands are not replayed in tx on non-read owner

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-8213?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-8213: ------------------------------ Status: Open (was: New) > Functional commands are not replayed in tx on non-read owner > ------------------------------------------------------------ > > Key: ISPN-8213 > URL: https://issues.jboss.org/browse/ISPN-8213 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.1.0.Final > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.4.0.Final > > > When a functional command is executed on a node that is rebalancing and is not a read owner, we don't fetch the value (it does not end up in context's looked-up entries) but execute the command remotely in a read-only way. > The entry should be later written on this node, too, but EWI tries to commit only looked-up entries. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8213) Functional commands are not replayed in tx on non-read owner

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-8213?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-8213: ------------------------------ Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/6163 > Functional commands are not replayed in tx on non-read owner > ------------------------------------------------------------ > > Key: ISPN-8213 > URL: https://issues.jboss.org/browse/ISPN-8213 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.1.0.Final > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.4.0.Final > > > When a functional command is executed on a node that is rebalancing and is not a read owner, we don't fetch the value (it does not end up in context's looked-up entries) but execute the command remotely in a read-only way. > The entry should be later written on this node, too, but EWI tries to commit only looked-up entries. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8213) Functional commands are not replayed in tx on non-read owner

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-8213?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-8213: ------------------------------ Status: Resolved (was: Pull Request Sent) Resolution: Done > Functional commands are not replayed in tx on non-read owner > ------------------------------------------------------------ > > Key: ISPN-8213 > URL: https://issues.jboss.org/browse/ISPN-8213 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.1.0.Final > Reporter: Radim Vansa > Assignee: Radim Vansa > Fix For: 9.4.0.Final > > > When a functional command is executed on a node that is rebalancing and is not a read owner, we don't fetch the value (it does not end up in context's looked-up entries) but execute the command remotely in a read-only way. > The entry should be later written on this node, too, but EWI tries to commit only looked-up entries. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9514) Entry replaced with same expiration can expire immediately

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9514?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9514: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Entry replaced with same expiration can expire immediately > ---------------------------------------------------------- > > Key: ISPN-9514 > URL: https://issues.jboss.org/browse/ISPN-9514 > Project: Infinispan > Issue Type: Bug > Components: Expiration > Affects Versions: 9.3.3.Final > Reporter: William Burns > Assignee: William Burns > Fix For: 9.4.0.Final > > > Currently lifespan expiration removes an expired entry based on the key value and lifespan parameter matching. Unfortunately this still leaves it open to removing an entry that was just inserted if it was expired and it was replaced with the same value. > This is especially problematic with `RemoteCache.putIfAbsent` or other conditional operations as they perform a get before doing the actual operation. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9528) Docs: Clustered max-idle expiration

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-9528?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9528: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.4.0.Final Resolution: Done > Docs: Clustered max-idle expiration > ----------------------------------- > > Key: ISPN-9528 > URL: https://issues.jboss.org/browse/ISPN-9528 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation-Servers > Reporter: Don Naro > Assignee: Don Naro > Fix For: 9.4.0.Final > > > Documentation for clustered max-idle expiration. Review and edit docs from William plus add to them where needed: https://github.com/infinispan/infinispan/pull/5962/files#diff-91aad70e455... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9553) Upgrade JS client and Spark connector components

by Katia Aresti (JIRA)

[ https://issues.jboss.org/browse/ISPN-9553?page=com.atlassian.jira.plugin.... ] Katia Aresti updated ISPN-9553: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > Upgrade JS client and Spark connector components > ------------------------------------------------ > > Key: ISPN-9553 > URL: https://issues.jboss.org/browse/ISPN-9553 > Project: Infinispan > Issue Type: Component Upgrade > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 9.4.0.Final > > > JavaScript client can be upgraded to 0.5.0-SNAPSHOT > Spark connector can be upgraded to 0.9-SNAPSHOT -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues September 2018