January 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3936) State transfer should not modify shared cache stores

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-3936?page=com.atlassian.jira.plugin.... ] Dan Berindei updated ISPN-3936: ------------------------------- Priority: Critical (was: Major) > State transfer should not modify shared cache stores > ---------------------------------------------------- > > Key: ISPN-3936 > URL: https://issues.jboss.org/browse/ISPN-3936 > Project: Infinispan > Issue Type: Bug > Components: Core, State Transfer > Affects Versions: 6.0.0.Final > Reporter: Dan Berindei > Assignee: Mircea Markus > Priority: Critical > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > > When installing a new topology, we invalidate the cache entries that are no longer mapped to the local node. We also iterate over the entries in the cache stores and delete the ones that are no longer local, but this should only happen if the cache store is not shared. > We had similar issues in the past, but this seems to be related to the new cache store API introduced in 6.0. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3935) True Async remote clients (HotRod, etc) API

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-3935?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-3935: ------------------------------ Description: Current RemoteCache xxxAsync methods are pseudo-async, they don't relay on NIO but just execute sync method version in separate thread. Please make them real async by supporting async operations at transport layer. was: Current RemoteCahe xxxAsync methods are pseudo-async, they don't relay on NIO but just executing sync method version in separate thread. Please make them real async by supporting async operations at transport layer. > True Async remote clients (HotRod, etc) API > ------------------------------------------- > > Key: ISPN-3935 > URL: https://issues.jboss.org/browse/ISPN-3935 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols > Affects Versions: 6.0.1.Final > Reporter: Alexander Furer > Assignee: Galder Zamarreño > Priority: Minor > > Current RemoteCache xxxAsync methods are pseudo-async, they don't relay on NIO but just execute sync method version in separate thread. > Please make them real async by supporting async operations at transport layer. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3935) True Async remote clients (HotRod, etc) API

by Radim Vansa (JIRA)

[ https://issues.jboss.org/browse/ISPN-3935?page=com.atlassian.jira.plugin.... ] Radim Vansa updated ISPN-3935: ------------------------------ Summary: True Async remote clients (HotRod, etc) API (was: True Async remote clients (HotRod, ect) API) > True Async remote clients (HotRod, etc) API > ------------------------------------------- > > Key: ISPN-3935 > URL: https://issues.jboss.org/browse/ISPN-3935 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Protocols > Affects Versions: 6.0.1.Final > Reporter: Alexander Furer > Assignee: Galder Zamarreño > Priority: Minor > > Current RemoteCahe xxxAsync methods are pseudo-async, they don't relay on NIO but just executing sync method version in separate thread. > Please make them real async by supporting async operations at transport layer. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3936) State transfer should not modify shared cache stores

by Dan Berindei (JIRA)

Dan Berindei created ISPN-3936: ---------------------------------- Summary: State transfer should not modify shared cache stores Key: ISPN-3936 URL: https://issues.jboss.org/browse/ISPN-3936 Project: Infinispan Issue Type: Bug Reporter: Dan Berindei Assignee: Mircea Markus -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3935) True Async remote clients (HotRod, ect) API

by Alexander Furer (JIRA)

Alexander Furer created ISPN-3935: ------------------------------------- Summary: True Async remote clients (HotRod, ect) API Key: ISPN-3935 URL: https://issues.jboss.org/browse/ISPN-3935 Project: Infinispan Issue Type: Feature Request Components: Remote Protocols Affects Versions: 6.0.1.Final Reporter: Alexander Furer Assignee: Galder Zamarreño Priority: Minor Current RemoteCahe xxxAsync methods are pseudo-async, they don't relay on NIO but just executing sync method version in separate thread. Please make them real async by supporting async operations at transport layer. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2895) org.infinispan.lucene.InfinispanDirectoryIOTest.testReadWholeFile fails randomly

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-2895?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-2895: -------------------------------- Status: Resolved (was: Pull Request Sent) Fix Version/s: 7.0.0.Alpha1 7.0.0.Final Resolution: Done Integrated in master. Thanks! > org.infinispan.lucene.InfinispanDirectoryIOTest.testReadWholeFile fails randomly > -------------------------------------------------------------------------------- > > Key: ISPN-2895 > URL: https://issues.jboss.org/browse/ISPN-2895 > Project: Infinispan > Issue Type: Bug > Components: Lucene Directory > Affects Versions: 5.2.2.Final > Reporter: Anna Manukyan > Assignee: Sanne Grinovero > Labels: stable_embedded_query, testsuite_stability > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > > The test fails randomly and the error message is: > {code} > java.lang.NullPointerException > at org.infinispan.lucene.DirectoryIntegrityCheck.verifyDirectoryStructure(DirectoryIntegrityCheck.java:76) > at org.infinispan.lucene.DirectoryIntegrityCheck.verifyDirectoryStructure(DirectoryIntegrityCheck.java:56) > at org.infinispan.lucene.InfinispanDirectoryIOTest.verifyOnBuffer(InfinispanDirectoryIOTest.java:184) > at org.infinispan.lucene.InfinispanDirectoryIOTest.testReadWholeFile(InfinispanDirectoryIOTest.java:153) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80) > at org.testng.internal.Invoker.invokeMethod(Invoker.java:715) > at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907) > at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237) > at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127) > at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111) > at org.testng.TestRunner.privateRun(TestRunner.java:767) > at org.testng.TestRunner.run(TestRunner.java:617) > at org.testng.SuiteRunner.runTest(SuiteRunner.java:334) > at org.testng.SuiteRunner.access$000(SuiteRunner.java:37) > at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368) > at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:722) > {code} -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3933) Preloading and Shared options can not be enabled on a JDBCCachestore via configuration files

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3933?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3933: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Integrated in master. Thanks! > Preloading and Shared options can not be enabled on a JDBCCachestore via configuration files > -------------------------------------------------------------------------------------------- > > Key: ISPN-3933 > URL: https://issues.jboss.org/browse/ISPN-3933 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 6.0.0.Final, 6.0.1.Final > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Priority: Critical > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > > The configuration schema doesn't allow to enable the "preload" attribute of a JDBCCacheStore. > I classify this as critical as the JDBCCacheStore is the only viable solution for a shared cachestore, and the Lucene Directory requires "preload" to be activated. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3934) Upgrade to Hibernate Search 4.5.0.CR1 and HQL-Parser 1.0.0.Alpha6

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-3934?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-3934: -------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done Integrated in master. Thanks! > Upgrade to Hibernate Search 4.5.0.CR1 and HQL-Parser 1.0.0.Alpha6 > ----------------------------------------------------------------- > > Key: ISPN-3934 > URL: https://issues.jboss.org/browse/ISPN-3934 > Project: Infinispan > Issue Type: Component Upgrade > Components: Embedded Querying > Reporter: Sanne Grinovero > Assignee: Sanne Grinovero > Fix For: 7.0.0.Alpha1 > > -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3868) Deadlock in RemoteCache getAsync

by Alexander Furer (JIRA)

[ https://issues.jboss.org/browse/ISPN-3868?page=com.atlassian.jira.plugin.... ] Alexander Furer commented on ISPN-3868: --------------------------------------- BTW, I see xnio library is already in dependency list, TcpTransport just need to be implemented over xnio api... > Deadlock in RemoteCache getAsync > -------------------------------- > > Key: ISPN-3868 > URL: https://issues.jboss.org/browse/ISPN-3868 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.0.Final > Environment: RemoteCahe component of 6.0.0.Final > Reporter: Alexander Furer > Assignee: Mircea Markus > Labels: remote > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > > Here is the implementation of remoteCahe.getAsync() : > {code} > public NotifyingFuture<V> getAsync(final K key) { > assertRemoteCacheManagerIsStarted(); > final NotifyingFutureImpl<V> result = new NotifyingFutureImpl<V>(); > Future<V> future = executorService.submit(new Callable<V>() { > @Override > public V call() throws Exception { > V toReturn = get(key); > result.notifyFutureCompletion(); > return toReturn; > } > }); > result.setExecuting(future); > return result; > } > {code} > 2 problems here : > 1. Callable's call method might be called BEFORE calling client had a chance to add listener (i.e. getAsync is not returned yet), in this case its' listener futureDone method will never be called. > 2. Even case #1 has not happened and notifyFutureCompletion is called on listener, but the future is not resolved yet : "call" has not returned, that's why the future that is passed to listener is not resolved, and calling future.get from listener blocks forever. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3868) Deadlock in RemoteCache getAsync

by Alexander Furer (JIRA)

[ https://issues.jboss.org/browse/ISPN-3868?page=com.atlassian.jira.plugin.... ] Alexander Furer edited comment on ISPN-3868 at 1/27/14 2:49 AM: ---------------------------------------------------------------- Sanne Can you please open action item to add async calls feature to Transport layer to track the issue ? Thanks was (Author: furic): Sanne Can you pleas open action item to add async calls feature to Transport layer to track the issue ? Thanks > Deadlock in RemoteCache getAsync > -------------------------------- > > Key: ISPN-3868 > URL: https://issues.jboss.org/browse/ISPN-3868 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 6.0.0.Final > Environment: RemoteCahe component of 6.0.0.Final > Reporter: Alexander Furer > Assignee: Mircea Markus > Labels: remote > Fix For: 7.0.0.Alpha1, 7.0.0.Final > > > Here is the implementation of remoteCahe.getAsync() : > {code} > public NotifyingFuture<V> getAsync(final K key) { > assertRemoteCacheManagerIsStarted(); > final NotifyingFutureImpl<V> result = new NotifyingFutureImpl<V>(); > Future<V> future = executorService.submit(new Callable<V>() { > @Override > public V call() throws Exception { > V toReturn = get(key); > result.notifyFutureCompletion(); > return toReturn; > } > }); > result.setExecuting(future); > return result; > } > {code} > 2 problems here : > 1. Callable's call method might be called BEFORE calling client had a chance to add listener (i.e. getAsync is not returned yet), in this case its' listener futureDone method will never be called. > 2. Even case #1 has not happened and notifyFutureCompletion is called on listener, but the future is not resolved yet : "call" has not returned, that's why the future that is passed to listener is not resolved, and calling future.get from listener blocks forever. -- 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

11 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 January 2014