September 2013 - infinispan-issues

[JBoss JIRA] (ISPN-3319) RemoteCacheStore should now be able to implement loadAllKeys

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-3319?page=com.atlassian.jira.plugin.... ] William Burns resolved ISPN-3319. --------------------------------- Fix Version/s: (was: 6.0.0.Beta2) Resolution: Out of Date This was fixed in ISPN-3290 with the refactoring. > RemoteCacheStore should now be able to implement loadAllKeys > ------------------------------------------------------------ > > Key: ISPN-3319 > URL: https://issues.jboss.org/browse/ISPN-3319 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Affects Versions: 5.3.0.Final > Reporter: William Burns > Assignee: Mircea Markus > > RemoteCacheStore can now utilize the RemoteCache.keySet method to retrieve all the keys for the loadAllKeys method. Currently it throws an exception. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3528) CacheLoaderInterceptor.visitEntrySetCommand can hang

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3528?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-3528: ------------------------------------ On a second thought, I think we need to support non-thread-safe tasks in {{PersistenceManager.processOnAllStores()}} as well, for some users the additional complexity of making the task thread-safe may not be worth the performance benefit. > CacheLoaderInterceptor.visitEntrySetCommand can hang > ---------------------------------------------------- > > Key: ISPN-3528 > URL: https://issues.jboss.org/browse/ISPN-3528 > Project: Infinispan > Issue Type: Bug > Components: Locking and Concurrency > Affects Versions: 6.0.0.Alpha4 > Reporter: Dan Berindei > Assignee: Mircea Markus > Priority: Critical > Fix For: 6.0.0.Beta2 > > > {{PersistenceManager.processOnAllStores}} receives a {{CacheLoaderTask}} parameter and calls it on potentially many threads concurrently. So the task object must be thread-safe. > The {{CacheLoaderTask}}&zwj;s used by {{CacheLoaderInterceptor.visitEntrySetCommand}}/{{visitKeySetCommand}}/{{visitValuesCommand}} are not thread-safe. They use a {{HashSet}} without any synchronization, and when accessed from concurrent threads the map can be corrupted. When this happens, the thread will block in an infinite loop: > {noformat} > "testng-LocalModeNoPassivationTest" prio=10 tid=0x00007f19141ac800 nid=0x622c runnable [0x00007f1902a62000] > java.lang.Thread.State: RUNNABLE > at java.util.HashMap.put(HashMap.java:498) > at java.util.HashSet.add(HashSet.java:217) > at java.util.AbstractCollection.addAll(AbstractCollection.java:342) > at org.infinispan.interceptors.CacheLoaderInterceptor.visitEntrySetCommand(CacheLoaderInterceptor.java:195) > ... > {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3517) Infinispan server ignores persistence configuration

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3517?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3517: -------------------------------- Issue Type: Bug (was: Feature Request) > Infinispan server ignores persistence configuration > --------------------------------------------------- > > Key: ISPN-3517 > URL: https://issues.jboss.org/browse/ISPN-3517 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 6.0.0.Alpha4 > Reporter: Mircea Markus > Assignee: Tristan Tarrant > Fix For: 6.0.0.Beta1 > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-469) Native Hot Rod client for .NET

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-469?page=com.atlassian.jira.plugin.s... ] Mircea Markus updated ISPN-469: ------------------------------- Fix Version/s: 6.0.0.Beta2 (was: 6.0.0.Beta1) > Native Hot Rod client for .NET > ------------------------------ > > Key: ISPN-469 > URL: https://issues.jboss.org/browse/ISPN-469 > Project: Infinispan > Issue Type: Feature Request > Components: Remote protocols > Environment: Must run .NET versions 4, 4.5 > Optional: .NET versions 3, 3.5 > Reporter: Manik Surtani > Assignee: Mircea Markus > Labels: jdg62 > Fix For: 6.0.0.Beta2, 6.0.0.CR1 > > > .NET client impl for HotRod. Protocol is documented here: > http://community.jboss.org/wiki/HotRodProtocol > Could be based off the Java reference impl client: > https://github.com/infinispan/infinispan/tree/master/client/hotrod-client -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-470) Native Hot Rod client for C++

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-470?page=com.atlassian.jira.plugin.s... ] Mircea Markus updated ISPN-470: ------------------------------- Fix Version/s: 6.0.0.Beta2 (was: 6.0.0.Beta1) > Native Hot Rod client for C++ > ----------------------------- > > Key: ISPN-470 > URL: https://issues.jboss.org/browse/ISPN-470 > Project: Infinispan > Issue Type: Feature Request > Components: Remote protocols > Environment: Windows, 64-bit, Visual Studio 2010* RHEL 6, 64-bit, RHEL 5, 64-bit > Reporter: Manik Surtani > Assignee: Mircea Markus > Priority: Blocker > Labels: jdg62 > Fix For: 6.0.0.Beta2, 6.0.0.CR1 > > Attachments: straw.patch > > > C++ client impl for HotRod. Protocol is documented here: > http://community.jboss.org/wiki/HotRodProtocol > Could be based off the Java reference impl client: > https://github.com/infinispan/infinispan/tree/master/client/hotrod-client -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-604) Re-design CacheStore transactions

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-604?page=com.atlassian.jira.plugin.s... ] Mircea Markus updated ISPN-604: ------------------------------- Fix Version/s: 6.0.0.Beta2 (was: 6.0.0.Beta1) > Re-design CacheStore transactions > ---------------------------------- > > Key: ISPN-604 > URL: https://issues.jboss.org/browse/ISPN-604 > Project: Infinispan > Issue Type: Sub-task > Components: Loaders and Stores, Transactions > Affects Versions: 4.0.0.Final, 4.1.0.CR2 > Reporter: Mircea Markus > Assignee: Mircea Markus > Labels: as7-ignored, modshape > Fix For: 6.0.0.Beta2, 6.0.0.CR1 > > > Current(4.1.x) transaction implementation in CacheStores is brocken in several ways: > 1st problem. > {code}AbstractCacheStore.prepare: > public void prepare(List<? extends Modification> mods, GlobalTransaction tx, boolean isOnePhase) throws CacheLoaderException { > if (isOnePhase) { > applyModifications(mods); > } else { > transactions.put(tx, mods); > } > } > {code} > If this is 1PC we apply the modifications in the prepare phase - we should do it in the commit phase (as JTA does it). > 2nd problem. > This currently exhibits during commit/rollback with JdbcXyzCacheStore, but it is rather a more general cache store issue. > When using a TransactionManager, during TM.commit AbstractCacheStore.commit is being called internally which tries to apply all the modifications that happened during that transaction. > Within the scope of AbstractCacheStore.commit, JdbcStore obtains a connection from a DataSource and tries to write the modifications on that connection. > Now if the DataSource is managed (e.g. by an A.S.) on the DS.getConnection call the A.S. would try to enlist the connection with the ongoing transaction by calling Transaction.enlistResource(XAResource xaRes) [1] > This method fails with an IllegalStateException, because the transaction's status is preparing (see javax.transaction.Transaction.enlistResource). > Suggested fix: > - the modifications should be registered to the transaction as they happen(vs. during prepare/commit as it happens now) > - this requires API changes in CacheStore, e.g. > void store(InternalCacheEntry entry) > should become > void store(InternalCacheEntry entry, GlobalTransaction gtx) > (gtx would be null if this is not a transactional call). > [1] This behavior is specified by the JDBC 2.0 Standard Extension API, chapter 7 - distributed transaction -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-484) Querying over HotRod

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-484?page=com.atlassian.jira.plugin.s... ] Mircea Markus updated ISPN-484: ------------------------------- Fix Version/s: 6.0.0.Beta2 (was: 6.0.0.Beta1) > Querying over HotRod > -------------------- > > Key: ISPN-484 > URL: https://issues.jboss.org/browse/ISPN-484 > Project: Infinispan > Issue Type: Feature Request > Components: Querying, Remote protocols > Reporter: Galder Zamarreño > Assignee: Adrian Nistor > Priority: Blocker > Labels: jdg62 > Fix For: 6.0.0.Beta2, 6.0.0.CR1 > > > The requirements are captured here: https://community.jboss.org/wiki/RemoteQueryDesignInInfinispan -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1986) Make putForExternalRead return a boolean instead of void

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1986?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1986: -------------------------------- Fix Version/s: 6.0.0.Beta2 (was: 6.0.0.Beta1) > Make putForExternalRead return a boolean instead of void > -------------------------------------------------------- > > Key: ISPN-1986 > URL: https://issues.jboss.org/browse/ISPN-1986 > Project: Infinispan > Issue Type: Enhancement > Components: Core API > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Priority: Critical > Fix For: 6.0.0.Beta2, 6.0.0.CR1 > > > Related to ISPN-1983 and https://hibernate.onjira.com/browse/HHH-7256, I'd like to change the API of putForExternalRead() to return a boolean instead of void. > The reason for doing this is to be able to find out if the PFER did actually end up storing something or not. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2034) Add backwards serialization compatibility tests

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2034?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2034: -------------------------------- Fix Version/s: 6.0.0.Beta2 (was: 6.0.0.Beta1) > Add backwards serialization compatibility tests > ----------------------------------------------- > > Key: ISPN-2034 > URL: https://issues.jboss.org/browse/ISPN-2034 > Project: Infinispan > Issue Type: Enhancement > Components: Marshalling > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Labels: compatibility > Fix For: 6.0.0.Beta2, 6.0.0.CR1 > > > Take each existing minor branch, i.e. 4.1.x, 4.0.x,...etc and modify VersionAwareMarshallerTest so that payloads are stored in a data file. > Then, take data files for each branch and store in git (master and 5.1.x), and try reading them with the existing externalizer/marshalling set up. > It should work... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1741) Remove old and deprecated pre-5.0 Configuration objects

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1741?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1741: -------------------------------- Fix Version/s: 6.0.0.Beta2 (was: 6.0.0.Beta1) > Remove old and deprecated pre-5.0 Configuration objects > ------------------------------------------------------- > > Key: ISPN-1741 > URL: https://issues.jboss.org/browse/ISPN-1741 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration > Affects Versions: 5.2.0.Final > Reporter: Manik Surtani > Assignee: Tristan Tarrant > Fix For: 6.0.0.Beta2, 6.0.0.CR1 > > > Remove the deprecated Configuration object altogether from the code base, and update all public APIs and SPIs accordingly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 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 September 2013