June 2011 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-1205) Redesign marshallers to be per named cache instance, per thread

by Pete Muir (JIRA)

Redesign marshallers to be per named cache instance, per thread --------------------------------------------------------------- Key: ISPN-1205 URL: https://issues.jboss.org/browse/ISPN-1205 Project: Infinispan Issue Type: Feature Request Affects Versions: 5.0.0.CR6 Reporter: Pete Muir Assignee: Manik Surtani Fix For: 5.1.0.BETA1 Since we have switched to explicit classloaders in Infinispan 5.0, we can now pass the correct classloader to use into JBoss Marshalling, rather than rely on the TCCL. However at the moment marshallers are per thread, not per named cache instance. We will need to change the way marshallers are created to make a marshaller per-thread-per-named-cache-instance. This will also require investigation of the best way of propagating this through the DI system. Dan has previously suggested using the InvocationContext -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

3
11
0 / 0

[JBoss JIRA] Created: (ISPN-279) Avoid instance MarshalledValue accross the code

by Galder Zamarreno (JIRA)

Avoid instance MarshalledValue accross the code ----------------------------------------------- Key: ISPN-279 URL: https://jira.jboss.org/jira/browse/ISPN-279 Project: Infinispan Issue Type: Task Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.1.0.BETA1 Avoid doing things like this in EntryFactoryImpl or EventImpl and instead provide a way for key to be extracted when it somehow needs to be exported to the outside world when lazy serialization is on. if (key instanceof MarshalledValue) { key = ((MarshalledValue) key).get(); } -- 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

14 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (ISPN-1106) Rehashing into a running cluster causes shared processing lock contention

by Erik Salter (JIRA)

Rehashing into a running cluster causes shared processing lock contention ------------------------------------------------------------------------- Key: ISPN-1106 URL: https://issues.jboss.org/browse/ISPN-1106 Project: Infinispan Issue Type: Bug Affects Versions: 5.0.0.CR2 Reporter: Erik Salter Assignee: Manik Surtani On our initial test of 5.0.0.CR2, we wanted to test the cluster's rehashing behavior/performance and if all locks were cleaned up. The test was to start two nodes, then add a third node, all the while issuing commands to it. Upon adding a third node, the cluster becomes inoperable. The stack traces is in the following location: http://dl.dropbox.com/u/10929737/5.0.0.CR2/server_node1.log, http://dl.dropbox.com/u/10929737/5.0.0.CR2/server_node2.log, http://dl.dropbox.com/u/10929737/5.0.0.CR2/server_node3.log -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

6
19
0 / 0

[JBoss JIRA] Created: (ISPN-1206) rest and memcached server modules aren't isolated and affect each other

by Michal Linhard (JIRA)

rest and memcached server modules aren't isolated and affect each other ----------------------------------------------------------------------- Key: ISPN-1206 URL: https://issues.jboss.org/browse/ISPN-1206 Project: Infinispan Issue Type: Bug Components: Cache Server Affects Versions: 5.0.0.CR4 Reporter: Michal Linhard Assignee: Galder Zamarreño if we work with the same key with REST and memcached client at once, a server side class cast exception occurs because both work with different value representation: SERVER_ERROR java.lang.ClassCastException: [B cannot be cast to org.infinispan.server.memcached.MemcachedValue SERVER_ERROR java.lang.ClassCastException: [B cannot be cast to org.infinispan.server.core.CacheValue test: https://svn.devel.redhat.com/repos/jboss-qa/edg/edg-adapter/src/test/java... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
13
0 / 0

[JBoss JIRA] Created: (ISPN-842) FirstAvailable load balance policy for Hot Rod clients and extend reach of load balance policies

by Galder Zamarreño (JIRA)

FirstAvailable load balance policy for Hot Rod clients and extend reach of load balance policies ------------------------------------------------------------------------------------------------ Key: ISPN-842 URL: https://issues.jboss.org/browse/ISPN-842 Project: Infinispan Issue Type: Feature Request Components: Cache Server Reporter: Galder Zamarreño Assignee: Mircea Markus Fix For: 5.0.0.BETA1 Create a FirstAvailable load balance policy for Java Hot Rod clients and make sure load balance policies are used by all operations, particularly those extending AbstractKeyOperation. See forum thread for more info. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
12
0 / 0

[JBoss JIRA] Created: (ISPN-1212) Improved PING and FD protocols for the testsuite

by Galder Zamarreño (JIRA)

Improved PING and FD protocols for the testsuite ------------------------------------------------ Key: ISPN-1212 URL: https://issues.jboss.org/browse/ISPN-1212 Project: Infinispan Issue Type: Task Components: Test Suite Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.0.0.CR7 Create: - INFINISPAN_TEST_PING: use thread locals to maintain cluster membership since all tests run in same JVM. This would make discovery rock solid and would make the testsuite more robust. - INFINISPAN_TEST_FD: instead of relying on pings to check whether the node is there, attach a cache or cache manager listener to detect when a cache stops or fails and propagate that information back to the membership. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
12
0 / 0

[JBoss JIRA] Created: (ISPN-1108) Test(s) ignored by maven

by Mircea Markus (JIRA)

Test(s) ignored by maven ------------------------ Key: ISPN-1108 URL: https://issues.jboss.org/browse/ISPN-1108 Project: Infinispan Issue Type: Bug Components: Test Suite Affects Versions: 5.0.0.CR2 Reporter: Mircea Markus Assignee: Manik Surtani "mvn test" doesn't run the test TransactionsSpanningReplicatedCaches. It does run though other tests from that package, ex: TransactionsSpanningDistributedCachesTest. TransactionsSpanningReplicatedCaches is marked as sequential = true (which is redundant). I've tried removing the sequential attribute, but the same thing happened: the test was not run. The test runs successfully when specified through: mvn test -Dtest=TransactionsSpanningReplicatedCaches While here, also consider removing the mandatory "testName" attribute from @Tests. TestNG now has an @Test (singleThreaded) attribute that: "If set to true, all the methods on this test class are guaranteed to run sequentially, even if the tests are currently being run with parallel="true". This attribute can only be used at the class level and will be ignored if used at the method level." -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
10
0 / 0

[JBoss JIRA] Created: (ISPN-835) State transfer should not force all invocations to be synchronous

by Galder Zamarreño (JIRA)

State transfer should not force all invocations to be synchronous ----------------------------------------------------------------- Key: ISPN-835 URL: https://issues.jboss.org/browse/ISPN-835 Project: Infinispan Issue Type: Bug Components: RPC, State transfer Affects Versions: 4.2.0.CR4, 4.1.0.Final Reporter: Galder Zamarreño Assignee: Manik Surtani Fix For: 5.0.0.BETA1, 5.0.0.Final Enabling state transfer is forcing even asynchronous caches to become synchronous. A better way is needed to make sure state transfer works correctly (sync calls needed here) while normal replication calls remain asynchronous/ -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

5
34
0 / 0

[JBoss JIRA] Created: (ISPN-996) Create an infinispan-cdi module containing integration with CDI

by Manik Surtani (JIRA)

Create an infinispan-cdi module containing integration with CDI --------------------------------------------------------------- Key: ISPN-996 URL: https://issues.jboss.org/browse/ISPN-996 Project: Infinispan Issue Type: Feature Request Components: CDI integration Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.0.0.CR1, 5.0.0.FINAL Depends on SEAM-45 * Cache definition, configuration and injection * Caching content of producer methods on beans * Wiki/screencast to demonstrate usage -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

5
26
0 / 0

[JBoss JIRA] Created: (ISPN-359) Affinity accross caches - static or dynamic

by Tero Heinonen (JIRA)

Affinity accross caches - static or dynamic ------------------------------------------- Key: ISPN-359 URL: https://jira.jboss.org/jira/browse/ISPN-359 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Affects Versions: 4.0.0.Final Reporter: Tero Heinonen Assignee: Manik Surtani Programmable affinity either through: 1) statically (e.g. annotating a certain field as the key for consistent hashing) - in our case this cannot be based on the hashCode() as the affinity requirement and object identity are not directly related 2) dynamically (e.g. providing a overridable/annotatable consistentHashCode() function) This would help to assign entities (in multiple Caches), which are needed together in the same nodes (to avoid remote lookups) -- 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

14 years, 2 months

7
23
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2011