September 2019 - infinispan-issues

[JBoss JIRA] (ISPN-10656) ClassNotFoundException: io.agroal.pool.DataSource

by Gustavo Lira e Silva (Jira)

Gustavo Lira e Silva created ISPN-10656: ------------------------------------------- Summary: ClassNotFoundException: io.agroal.pool.DataSource Key: ISPN-10656 URL: https://issues.jboss.org/browse/ISPN-10656 Project: Infinispan Issue Type: Bug Components: Dependency, Server Affects Versions: 10.0.0.CR2 Reporter: Gustavo Lira e Silva Assignee: Gustavo Lira e Silva Remote cache using JDBC cache store running on infinispan server is throwing {{ClassNotFoundException: io.agroal.pool.DataSource}} The following code was used: {code:java} GlobalConfigurationBuilder globalConfigurationBuilder = new GlobalConfigurationBuilder().defaultCacheName("default"); ConfigurationBuilder builder = new ConfigurationBuilder(); Configuration build = builder.persistence() .addStore(JdbcStringBasedStoreConfigurationBuilder.class) .table() .dropOnExit(true) .createOnStart(true) .tableNamePrefix("ISPN_STRING_TABLE") .idColumnName("ID_COLUMN").idColumnType("VARCHAR(255)") .dataColumnName("DATA_COLUMN").dataColumnType("VARBINARY(1000)") .timestampColumnName("TIMESTAMP_COLUMN").timestampColumnType("BIGINT") .connectionPool() .connectionUrl("jdbc:h2:mem:test;DB_CLOSE_DELAY=-1") .username("sa") .password("sa") .driverClass("org.h2.Driver") .build(); RemoteCache<String, String> cache = new RemoteCacheManager().administration().getOrCreateCache("test", builder.build()); cache.put("k1", "v1"); System.out.println(cache.get("k1")); {code} {{server/runtime/target/infinispan-server-10.0.0-SNAPSHOT/lib}} only have {{agroal-api.jar}}, {{agroal-pool.jar}} is missing -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10651) jars added to the server/lib folder are not adding classes to classpath

by Gustavo Lira e Silva (Jira)

[ https://issues.jboss.org/browse/ISPN-10651?page=com.atlassian.jira.plugin... ] Gustavo Lira e Silva reassigned ISPN-10651: ------------------------------------------- Assignee: Tristan Tarrant (was: Gustavo Lira e Silva) > jars added to the server/lib folder are not adding classes to classpath > ----------------------------------------------------------------------- > > Key: ISPN-10651 > URL: https://issues.jboss.org/browse/ISPN-10651 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 10.0.0.CR2 > Reporter: Gustavo Lira e Silva > Assignee: Tristan Tarrant > Priority: Major > Attachments: h2-1.4.199.jar, ispn10651.zip > > > {code:java} > GlobalConfigurationBuilder globalConfigurationBuilder = new GlobalConfigurationBuilder().defaultCacheName("default"); > ConfigurationBuilder builder = new ConfigurationBuilder(); > Configuration build = builder.persistence().addStore(JdbcStringBasedStoreConfigurationBuilder.class) > .table() > .dropOnExit(true) > .createOnStart(true) > .tableNamePrefix("ISPN_STRING_TABLE") > .idColumnName("ID_COLUMN").idColumnType("VARCHAR(255)") > .dataColumnName("DATA_COLUMN").dataColumnType("VARBINARY(1000)") > .timestampColumnName("TIMESTAMP_COLUMN").timestampColumnType("BIGINT") > .connectionPool() > .connectionUrl("jdbc:h2:mem:test;DB_CLOSE_DELAY=-1") > .username("sa") > .password("sa") > .driverClass("org.h2.Driver") > .build(); > RemoteCache<String, String> cache = new RemoteCacheManager().administration().getOrCreateCache("test", builder.build()); > cache.put("k1", "v1"); > System.out.println(cache.get("k1")); > {code} > If you place H2 driver inside ISPN_HOME/server/lib start the server and run the code above, you will receive ClassNotFoundException: org.h2.Driver -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10644) Random failures in JsonSerializationTest

by Ryan Emerson (Jira)

[ https://issues.jboss.org/browse/ISPN-10644?page=com.atlassian.jira.plugin... ] Ryan Emerson resolved ISPN-10644. --------------------------------- Fix Version/s: 10.0.0.CR3 Resolution: Done > Random failures in JsonSerializationTest > ---------------------------------------- > > Key: ISPN-10644 > URL: https://issues.jboss.org/browse/ISPN-10644 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 10.0.0.CR3 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10650) Expiration should not be replicated cross site

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10650?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-10650: ------------------------------ Git Pull Request: https://github.com/infinispan/infinispan/pull/7351, https://github.com/infinispan/infinispan/pull/7352 (was: https://github.com/infinispan/infinispan/pull/7351) > Expiration should not be replicated cross site > ---------------------------------------------- > > Key: ISPN-10650 > URL: https://issues.jboss.org/browse/ISPN-10650 > Project: Infinispan > Issue Type: Bug > Components: Cross-Site Replication, Expiration > Affects Versions: 9.4.16.Final, 10.0.0.CR2 > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.0.0.CR3, 9.4.17.Final > > > There is no reason currently to replicate expiration commands across site. > Lifespan will work just fine without without replicating as the entry is expired on either side properly, irrespective of system clocks. > However max idle doesn't support the given semantics with xsite. We currently only confirm from other nodes in the same cluster for max idle before removing. It would be extremely costly to query all the cross sites to see if they have a read on the same entry before expiring. Also this requires having system clocks somewhat close in time, which can be even more problematic with clusters in disparate locations. We need to document that this doesn't work as well. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10655) REST operation to return a list of counters

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-10655: -------------------------------------- Summary: REST operation to return a list of counters Key: ISPN-10655 URL: https://issues.jboss.org/browse/ISPN-10655 Project: Infinispan Issue Type: Bug Components: Clustered Counter, REST Affects Versions: 10.0.0.CR2 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 10.0.0.CR3 GET /v2/counters/ should return a list of available counter names -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10654) remote-sites element in embedded jgroups schema must be unbounded

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-10654: -------------------------------------- Summary: remote-sites element in embedded jgroups schema must be unbounded Key: ISPN-10654 URL: https://issues.jboss.org/browse/ISPN-10654 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 10.0.0.CR2 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 10.0.0.CR3 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10653) Upgrade to Elytron 1.10.1.Final

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-10653: -------------------------------------- Summary: Upgrade to Elytron 1.10.1.Final Key: ISPN-10653 URL: https://issues.jboss.org/browse/ISPN-10653 Project: Infinispan Issue Type: Component Upgrade Components: Security Affects Versions: 10.0.0.CR2 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 10.0.0.CR3 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10652) Agroal missing from serverng

by Tristan Tarrant (Jira)

Tristan Tarrant created ISPN-10652: -------------------------------------- Summary: Agroal missing from serverng Key: ISPN-10652 URL: https://issues.jboss.org/browse/ISPN-10652 Project: Infinispan Issue Type: Bug Components: Server Affects Versions: 10.0.0.CR2 Reporter: Tristan Tarrant Assignee: Tristan Tarrant Fix For: 10.0.0.CR3 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10652) Agroal missing from server

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10652?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10652: ----------------------------------- Summary: Agroal missing from server (was: Agroal missing from serverng) > Agroal missing from server > -------------------------- > > Key: ISPN-10652 > URL: https://issues.jboss.org/browse/ISPN-10652 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 10.0.0.CR2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.CR3 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10650) Expiration should not be replicated cross site

by Will Burns (Jira)

[ https://issues.jboss.org/browse/ISPN-10650?page=com.atlassian.jira.plugin... ] Will Burns updated ISPN-10650: ------------------------------ Status: Pull Request Sent (was: Coding In Progress) Git Pull Request: https://github.com/infinispan/infinispan/pull/7351 > Expiration should not be replicated cross site > ---------------------------------------------- > > Key: ISPN-10650 > URL: https://issues.jboss.org/browse/ISPN-10650 > Project: Infinispan > Issue Type: Bug > Components: Cross-Site Replication, Expiration > Affects Versions: 9.4.16.Final, 10.0.0.CR2 > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.0.0.CR3, 9.4.17.Final > > > There is no reason currently to replicate expiration commands across site. > Lifespan will work just fine without without replicating as the entry is expired on either side properly, irrespective of system clocks. > However max idle doesn't support the given semantics with xsite. We currently only confirm from other nodes in the same cluster for max idle before removing. It would be extremely costly to query all the cross sites to see if they have a read on the same entry before expiring. Also this requires having system clocks somewhat close in time, which can be even more problematic with clusters in disparate locations. We need to document that this doesn't work as well. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues September 2019