January 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3453) Notification in case that entries have been lost

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3453?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-3453: ------------------------------------- Assignee: (was: Mircea Markus) > Notification in case that entries have been lost > ------------------------------------------------ > > Key: ISPN-3453 > URL: https://issues.jboss.org/browse/ISPN-3453 > Project: Infinispan > Issue Type: Feature Request > Components: State Transfer > Reporter: Radim Vansa > > Currently, when some entries are lost due to multiple node crash, the application executing requests against infinispan cache is not notified in any way - it just gets null response for subsequent requests for the lost entries. > IMO there should be at least an option to get exception if the cache gets corrupted in this way, so that the application will not produce further inconsistent data. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2442) Ability to take site offline needs to be extended to async replication

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2442?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-2442: ------------------------------------- Assignee: (was: Mircea Markus) > Ability to take site offline needs to be extended to async replication > ---------------------------------------------------------------------- > > Key: ISPN-2442 > URL: https://issues.jboss.org/browse/ISPN-2442 > Project: Infinispan > Issue Type: Feature Request > Components: Cross-Site Replication > Affects Versions: 5.2.0.Beta2 > Reporter: Erik Salter > > Currently the site offline implementation only accounts for synchronous caches. This needs to be extended to asynchronous replication as well. > Best case, this avoids wasted cycles and thread resources sending to a dead site. Worst case this could tie up all OOB threads, which could halt communication in the local site. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4290) jdbcStore oracle select sql with mixed case index name leads to table or view does not exist

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4290?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-4290: ------------------------------------- Assignee: (was: Mircea Markus) > jdbcStore oracle select sql with mixed case index name leads to table or view does not exist > -------------------------------------------------------------------------------------------- > > Key: ISPN-4290 > URL: https://issues.jboss.org/browse/ISPN-4290 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.2.Final > Reporter: Eric van Lydegraf > > This was discovered when adding JdbcStore to infinispan for hibernate-search lucene integration. The default cache names are mixed case. > e.g. > name="LuceneIndexesMetadata" > This leads to a syntax with select ... "LuceneIndexesMetadata". > In Oracle quotes on a table name mean exact match. > But most tools that will create the table (eg. liquibase, toad) do not put quotes > around the table name and hence is treated as all UPPERCASE in the database. > So then when infinispan tries to load the data, it fails on sql select with table or view does not exist. > The easy fix is to have the quote identifier return blank for oracle in TableManipulation class > line 454-466 > {code} > public String getIdentifierQuoteString() { > if(identifierQuoteString == null){ > switch (getDatabaseType()) { > case MYSQL: > identifierQuoteString = "`"; > break; > default: > identifierQuoteString = "\""; > break; > } > } > return identifierQuoteString; > } > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2198) Cluster with non-shared JDBC cache store has too much entries after node failure

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2198?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-2198: ------------------------------------- Assignee: (was: Mircea Markus) > Cluster with non-shared JDBC cache store has too much entries after node failure > -------------------------------------------------------------------------------- > > Key: ISPN-2198 > URL: https://issues.jboss.org/browse/ISPN-2198 > Project: Infinispan > Issue Type: Feature Request > Components: Loaders and Stores > Affects Versions: 5.1.5.FINAL > Reporter: Radim Vansa > Attachments: cache_entries.csv, logs.zip, sfout.txt > > > In resilience test with 4-node cluster where one node is killed a weird situation appears. Before the node kill have this number of entries: > 210602;215820;209400;203038 = 838860 entries > After the kill the number of entries changes for a while: > 210602;null;209400;203038 > 250602;null;269400;243038 > 290602;null;269400;273038 > 300602;null;289400;293038 > 300602;null;289400;293038 > 321218;null;296035;293038 > But then it stabilizes on > 326899;null;305039;314165 = 946103 entries > When the node02 is restarted it complains about duplicit entries: > ERROR [org.infinispan.loaders.jdbc.stringbased.JdbcStringBasedCacheStore] (OOB-124,null) ISPN008024: Error while storing string key to database; key: '8Az4Ia2V5NzYzNDI=', buffer size of value: 1050 bytes: com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry '?8Az4Ia2V5NzYzNDI=' for key 'PRIMARY' > Is this a bug or wrong configuration? > Here is an excerpt from configuration (sorry for no formatting): > <distributed-cache batching="false" indexing="NONE" l1-lifespan="0" mode="SYNC" name="memcachedCache" owners="2" remote-timeout="60000" start="EAGER" virtual-nodes="512"> > <locking acquire-timeout="3000" concurrency-level="1000" isolation="REPEATABLE_READ" striping="false"/> > <transaction mode="NONE"/> > <state-transfer enabled="true" timeout="600000"/> > <eviction max-entries="-1" strategy="NONE"/> > <string-keyed-jdbc-store datasource="java:jboss/datasources/JdbcDS" passivation="false" preload="false" purge="true" shared="false"> > <property name="databaseType">MYSQL</property> > <string-keyed-table prefix="node01"> > <id-column name="id" type="VARCHAR(100)"/> > <data-column name="value" type="BLOB(1200)"/> > </string-keyed-table> > </string-keyed-jdbc-store> > </distributed-cache> -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2397) Allow proper config of PooledConnectionFactory

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2397?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-2397: ------------------------------------- Assignee: (was: Mircea Markus) > Allow proper config of PooledConnectionFactory > ---------------------------------------------- > > Key: ISPN-2397 > URL: https://issues.jboss.org/browse/ISPN-2397 > Project: Infinispan > Issue Type: Feature Request > Components: Loaders and Stores > Affects Versions: 5.1.0.FINAL > Reporter: Thomas Kratz > Priority: Trivial > > mysql needs testConnection on checkout settings as those connection die after a certain time. > Currently it is not possible to set this on the c3p0 config. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1219) Add support for incremental optimistic locking

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-1219?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-1219: ------------------------------------- Assignee: (was: Mircea Markus) > Add support for incremental optimistic locking > ---------------------------------------------- > > Key: ISPN-1219 > URL: https://issues.jboss.org/browse/ISPN-1219 > Project: Infinispan > Issue Type: Feature Request > Components: Transactions > Reporter: Mircea Markus > Labels: deadlock, deadlock_detection > > This feature is fully described here: http://community.jboss.org/wiki/IncrementalOptimisticLocking > This together with lock reordering[1] cover 100% of the possible deadlock situations in the optimistic locking scheme[2]. > [1] http://community.jboss.org/wiki/LockReorderingForAvoidingDeadlocks > [2] http://community.jboss.org/wiki/OptimisticLockingInInfinispan -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4322) AS Remote Client Module Integration Tests module fails with IBM JDK

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-4322?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-4322: ------------------------------------- Assignee: (was: Mircea Markus) > AS Remote Client Module Integration Tests module fails with IBM JDK > ------------------------------------------------------------------- > > Key: ISPN-4322 > URL: https://issues.jboss.org/browse/ISPN-4322 > Project: Infinispan > Issue Type: Bug > Components: Integration > Affects Versions: 7.0.0.Alpha2, 7.0.0.Alpha3, 7.0.0.Alpha4 > Environment: IBM JDK, RHEL > Reporter: Vitalii Chepeliuk > Labels: testsuite_stability > > {noformat} > [INFO] ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] Infinispan BOM .................................... SUCCESS [10.419s] > [INFO] Infinispan Common Parent .......................... SUCCESS [16.691s] > [INFO] Infinispan Commons ................................ SUCCESS [30.414s] > [INFO] Infinispan Core ................................... SUCCESS [1:20:24.345s] > [INFO] Parent pom for server modules ..................... SUCCESS [2.764s] > [INFO] Infinispan Server - Core Components ............... SUCCESS [1:39.998s] > [INFO] Infinispan Query DSL API .......................... SUCCESS [3.182s] > [INFO] Parent pom for cachestore modules ................. SUCCESS [1.421s] > [INFO] Infinispan JDBC CacheStore ........................ SUCCESS [7:13.024s] > [INFO] Parent pom for the Lucene integration modules ..... SUCCESS [1.302s] > [INFO] Infinispan integration with Lucene v.3.x .......... SUCCESS [1:22.270s] > [INFO] Infinispan Lucene Directory Implementation ........ SUCCESS [5.801s] > [INFO] Infinispan Query API .............................. SUCCESS [16:27.946s] > [INFO] Infinispan Tools .................................. SUCCESS [12.958s] > [INFO] Infinispan Remote Query Client .................... SUCCESS [3.958s] > [INFO] Infinispan Remote Query Server .................... SUCCESS [16.646s] > [INFO] Infinispan JPA CacheStore ......................... SUCCESS [54.680s] > [INFO] Infinispan Hot Rod Server ......................... SUCCESS [6:13.951s] > [INFO] Infinispan Hot Rod Client ......................... SUCCESS [9:17.450s] > [INFO] Parent pom for compatibility modules .............. SUCCESS [0.876s] > [INFO] infinispan-custom52x-store ........................ SUCCESS [33.084s] > [INFO] infinispan-adaptor52x ............................. SUCCESS [4:05.587s] > [INFO] Infinispan remote CacheStore ...................... SUCCESS [53.506s] > [INFO] Infinispan LevelDB CacheStore ..................... SUCCESS [1:19.592s] > [INFO] Infinispan REST Server ............................ SUCCESS [2:08.409s] > [INFO] Infinispan REST CacheStore ........................ SUCCESS [16.715s] > [INFO] Infinispan Memcached Server ....................... SUCCESS [2:22.394s] > [INFO] Infinispan RHQ Plugin ............................. SUCCESS [42.140s] > [INFO] Infinispan CLI Server ............................. SUCCESS [48.143s] > [INFO] Infinispan CLI Client ............................. SUCCESS [16.878s] > [INFO] Infinispan CDI support ............................ SUCCESS [1:24.550s] > [INFO] Infinispan AS/EAP modules for library ............. SUCCESS [18.319s] > [INFO] Infinispan AS/EAP modules for remote client ....... SUCCESS [2.329s] > [INFO] Integration tests: Security Tests ................. SUCCESS [2:11.936s] > [INFO] Integration tests: SecurityManager tests .......... SUCCESS [13.313s] > [INFO] Integration tests: AS Module Integration Tests .... SUCCESS [1:10.370s] > [INFO] Integration tests: AS Remote Client Module Integration Tests FAILURE [57.162s] > [INFO] Integration tests: Lucene Directory with Infinispan Query SUCCESS [23.074s] > [INFO] Integration tests: Infinispan compatibility mode .. SUCCESS [35.351s] > [INFO] Infinispan Distribution ........................... SUCCESS [1.090s] > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 2:26:30.994s > [INFO] Finished at: Fri May 23 21:38:55 EDT 2014 > [INFO] Final Memory: 227M/542M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (infinispan-server-shutdown) on project infinispan-as-module-remote-client-integrationtests: An Ant BuildException has occured: Execute failed: java.io.IOException: Cannot run program "/qa/tools/opt/amd64/ibm-java-70/bin/jps" (in directory "/mnt/hudson_workspace/workspace/edg-60-ispn-testsuite-rhel/7e5d4f04/infinispan/integrationtests/as-integration-remote-client"): error=2, No such file or directory > [ERROR] around Ant part ...<exec executable="/qa/tools/opt/amd64/ibm-java-70/bin/jps" output="jps.pid" osfamily="unix"/>... @ 4:96 in /mnt/hudson_workspace/workspace/edg-60-ispn-testsuite-rhel/7e5d4f04/infinispan/integrationtests/as-integration-remote-client/target/antrun/build-main.xml > [ERROR] -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the command > [ERROR] mvn <goals> -rf :infinispan-as-module-remote-client-integrationtests > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3675) Revisit covariant return type for various implementations

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3675?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-3675: ------------------------------------- Assignee: (was: Mircea Markus) > Revisit covariant return type for various implementations > --------------------------------------------------------- > > Key: ISPN-3675 > URL: https://issues.jboss.org/browse/ISPN-3675 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 6.0.0.CR1 > Reporter: William Burns > > We use interfaces all over the place, which is great. However a lot of implementations currently only define their return types to be that of the type defined in the interface. However we can change the implementation return type of the method to be covariant which allows for direct users of the implementation to use the subclass if desired. > This especially came up in the discussion here: https://github.com/infinispan/infinispan/pull/2177/files#r7375883 as we could remove redundant casts which would provide cleaner code. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2334) Distributed mode and single shared cache loader - preload and state transfer

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2334?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-2334: ------------------------------------- Assignee: (was: Mircea Markus) > Distributed mode and single shared cache loader - preload and state transfer > ---------------------------------------------------------------------------- > > Key: ISPN-2334 > URL: https://issues.jboss.org/browse/ISPN-2334 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores, State Transfer > Affects Versions: 5.1.5.FINAL > Reporter: Fernando Wasylyszyn > Priority: Minor > > When you have a cluster in Infinispan, configured as Distributed and with a single and shared cache loader by all members, the preload option should work making each node loading the entries that correspond to it, not all of them, which is the current behaviour. > Also, with this configuration, the "state transfer" could be configured to make each node retrieve the "new entries" that should keep after a topology change directly from the cache store, instead of the transfer of entries through the network. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2673) maxEntries = 0 support for eviction

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-2673?page=com.atlassian.jira.plugin.... ] Tristan Tarrant reassigned ISPN-2673: ------------------------------------- Assignee: (was: Mircea Markus) > maxEntries = 0 support for eviction > ----------------------------------- > > Key: ISPN-2673 > URL: https://issues.jboss.org/browse/ISPN-2673 > Project: Infinispan > Issue Type: Feature Request > Components: Eviction > Affects Versions: 5.2.0.Beta6 > Reporter: Thomas Fromm > Priority: Minor > > To save memory I'd like to configure maxEntries to 0. > In case I use a Cache to share (possible) big data as entry between nodes. These data are persisted inside store and only used rarely. So I see two ways to realize that: > 1) I can set maxEntries to 0 so that after use the entry is evicted from cache. > 2) Have a cache mode which does not keep data in memory and just work transparent on the store. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 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 January 2015