January 2017 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-7362) Use bundler no-bundler in the default UDP configuration

by Dan Berindei (JIRA)

Dan Berindei created ISPN-7362: ---------------------------------- Summary: Use bundler no-bundler in the default UDP configuration Key: ISPN-7362 URL: https://issues.jboss.org/browse/ISPN-7362 Project: Infinispan Issue Type: Task Components: Configuration, Core Affects Versions: 9.0.0.Beta1 Reporter: Dan Berindei Assignee: Dan Berindei Fix For: 9.0.0.Beta2 Large datagrams don't seem to work very well in some networks, like our QE cluster. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4810) Local Transactional Cache loses data when eviction is enabled and there are multiple readers and one writer

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4810?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4810: ----------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1202354|https://bugzilla.redhat.com/show_bug.cgi?id=1202354] from VERIFIED to CLOSED > Local Transactional Cache loses data when eviction is enabled and there are multiple readers and one writer > ----------------------------------------------------------------------------------------------------------- > > Key: ISPN-4810 > URL: https://issues.jboss.org/browse/ISPN-4810 > Project: Infinispan > Issue Type: Bug > Affects Versions: 6.0.2.Final > Environment: Windows 7 x64 (NTFS) > Oracle JDK1.7.0_40 > Apache Maven 3.0.5 > Reporter: Horia Chiorean > Assignee: William Burns > Labels: modeshape > Fix For: 7.2.0.Beta1, 5.2.12.Final, 5.2.13.Final > > Attachments: ispn_concurrent.zip > > > Using Infinispan 6.0.2 and a local, transactional cache backed by a <singleFile> store, with eviction enabled and a small {{max-entries}} setting, we have the following scenario: > * the main thread (i.e. the "writer") starts a transaction, adds a batch of strings into the cache and also appends the same strings into a List cache entry and then commits the transaction > * after the above has finished (i.e. after tx.commit) it fires a number of reader threads where each reader thread > ** checks that the string entries were added into the cache and > ** checks that the entries were correctly appended to the List entry > * the above steps are repeated a number of times > On any given run, based on timing, we're seeing that at some point (after some time) some of the reader threads will not see the latest version of the List entry (i.e. will not see the latest elements that were added into the list) but rather an old, stale List (sort of a "lost update" scenario). > If we either: > * disable eviction or > * set the {{max-entries}} to a large enough value (which I suspect has the same effect - not evicting anything) the problem doesn't show up. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3797) DataContainer should interact atomically with Persistence

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3797?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-3797: ----------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1202354|https://bugzilla.redhat.com/show_bug.cgi?id=1202354] from VERIFIED to CLOSED > DataContainer should interact atomically with Persistence > --------------------------------------------------------- > > Key: ISPN-3797 > URL: https://issues.jboss.org/browse/ISPN-3797 > Project: Infinispan > Issue Type: Enhancement > Components: Eviction, Loaders and Stores > Affects Versions: 6.0.0.Final, 5.2.10.Final > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Fix For: 7.0.0.Alpha3, 7.0.0.Final, 5.2.11.Final > > > DataContainer should handle atomically all the interactions with the Persistence. This includes all the eviction/passivation. > Main points: > * In DataContainer load/store will avoid any lose of data during concurrent operations > * Take advantage of CHMv8 > * CacheLoader and Writer Interceptors are no longer needed. > Check the mailling list for more info. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5526) Replication: The DELTA_WRITE flag should force a remote get during state transfer

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5526?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5526: ----------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1228780|https://bugzilla.redhat.com/show_bug.cgi?id=1228780] from VERIFIED to CLOSED > Replication: The DELTA_WRITE flag should force a remote get during state transfer > --------------------------------------------------------------------------------- > > Key: ISPN-5526 > URL: https://issues.jboss.org/browse/ISPN-5526 > Project: Infinispan > Issue Type: Bug > Affects Versions: 5.2.10.Final > Reporter: Dennis Reed > Assignee: Ryan Emerson > Priority: Critical > Fix For: 5.2.13.Final > > > Same issue as ISPN-3184, but for repl caches in Infinispan 5.2.x. > (ISPN-3184 only fixed dist caches, since repl uses the same code in 5.3+). > AtomicHashMap and FineGrainedAtomicHashMap, as well as custom DeltaAware implementations, use PutKeyValueCommands with the DELTA_WRITE flag to execute incremental updates. These commands need the previous value of the entry in order to work. > If a node is joining and it receives a PutKeyValueCommand with the DELTA_WRITE flag before it has received the value of the affected key, it should do a remote get to retrieve the previous value and apply the change on top of that value, just like we do for conditional commands. Not doing so leads to data loss. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3618) Cannot retrieve evicted entries from Microsoft SQL Server 2012/2008R2

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-3618?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-3618: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Beta2 9.0.0.Final Resolution: Done > Cannot retrieve evicted entries from Microsoft SQL Server 2012/2008R2 > --------------------------------------------------------------------- > > Key: ISPN-3618 > URL: https://issues.jboss.org/browse/ISPN-3618 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores, Server > Affects Versions: 6.0.0.CR1 > Reporter: Jakub Markos > Assignee: Ryan Emerson > Fix For: 9.0.0.Beta2, 9.0.0.Final > > Attachments: server_mssql2012_mysql55.log.zip > > > When using this configuration: > {code:xml} > <local-cache name="default" start="EAGER" batching="false"> > <locking isolation="READ_COMMITTED" acquire-timeout="20000" concurrency-level="500" striping="false" /> > <transaction mode="NONE" /> > <eviction strategy="LRU" max-entries="2"/> > <string-keyed-jdbc-store name="defaultStoreName" datasource="java:jboss/datasources/JdbcDS" passivation="false" preload="true" purge="false"> > <string-keyed-table prefix="EDG_STRING"> > <id-column name="id" type="VARCHAR(255)"/> > <data-column name="datum" type="VARBINARY(1000)"/> > <timestamp-column name="version" type="BIGINT"/> > </string-keyed-table> > </string-keyed-jdbc-store> > </local-cache> > {code} > and running this code: > {code} > RemoteCache<Object, Object> cache = new RemoteCacheManager(conf).getCache(); > cache.clear(); > cache.put(new Double(10), new Double(10)); > cache.put(new Double(20), new Double(20)); > cache.put(new Double(30), new Double(30)); // key 10 is evicted > System.out.println(cache.get(new Double(10))); > System.out.println(cache.get(new Double(20))); > System.out.println(cache.get(new Double(30))); > {code} > output: > {quote} > null > 20.0 > 30.0 > {quote} > Attached are logs for mssql2012 and mysql55 (where it works). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7292) SQL Server Upsert Errors

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/ISPN-7292?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7292: ---------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 9.0.0.Beta2 9.0.0.Final Resolution: Done > SQL Server Upsert Errors > ------------------------ > > Key: ISPN-7292 > URL: https://issues.jboss.org/browse/ISPN-7292 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 9.0.0.Beta1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.0.0.Beta2, 9.0.0.Final > > > When utilising upserts with SQL server an SQL exception is thrown due to a `ambiguous column name`. > The existing upstert statement also causes concurrency issues as SQL server does not handle MERGE statements atomically. Consequently it is necessary for a table lock to be acquired per merge statement in order to prevent deadlocks from occurring. See [here|https://www.mssqltips.com/sqlservertip/3074/use-caution-with-sql-ser...] for more details. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7230) XSite view should be logged at INFO

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-7230?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-7230: ----------------------------------- Fix Version/s: 9.0.0.Final > XSite view should be logged at INFO > ----------------------------------- > > Key: ISPN-7230 > URL: https://issues.jboss.org/browse/ISPN-7230 > Project: Infinispan > Issue Type: Feature Request > Components: Cross-Site Replication > Affects Versions: 9.0.0.Alpha4, 8.2.5.Final > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.0.0.Beta2, 9.0.0.Final > > > XSite view should be printed as INFO message. Currently, the only log messages printed are: > Site A: > {code} > 11:19:00,398 INFO [org.jgroups.protocols.relay.RELAY2] > (Timer-2,gs-macbook-pro-3) _gs-macbook-pro-3:LON: > joined bridge cluster 'xsite' > {code} > Site B: > {code} > 11:19:31,329 INFO [org.jgroups.protocols.relay.RELAY2] > (Timer-3,gs-macbook-pro-3) _gs-macbook-pro-3:NYC: > joined bridge cluster 'xsite' > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7231) XSite view should be available via JMX and DMR operations

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-7231?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-7231: ----------------------------------- Status: Open (was: New) > XSite view should be available via JMX and DMR operations > --------------------------------------------------------- > > Key: ISPN-7231 > URL: https://issues.jboss.org/browse/ISPN-7231 > Project: Infinispan > Issue Type: Feature Request > Components: Cross-Site Replication > Affects Versions: 9.0.0.Alpha4, 8.2.5.Final > Reporter: Galder Zamarreño > Fix For: 9.0.0.Beta2, 9.0.0.Final > > > XSite view is currently only available via TRACE messages in {{org.jgroups.protocols.relay.RELAY2}} class. The view should be also available via JMX and DMR. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7231) XSite view should be available via JMX and DMR operations

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-7231?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-7231: ----------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4769 > XSite view should be available via JMX and DMR operations > --------------------------------------------------------- > > Key: ISPN-7231 > URL: https://issues.jboss.org/browse/ISPN-7231 > Project: Infinispan > Issue Type: Feature Request > Components: Cross-Site Replication > Affects Versions: 9.0.0.Alpha4, 8.2.5.Final > Reporter: Galder Zamarreño > Fix For: 9.0.0.Beta2, 9.0.0.Final > > > XSite view is currently only available via TRACE messages in {{org.jgroups.protocols.relay.RELAY2}} class. The view should be also available via JMX and DMR. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7231) XSite view should be available via JMX and DMR operations

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-7231?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-7231: ----------------------------------- Fix Version/s: 9.0.0.Beta2 9.0.0.Final > XSite view should be available via JMX and DMR operations > --------------------------------------------------------- > > Key: ISPN-7231 > URL: https://issues.jboss.org/browse/ISPN-7231 > Project: Infinispan > Issue Type: Feature Request > Components: Cross-Site Replication > Affects Versions: 9.0.0.Alpha4, 8.2.5.Final > Reporter: Galder Zamarreño > Fix For: 9.0.0.Beta2, 9.0.0.Final > > > XSite view is currently only available via TRACE messages in {{org.jgroups.protocols.relay.RELAY2}} class. The view should be also available via JMX and DMR. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 2017