April 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-11556) SFS file location not relative to global persistent-location

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-11556?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-11556: ------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/8122, https://github.com/infinispan/infinispan/pull/8215, https://github.com/infinispan/infinispan/pull/8217, https://github.com/infinispan/infinispan/pull/8262 (was: https://github.com/infinispan/infinispan/pull/8122, https://github.com/infinispan/infinispan/pull/8215, https://github.com/infinispan/infinispan/pull/8217) > SFS file location not relative to global persistent-location > ------------------------------------------------------------ > > Key: ISPN-11556 > URL: https://issues.redhat.com/browse/ISPN-11556 > Project: Infinispan > Issue Type: Bug > Components: Configuration, Core > Affects Versions: 10.1.5.Final, 11.0.0.Dev03 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.1.7.Final, 11.0.0.Dev05 > > > Currently if a user specifies the location `/blah` in the SFS configuration, this location will be used regardless of the configure `persistent-location`. Instead, we should create the file location using `PersistenceUtil#getQualifiedLocation` and an exception will be thrown if `/blah` is not the root of the configure `persistent-location`. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11744) ConnectException for ManagedConnectionOperations in CentOS8

by Diego Lovison (Jira)

Diego Lovison created ISPN-11744: ------------------------------------ Summary: ConnectException for ManagedConnectionOperations in CentOS8 Key: ISPN-11744 URL: https://issues.redhat.com/browse/ISPN-11744 Project: Infinispan Issue Type: Bug Components: Server Affects Versions: 10.1.6.Final, 11.0.0.Dev04 Reporter: Diego Lovison ConnectException for ManagedConnectionOperations in CentOS8 It is working for CentOS7 {noformat} org.infinispan.commons.CacheException: Unable to start cache loaders org.infinispan.persistence.spi.PersistenceException: ISPN000527: Maximum startup attempts exceeded for store org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStore org.infinispan.persistence.spi.PersistenceException: This might be related to https://jira.jboss.org/browse/ISPN-604 org.h2.jdbc.JdbcSQLNonTransientConnectionException: Connection is broken: "java.net.ConnectException: Connection refused (Connection refused): 127.0.0.1:20000" [90067-199] java.net.ConnectException: Connection refused (Connection refused) at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:337) at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:176) at org.infinispan.client.hotrod.impl.transport.netty.HeaderDecoder.decode(HeaderDecoder.java:139) {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11744) ConnectException for ManagedConnectionOperations in CentOS8

by Diego Lovison (Jira)

[ https://issues.redhat.com/browse/ISPN-11744?page=com.atlassian.jira.plugi... ] Diego Lovison updated ISPN-11744: --------------------------------- Status: Open (was: New) > ConnectException for ManagedConnectionOperations in CentOS8 > ----------------------------------------------------------- > > Key: ISPN-11744 > URL: https://issues.redhat.com/browse/ISPN-11744 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 11.0.0.Dev04, 10.1.6.Final > Reporter: Diego Lovison > Priority: Major > > ConnectException for ManagedConnectionOperations in CentOS8 > It is working for CentOS7 > {noformat} > org.infinispan.commons.CacheException: Unable to start cache loaders > org.infinispan.persistence.spi.PersistenceException: ISPN000527: Maximum startup attempts exceeded for store org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStore > org.infinispan.persistence.spi.PersistenceException: This might be related to https://jira.jboss.org/browse/ISPN-604 > org.h2.jdbc.JdbcSQLNonTransientConnectionException: Connection is broken: "java.net.ConnectException: Connection refused (Connection refused): 127.0.0.1:20000" [90067-199] > java.net.ConnectException: Connection refused (Connection refused) > at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:337) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:176) > at org.infinispan.client.hotrod.impl.transport.netty.HeaderDecoder.decode(HeaderDecoder.java:139) > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11744) ConnectException for ManagedConnectionOperations in CentOS8

by Diego Lovison (Jira)

[ https://issues.redhat.com/browse/ISPN-11744?page=com.atlassian.jira.plugi... ] Diego Lovison reassigned ISPN-11744: ------------------------------------ Assignee: Diego Lovison > ConnectException for ManagedConnectionOperations in CentOS8 > ----------------------------------------------------------- > > Key: ISPN-11744 > URL: https://issues.redhat.com/browse/ISPN-11744 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 11.0.0.Dev04, 10.1.6.Final > Reporter: Diego Lovison > Assignee: Diego Lovison > Priority: Major > > ConnectException for ManagedConnectionOperations in CentOS8 > It is working for CentOS7 > {noformat} > org.infinispan.commons.CacheException: Unable to start cache loaders > org.infinispan.persistence.spi.PersistenceException: ISPN000527: Maximum startup attempts exceeded for store org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStore > org.infinispan.persistence.spi.PersistenceException: This might be related to https://jira.jboss.org/browse/ISPN-604 > org.h2.jdbc.JdbcSQLNonTransientConnectionException: Connection is broken: "java.net.ConnectException: Connection refused (Connection refused): 127.0.0.1:20000" [90067-199] > java.net.ConnectException: Connection refused (Connection refused) > at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:337) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:176) > at org.infinispan.client.hotrod.impl.transport.netty.HeaderDecoder.decode(HeaderDecoder.java:139) > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11744) ConnectException for ManagedConnectionOperations in CentOS8

by Diego Lovison (Jira)

[ https://issues.redhat.com/browse/ISPN-11744?page=com.atlassian.jira.plugi... ] Work on ISPN-11744 started by Diego Lovison. -------------------------------------------- > ConnectException for ManagedConnectionOperations in CentOS8 > ----------------------------------------------------------- > > Key: ISPN-11744 > URL: https://issues.redhat.com/browse/ISPN-11744 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 11.0.0.Dev04, 10.1.6.Final > Reporter: Diego Lovison > Assignee: Diego Lovison > Priority: Major > > ConnectException for ManagedConnectionOperations in CentOS8 > It is working for CentOS7 > {noformat} > org.infinispan.commons.CacheException: Unable to start cache loaders > org.infinispan.persistence.spi.PersistenceException: ISPN000527: Maximum startup attempts exceeded for store org.infinispan.persistence.jdbc.stringbased.JdbcStringBasedStore > org.infinispan.persistence.spi.PersistenceException: This might be related to https://jira.jboss.org/browse/ISPN-604 > org.h2.jdbc.JdbcSQLNonTransientConnectionException: Connection is broken: "java.net.ConnectException: Connection refused (Connection refused): 127.0.0.1:20000" [90067-199] > java.net.ConnectException: Connection refused (Connection refused) > at org.infinispan.client.hotrod.impl.protocol.Codec20.checkForErrorsInResponseStatus(Codec20.java:337) > at org.infinispan.client.hotrod.impl.protocol.Codec20.readHeader(Codec20.java:176) > at org.infinispan.client.hotrod.impl.transport.netty.HeaderDecoder.decode(HeaderDecoder.java:139) > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11624) Server patching tool

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-11624?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-11624: ------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/8235, https://github.com/infinispan/infinispan/pull/8261 (was: https://github.com/infinispan/infinispan/pull/8235) > Server patching tool > -------------------- > > Key: ISPN-11624 > URL: https://issues.redhat.com/browse/ISPN-11624 > Project: Infinispan > Issue Type: Feature Request > Components: CLI, Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Labels: supportability > Fix For: 10.1.7.Final, 11.0.0.Dev05 > > > Add patching commands to the CLI: > * *patch create* to create patch archives (zips) > * *patch ls* to list the patches applied to a server > * *patch describe* to describe the contents of a patch archive > * *patch install* to install a patch on a server > * *patch rollback* to roll back the server to the previous patch > The patch zip should contain all the artifacts to upgrade from any number of source versions to a target version and a series of json patch descriptor with instructions (ADD, REMOVE, REPLACE, UPGRADE) on how to apply those artifacts. Take into account files which can be modified by users (e.g. infinispan.xml) and in case of differences create them with a different filename (e.g infinispan.xml-11.0.1.Final) > The installation process will back up any artifacts that will be replaced/upgraded/removed so that they can be rolled back. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11709) The MassIndexer reports wrong status for local caches

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-11709?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-11709: ------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 10.1.7.Final 11.0.0.Dev05 Resolution: Done > The MassIndexer reports wrong status for local caches > ----------------------------------------------------- > > Key: ISPN-11709 > URL: https://issues.redhat.com/browse/ISPN-11709 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 11.0.0.Dev04, 10.1.6.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 10.1.7.Final, 11.0.0.Dev05 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11710) MassIndexer timeouts after 4 minutes

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-11710?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-11710: ------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 10.1.7.Final 11.0.0.Dev05 Resolution: Done > MassIndexer timeouts after 4 minutes > ------------------------------------ > > Key: ISPN-11710 > URL: https://issues.redhat.com/browse/ISPN-11710 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Affects Versions: 11.0.0.Dev04, 10.1.6.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 10.1.7.Final, 11.0.0.Dev05 > > > The MassIndexer on a clustered cache follows the Transport timeout configuration that is 4 minutes by default. On Local caches, it always uses 4 minutes (hardcoded). > Until it is possible to cancel the MassIndexer (see ISPN-11735), it should not timeout. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11643) REST connector misinterprets % in query path elements

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-11643?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-11643: ------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done > REST connector misinterprets % in query path elements > ----------------------------------------------------- > > Key: ISPN-11643 > URL: https://issues.redhat.com/browse/ISPN-11643 > Project: Infinispan > Issue Type: Bug > Affects Versions: 11.0.0.Dev04, 10.1.6.Final > Reporter: Tristan Tarrant > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 10.1.7.Final, 11.0.0.Dev05 > > > The REST resource manager performs a QueryStringDecoder.decodeComponent on path elements that have already bee decoded by Netty. This causes a path like `a%25bc` to be converted to `a%bc` but then converted again to `a�` -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11624) Server patching tool

by Tristan Tarrant (Jira)

[ https://issues.redhat.com/browse/ISPN-11624?page=com.atlassian.jira.plugi... ] Tristan Tarrant updated ISPN-11624: ----------------------------------- Fix Version/s: 10.1.7.Final > Server patching tool > -------------------- > > Key: ISPN-11624 > URL: https://issues.redhat.com/browse/ISPN-11624 > Project: Infinispan > Issue Type: Feature Request > Components: CLI, Server > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Labels: supportability > Fix For: 10.1.7.Final, 11.0.0.Dev05 > > > Add patching commands to the CLI: > * *patch create* to create patch archives (zips) > * *patch ls* to list the patches applied to a server > * *patch describe* to describe the contents of a patch archive > * *patch install* to install a patch on a server > * *patch rollback* to roll back the server to the previous patch > The patch zip should contain all the artifacts to upgrade from any number of source versions to a target version and a series of json patch descriptor with instructions (ADD, REMOVE, REPLACE, UPGRADE) on how to apply those artifacts. Take into account files which can be modified by users (e.g. infinispan.xml) and in case of differences create them with a different filename (e.g infinispan.xml-11.0.1.Final) > The installation process will back up any artifacts that will be replaced/upgraded/removed so that they can be rolled back. -- 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