September 2011 - infinispan-issues

[JBoss JIRA] Updated: (ISPN-20) check whether locking in JDBC cache stores can be replaced with SELECT FOR UPDATE

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-20?page=com.atlassian.jira.plugin.sy... ] Galder Zamarreño updated ISPN-20: --------------------------------- Fix Version/s: 5.2.0.FINAL (was: 5.1.0.BETA1) (was: 5.1.0.FINAL) > check whether locking in JDBC cache stores can be replaced with SELECT FOR UPDATE > --------------------------------------------------------------------------------- > > Key: ISPN-20 > URL: https://issues.jboss.org/browse/ISPN-20 > Project: Infinispan > Issue Type: Feature Request > Components: Loaders and Stores, Locking and Concurrency > Reporter: Mircea Markus > Assignee: Galder Zamarreño > Labels: hackathon > Fix For: 5.2.0.FINAL > > > Not sure whether the 'outside' locking (MVCC) can't be used so that we won't need locking code within cache stores -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (ISPN-813) "Infinispan Cache Manager" option doesn't show up in the drop down menu for "Manually add" function

by Michal Linhard (JIRA)

"Infinispan Cache Manager" option doesn't show up in the drop down menu for "Manually add" function --------------------------------------------------------------------------------------------------- Key: ISPN-813 URL: https://jira.jboss.org/browse/ISPN-813 Project: Infinispan Issue Type: Bug Components: JMX, reporting and management Affects Versions: 4.2.0.CR2 Reporter: Michal Linhard Assignee: Manik Surtani infinispan 4.2.0.CR2 RHQ version: 3.0.0 build number: 59e9341 postgresql 8.4.5 I've setup RHQ with infinispan-jopr-plugin as described here: http://community.jboss.org/wiki/MonitoringInfinispanwithRHQ I'm running this on my local machine having these virtual interfaces 192.168.10.101 test1 192.168.10.102 test2 192.168.10.103 test3 192.168.10.104 test4 192.168.10.105 test5 192.168.10.106 test6 test1 - test4 running jboss 5.1.0.GA with infinispan-gridfs-webdav demo (ran with -Dcom.sun.management.jmxremote.port=6991 to 9664 respectively) test1 - test2 running rhq-agent bound to respective interface test5 running rhq-server sucessfully installed RHQ server sucessfully installed agents test1 test2 sucessfully imported platforms test1 and test2 sucessfully installed infinispan-jopr-plugin, updated agents tried to manually add Infinispan Cache Manager according to the instructions: "To add Infinispan instances manually, go to Resources > Platforms > localhost and then click on Inventory. At the bottom of the page, there's a section that says "Manually Add" and next to it there's a drop down list. Open this list, select "Infinispan Cache Manager" and click Ok." but the option "Infinispan Cache Manager" doesn't appear in the drop down box. i don't know wheter this is a RHQ bug or plugin bug or wheter there's something wrong with my installation steps. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
32
0 / 0

[JBoss JIRA] Created: (ISPN-575) Corruption in data when using a permanent store between stop-start cycles

by Sanne Grinovero (JIRA)

Corruption in data when using a permanent store between stop-start cycles ------------------------------------------------------------------------- Key: ISPN-575 URL: https://jira.jboss.org/browse/ISPN-575 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 4.1.0.CR2 Reporter: Sanne Grinovero Assignee: Manik Surtani Fix For: 4.1.0.Final We verified the issue while using the Lucene Directory; using the Directory under stress leads to no issues even during long running tests of several hours. If during the same stress test a permanent store is enabled, all works still fine, until the CacheManager is stopped. No errors during the stop(), but after starting it again the checksum on some data fails and the index is unusable. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

4
19
0 / 0

[JBoss JIRA] Created: (ISPN-1368) RpcManagerFactory should not create an RpcManager for local caches

by Galder Zamarreño (JIRA)

RpcManagerFactory should not create an RpcManager for local caches ------------------------------------------------------------------ Key: ISPN-1368 URL: https://issues.jboss.org/browse/ISPN-1368 Project: Infinispan Issue Type: Bug Components: RPC Affects Versions: 5.0.0.FINAL Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 6.0.0.FINAL As indicated in ISPN-1348, RpcManagerFactory should not create an RpcManager for those caches whose mode is LOCAL,, even if the transport is not null. Btw, I don't want this fixed till ISPN-1366 is in place, otherwise ISPN-1348 does become a problem and finding a solution for it without ISPN-1366 complicates things greatly. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (ISPN-1348) Cluster ID generator initialization might not work when default cache is not clustered

by Galder Zamarreño (JIRA)

Cluster ID generator initialization might not work when default cache is not clustered -------------------------------------------------------------------------------------- Key: ISPN-1348 URL: https://issues.jboss.org/browse/ISPN-1348 Project: Infinispan Issue Type: Bug Components: Cache Server Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.1.0.ALPHA1 This is related to the changes introduced as part of ISPN-1233. In Hot Rod servers, cluster ID generator initialization can fail to assign an initial view rank if the default cache is not clustered but other caches are. A better solution would be to simply cache the cache manager on construction, and if a new version for a clustered cache is created and the rank is not set yet (i.e. in cases such as AS7 where cache manager is started before the servers themselves), use the cached cache manager's transport to quickly calculate the view rank. This won't happen with Memcached because you can only interact with the default cache. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
6
0 / 0

[JBoss JIRA] Created: (ISPN-1366) Make it easier to get view id from EmbeddedCacheManager

by Galder Zamarreño (JIRA)

Make it easier to get view id from EmbeddedCacheManager ------------------------------------------------------- Key: ISPN-1366 URL: https://issues.jboss.org/browse/ISPN-1366 Project: Infinispan Issue Type: Enhancement Components: Core API, RPC Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 6.0.0.FINAL Getting the view ID from a cache manager is not very straightforward. This is located in Transport interface but this is not directly accessible EmbeddedCacheManager. At first glance, the only possible way to do it is by getting a reference to a cache, then getting the RPCManager from it and the transport associated with it. That's of course assuming the cache is clustered, otherwise it won't work. I'checking for other workarounds. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (ISPN-230) Enable JNDI binding of Cache/CacheManager out of the box

by Galder Zamarreno (JIRA)

Enable JNDI binding of Cache/CacheManager out of the box -------------------------------------------------------- Key: ISPN-230 URL: https://jira.jboss.org/jira/browse/ISPN-230 Project: Infinispan Issue Type: Feature Request Reporter: Galder Zamarreno Priority: Minor Fix For: 4.1.0.BETA1 Note that implementing this has no urgency since it does not really help Brian S for the JBoss AS integration. See: http://lists.jboss.org/pipermail/infinispan-dev/2009-October/001663.html So, I'm thinking that we could have a <jndi name="xyz"/> configuration option both at the global level (for Cache Manager) and at the Cache level. So, - if <jndi/> was present in the global section, we'd bind CacheManager to java:CacheManager - if <jndi name="xyz"/> was present in the global section, we'd bind CacheManager to java:xyz - if <jndi/> was present in the cache section, we'd bind Cache to java:<name-of-the-cache> - if <jndi name="xyz"/> was present in the cache section, we'd bind Cache to java:xyz -- 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, 3 months

3
3
0 / 0

[JBoss JIRA] Created: (ISPN-231) Replace use of ScheduledThreadPoolExecutor if affected by contention

by Galder Zamarreno (JIRA)

Replace use of ScheduledThreadPoolExecutor if affected by contention -------------------------------------------------------------------- Key: ISPN-231 URL: https://jira.jboss.org/jira/browse/ISPN-231 Project: Infinispan Issue Type: Task Reporter: Galder Zamarreno Assignee: Galder Zamarreno Priority: Minor Fix For: 4.1.0.BETA1 Verify whether JGRP-1051 affects Infinispan. -- 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, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (ISPN-1354) Support queue and topic structures

by Magnus Magnus (JIRA)

Support queue and topic structures ---------------------------------- Key: ISPN-1354 URL: https://issues.jboss.org/browse/ISPN-1354 Project: Infinispan Issue Type: Feature Request Reporter: Magnus Magnus Assignee: Manik Surtani Fix For: 5.1.0.FINAL, 5.2.0.FINAL Support distributed queue and topic structures -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

3
3
0 / 0

[JBoss JIRA] Created: (ISPN-1355) Create an ultra high performance serialization as an internal cache format. Eg: with Kryo

by Magnus Magnus (JIRA)

Create an ultra high performance serialization as an internal cache format. Eg: with Kryo ----------------------------------------------------------------------------------------- Key: ISPN-1355 URL: https://issues.jboss.org/browse/ISPN-1355 Project: Infinispan Issue Type: Feature Request Reporter: Magnus Magnus Assignee: Manik Surtani Fix For: 6.0.0.FINAL Create an ultra high performance serialization for internal cache format. Eg: with Kryo or something like that. Serialized data should be able to compress as well with a high performance compression algorithm. Use Snappy compression from Google. With this solution the memory requirement could be reduced. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues September 2011