April 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11676) Per-cache Hot Rod client configuration

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-11676?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-11676: ------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/8214, https://github.com/infinispan/infinispan/pull/8222 (was: https://github.com/infinispan/infinispan/pull/8214) > Per-cache Hot Rod client configuration > -------------------------------------- > > Key: ISPN-11676 > URL: https://issues.redhat.com/browse/ISPN-11676 > Project: Infinispan > Issue Type: Enhancement > Components: Hot Rod > Affects Versions: 11.0.0.Dev04, 10.1.6.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.1.7.Final, 11.0.0.Dev05 > > > Currently some configuration in the Hot Rod client is global (tx mode, force return values, near cache). We should introduce per-cache configuration. Additionally we should also be able to specify a server-side template/configuration to use if a cache doesn't exist. > {code:java} > builder > .remoteCache(cacheName) > .templateName("template") > .nearCacheMode(NearCacheMode.INVALIDATED) > .nearCacheMaxEntries(100) > .forceReturnValues(true); > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11575) Server properties realm should use encrypted salted passwords

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11575?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11575: ----------------------------------- Summary: Server properties realm should use encrypted salted passwords (was: Server properties realm should use encrypted salted password) > Server properties realm should use encrypted salted passwords > -------------------------------------------------------------- > > Key: ISPN-11575 > URL: https://issues.redhat.com/browse/ISPN-11575 > Project: Infinispan > Issue Type: Enhancement > Components: Security, Server > Affects Versions: 11.0.0.Dev03 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 11.0.0.Dev05 > > > Store the passwords in the property files using multiple formats suitable for the various mechs (Scram, Digest, etc) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11575) Server properties realm should use encrypted salted password

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11575?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11575: ----------------------------------- Description: Store the passwords in the property files using multiple formats suitable for the various mechs (Scram, Digest, etc) (was: Store the passwords in the property files using bcrypt salted encryption) > Server properties realm should use encrypted salted password > ------------------------------------------------------------- > > Key: ISPN-11575 > URL: https://issues.redhat.com/browse/ISPN-11575 > Project: Infinispan > Issue Type: Enhancement > Components: Security, Server > Affects Versions: 11.0.0.Dev03 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 11.0.0.Dev05 > > > Store the passwords in the property files using multiple formats suitable for the various mechs (Scram, Digest, etc) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11575) Server properties realm should use encrypted salted password

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11575?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11575: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8221 > Server properties realm should use encrypted salted password > ------------------------------------------------------------- > > Key: ISPN-11575 > URL: https://issues.redhat.com/browse/ISPN-11575 > Project: Infinispan > Issue Type: Enhancement > Components: Security, Server > Affects Versions: 11.0.0.Dev03 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 11.0.0.Dev05 > > > Store the passwords in the property files using bcrypt salted encryption -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11687) Infinispan not able to start after CR configuration change

by Marian Macik (Jira)

Marian Macik created ISPN-11687: ----------------------------------- Summary: Infinispan not able to start after CR configuration change Key: ISPN-11687 URL: https://issues.redhat.com/browse/ISPN-11687 Project: Infinispan Issue Type: Bug Components: OpenShift, Operator Affects Versions: 10.1.2.Final Reporter: Marian Macik Assignee: Vittorio Rigamonti Hi guys, as you may know, Kogito Operator uses Infinispan Operator to create a predefined Infinispan instance running on Openshift. Quite often we encounter an issue reproducible with these steps: 1. Install the Kogito Operator (this will also install Infinispan Operator). 2. Create a KogitoApp custom resource (CR) with this YAML: {code:yaml} apiVersion: app.kiegroup.org/v1alpha1 kind: KogitoApp metadata: name: example-quarkus spec: enablePersistence: true build: envs: # enable persistence - name: MAVEN_ARGS_APPEND value: "-Ppersistence" gitSource: contextDir: process-quarkus-example uri: 'https://github.com/kiegroup/kogito-examples' reference: master {code} This will create a KogitoApp CR and will tell the Kogito Operator to provision Infinispan with one replica. Kogito application runs on Quarkus which makes use of RemoteCacheManager of Quarkus Infinispan Client Extension. Up to this point, everything works, application is deployed. 3. Try change Infinispan config by editing Infinispan CR a few times and Infinispan won't be able to start properly. By editing I mean - change one of these 3 parameters: {code:yaml} ... spec: container: cpu: '' extraJvmOpts: '' memory: '' ... {code} I generally want to change the cpu and memory as defaults are too low and I am also specifying `-Xmx2G` to extraJvmOpts so Infinispan has more heap than 200 MB which is default. Anyway, if you do this change a couple of times and after each change you wait until Infinispan pod is restarted, after ~5 times you will see [java.nio.channels.OverlappingFileLockException|https://gist.github.com/Ma...] in the Infinispan pod log. There is also another issue attached at the bottom of the Gist which was observed in Openshift events logs. What I have found is that if I create only KogitoInfra CR, which will create Infinispan CR and won't run any KogitoApp, so there is nothing connected to Infinispan, I can restart it how many times I want and it will work without any issues. I even tried to store something to the Infinispan via Infinispan REST API from the pod and tried changing Infinispan configuration then, and it worked like a charm after each restart. However, as soon as I deploy KogitoApp so it is connected to Infinispan using HotRod client and change Infinispan CR a few times (after each change waiting for Infinispan pod to restart), it will break with the linked exception present in the logs. To me it seems that this stops working once there is actual connection to Infinispan using HotRod client. I am not sure how this client works internally, but I would think that in addition to real user data there is some sort of exchange of "control data" let's say in this protocol between client and Infinispan which might break if Infinispan is suddenly restarted? Not sure, but with pushing there data using REST API (so without HotRod client) where the connection is maintained only for the time of the request, the exception didn't occur. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10864) Scattered state transfer should be non blocking

by Will Burns (Jira)

[ https://issues.redhat.com/browse/ISPN-10864?page=com.atlassian.jira.plugi... ] Will Burns updated ISPN-10864: ------------------------------ Summary: Scattered state transfer should be non blocking (was: PrefetchInterceptor should use non blocking publisher and ban iterator) > Scattered state transfer should be non blocking > ----------------------------------------------- > > Key: ISPN-10864 > URL: https://issues.redhat.com/browse/ISPN-10864 > Project: Infinispan > Issue Type: Sub-task > Reporter: Will Burns > Priority: Major > > Scattered cache requires possibly checking if a segment is owned or not. This requires waiting for this to complete if it is in process. This means iterator will blocking waiting for this to occur. Thus we shouldn't utilize the iterator methods and instead provide a publisher that doesn't block properly. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11686) Windows batch files should use CR/LF

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11686?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11686: ----------------------------------- Status: Open (was: New) > Windows batch files should use CR/LF > ------------------------------------ > > Key: ISPN-11686 > URL: https://issues.redhat.com/browse/ISPN-11686 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 11.0.0.Dev04, 10.1.6.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.1.7.Final, 11.0.0.Dev05 > > > The Windows batch files should always maintain their CR/LF eols. Fix them and amend .gitattributes. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11686) Windows batch files should use CR/LF

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11686?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11686: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/8219, https://github.com/infinispan/infinispan/pull/8220 > Windows batch files should use CR/LF > ------------------------------------ > > Key: ISPN-11686 > URL: https://issues.redhat.com/browse/ISPN-11686 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 11.0.0.Dev04, 10.1.6.Final > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.1.7.Final, 11.0.0.Dev05 > > > The Windows batch files should always maintain their CR/LF eols. Fix them and amend .gitattributes. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11684) Errors not handled correctly when the cache is created

by Katia Aresti (Jira)

[ https://issues.redhat.com/browse/ISPN-11684?page=com.atlassian.jira.plugi... ] Katia Aresti updated ISPN-11684: -------------------------------- Git Pull Request: https://github.com/infinispan/infinispan-console/pull/6, https://github.com/infinispan/infinispan-console/pull/8 (was: https://github.com/infinispan/infinispan-console/pull/6) > Errors not handled correctly when the cache is created > ------------------------------------------------------ > > Key: ISPN-11684 > URL: https://issues.redhat.com/browse/ISPN-11684 > Project: Infinispan > Issue Type: Bug > Components: Console > Affects Versions: 10.1.6.Final > Reporter: Katia Aresti > Assignee: Katia Aresti > Priority: Critical > Labels: console-ng > > When a cache is created, errors are not handled correctly. We might get a 403 and not body text error. This leads into an Ok message that cofuses the users. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11686) Windows batch files should use CR/LF

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-11686: -------------------------------------- Summary: Windows batch files should use CR/LF Key: ISPN-11686 URL: https://issues.redhat.com/browse/ISPN-11686 Project: Infinispan Issue Type: Bug Components: Server Affects Versions: 10.1.6.Final, 11.0.0.Dev04 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 10.1.7.Final, 11.0.0.Dev05 The Windows batch files should always maintain their CR/LF eols. Fix them and amend .gitattributes. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 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 2020