January 2011 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-841) Flag.CACHE_MODE_LOCAL is not working properly for put operation in TreeCache

by Konstantin Kuzmin (JIRA)

Flag.CACHE_MODE_LOCAL is not working properly for put operation in TreeCache ---------------------------------------------------------------------------- Key: ISPN-841 URL: https://issues.jboss.org/browse/ISPN-841 Project: Infinispan Issue Type: Bug Components: Tree API Affects Versions: 4.1.0.Final Environment: Windows XP Professional SP3 Reporter: Konstantin Kuzmin Assignee: Manik Surtani Actually, the problem might be wider. I suppose the Flag set is not propagated to underlying (Cache) infrastructure in some cases. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
14
0 / 0

[JBoss JIRA] Created: (ISPN-805) Use custom externalizers to improve performance of Lucene Directory

by Sanne Grinovero (JIRA)

Use custom externalizers to improve performance of Lucene Directory ------------------------------------------------------------------- Key: ISPN-805 URL: https://jira.jboss.org/browse/ISPN-805 Project: Infinispan Issue Type: Feature Request Components: Lucene Directory Reporter: Sanne Grinovero Assignee: Sanne Grinovero Priority: Minor Fix For: 5.0.0.ALPHA1 Use ISPN-244 to improve the Lucene Directory -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (ISPN-854) Query module unable to detect stopped state of Search engine (failing test)

by Sanne Grinovero (JIRA)

Query module unable to detect stopped state of Search engine (failing test) --------------------------------------------------------------------------- Key: ISPN-854 URL: https://issues.jboss.org/browse/ISPN-854 Project: Infinispan Issue Type: Bug Components: Querying Affects Versions: 5.0.0.ALPHA1 Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 5.0.0.BETA1 org.infinispan.query.blackbox.SearchFactoryShutdownTest is currently failing because of a change in Hibernate Search. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (ISPN-133) Upgrade JClouds to a version that depends on Apache HTTP Core that fixes HTTPCORE-199

by Galder Zamarreno (JIRA)

Upgrade JClouds to a version that depends on Apache HTTP Core that fixes HTTPCORE-199 ------------------------------------------------------------------------------------- Key: ISPN-133 URL: https://jira.jboss.org/jira/browse/ISPN-133 Project: Infinispan Issue Type: Thirdparty Change Components: Loaders and Stores Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.0.0.CR1 https://issues.apache.org/jira/browse/HTTPCORE-199 Remove temporary workaround in ISPN-119 as part of this: http://fisheye.jboss.org/browse/Infinispan/trunk/core/src/main/java/org/i... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

4
14
0 / 0

[JBoss JIRA] Created: (ISPN-838) Default for fetchInMemoryState should be true

by Galder Zamarreño (JIRA)

Default for fetchInMemoryState should be true --------------------------------------------- Key: ISPN-838 URL: https://issues.jboss.org/browse/ISPN-838 Project: Infinispan Issue Type: Task Components: Configuration, State transfer Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.0.0.BETA1 Currently the default for stateRetrieval.fetchInMemoryState is false, which means if someone writes: <stateRetrieval /> Then fetchInMemoryState is false, so no state transfer will occur. Instead, the default should be switched to true, cos it's the essence of state transfer. Otherwise, users are forced to write: <stateRetrieval fetchInMemoryState="true" /> -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
6
0 / 0

[JBoss JIRA] Assigned: (ISPN-39) Distributed executors

by Manik Surtani (JIRA)

[ https://issues.jboss.org/browse/ISPN-39?page=com.atlassian.jira.plugin.sy... ] Manik Surtani reassigned ISPN-39: --------------------------------- Assignee: Vladimir Blagojevic (was: Trustin Lee) > Distributed executors > --------------------- > > Key: ISPN-39 > URL: https://issues.jboss.org/browse/ISPN-39 > Project: Infinispan > Issue Type: Feature Request > Components: RPC > Reporter: Manik Surtani > Assignee: Vladimir Blagojevic > Priority: Critical > Labels: hackathon > Fix For: 5.0.0.BETA1, 5.0.0.Final > > > A new API to allow users to provide a Runnable/Callable and a set of keys to run this on, and the ability to move the code to where the data is and execute it there, returning results (if any) across a network. > Scope and objectives of this task are described in https://community.jboss.org/wiki/InfinispanDistributedExecutionFramework -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (ISPN-860) Rehashing into a running cluster causes lock timeouts and lock cleanup errors

by Erik Salter (JIRA)

[ https://issues.jboss.org/browse/ISPN-860?page=com.atlassian.jira.plugin.s... ] Erik Salter updated ISPN-860: ----------------------------- Attachment: multinode-rehash.zip > Rehashing into a running cluster causes lock timeouts and lock cleanup errors > ----------------------------------------------------------------------------- > > Key: ISPN-860 > URL: https://issues.jboss.org/browse/ISPN-860 > Project: Infinispan > Issue Type: Bug > Reporter: Erik Salter > Assignee: Manik Surtani > Attachments: multinode-rehash.zip > > > We are seeing some severe issues with a new node joining a cluster running transactions. Specifically, when a new node added to the system, some transactions running against the previous nodes will fail due to locks never being released. There will be a lot of lock timeouts as well. > All of our caches are in DIST mode. The number of owners is 3. We are also making liberal use of the new "eagerLockSingleNode" flag. > The attached test case illustrates the lock timeout problem. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (ISPN-376) Enable Infinispan standalone's Channel to be plugged with MessageListeners

by Galder Zamarreno (JIRA)

Enable Infinispan standalone's Channel to be plugged with MessageListeners -------------------------------------------------------------------------- Key: ISPN-376 URL: https://jira.jboss.org/jira/browse/ISPN-376 Project: Infinispan Issue Type: Feature Request Components: RPC Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 5.0.0.BETA1, 5.0.0.Final Investigate what would need doing to enable Infinispan to receive a JGroups' Channel or ChannelFactory that allows users to add their own message listeners when such clients want to be sending rpcs around. Brian will be using a solution like this for the AS case but since AS is owner of the Channel, this is relatively easy for it assuming that JGroups has the right API for it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (ISPN-329) Move coalesced logic from Unscheduled to Scheduled Write-Behind or asynchronous cache store

by Galder Zamarreno (JIRA)

Move coalesced logic from Unscheduled to Scheduled Write-Behind or asynchronous cache store ------------------------------------------------------------------------------------------- Key: ISPN-329 URL: https://jira.jboss.org/jira/browse/ISPN-329 Project: Infinispan Issue Type: Task Components: Loaders and Stores Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.1.0.BETA1 In the async cache store, remove coalescing of modifications from Unscheduled Write-Behind or strategy and move it to the Scheduled Write-Behind strategy. The aim of the Unscheduled strategy is to be as fast as possible. Having to deal with coalescing changes is only going to slow it down for very little gain. Coalescing changes in an schedule strategy makes a lot more sense. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (ISPN-313) Provide an StandaloneJGroupsChannelLookup implementation

by Galder Zamarreno (JIRA)

Provide an StandaloneJGroupsChannelLookup implementation -------------------------------------------------------- Key: ISPN-313 URL: https://jira.jboss.org/jira/browse/ISPN-313 Project: Infinispan Issue Type: Feature Request Components: RPC Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.1.0.BETA1 StandaloneJGroupsChannelLookup would target environments that are either standalone or within other app servers that are not JBoss. It would allow for different Infinispan configurations to use the same shared transport, reducing network configuration. Infinispan and StandaloneJGroupsChannelLookup, if you guys create such a class, have it use the ChannelFactory.createChannel(String stack_name) method, not the old legacy createMultiplexerChannel method used by JBC. ChannelFactory.createChannel(String stack_name) will be a stable API, createMultiplexerChannel(...) may go away in JGroups 3.0. ChannelFactory.createChannel(String stack_name) lets you get a shared transport channel if the stack's transport protocol config has the singleton_name element. Full thread can be found in forum reference link -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues January 2011