June 2010 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-486) Coherence transformer not working

by Mircea Markus (JIRA)

Coherence transformer not working --------------------------------- Key: ISPN-486 URL: https://jira.jboss.org/browse/ISPN-486 Project: Infinispan Issue Type: Bug Reporter: Mircea Markus Assignee: Manik Surtani see forum ref -- 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

14 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (ISPN-494) Hot Rod needs proxy address and port to work on cloud-like envs

by Galder Zamarreno (JIRA)

Hot Rod needs proxy address and port to work on cloud-like envs --------------------------------------------------------------- Key: ISPN-494 URL: https://jira.jboss.org/browse/ISPN-494 Project: Infinispan Issue Type: Feature Request Components: Cache Server Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.1.0.CR1 To get HotRod to work properly on environments such as ec2, a configurable proxy host+port are needed. Example: - Hot Rod running on an ec2 instance with elastic IP address 1.2.3.4 - If you bind to 0.0.0.0, Hot Rod server starts and serves requests via 1.2.3.4, but the exposed address in the topology is 0.0.0.0. Hence, client fails to connect to 0.0.0.0. - You can't have the Hot Rod bind to 1.2.3.4 since it does not exist in the ec2 instance. - So, a proxy address and port are needed so that these are published in topology views to external clients. -- 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

14 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (ISPN-482) CacheManager change to generics interface missing methods. Cannot hook it up to Hibernate 3.5.x

by Gisella Saavedra (JIRA)

CacheManager change to generics interface missing methods. Cannot hook it up to Hibernate 3.5.x ------------------------------------------------------------------------------------------------ Key: ISPN-482 URL: https://jira.jboss.org/browse/ISPN-482 Project: Infinispan Issue Type: Bug Components: Core API Affects Versions: 4.1.0.BETA2 Reporter: Gisella Saavedra Assignee: Manik Surtani Priority: Blocker The latest BETA2 release has a change for core interface org.infinispan.manager.CacheManager. Most of the methods are missing (from BETA1 and 4.0). The hibernate class InfinispanRegionFactory fails to create the CacheManager. manager.getGlobalConfiguration() does not exist!!!!!!!!!!!!!!!!! ------------------------- protected CacheManager createCacheManager(Properties properties) throws CacheException { try { String configLoc = PropertiesHelper.getString(INFINISPAN_CONFIG_RESOURCE_PROP, properties, DEF_INFINISPAN_CONFIG_RESOURCE); CacheManager manager = new DefaultCacheManager(configLoc, false); String globalStats = PropertiesHelper.extractPropertyValue(INFINISPAN_GLOBAL_STATISTICS_PROP, properties); if (globalStats != null) { manager.getGlobalConfiguration().setExposeGlobalJmxStatistics(Boolean.parseBoolean(globalStats)); } manager.start(); return manager; } catch (IOException e) { throw new CacheException("Unable to create default cache manager", e); } } -- 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

14 years, 6 months

3
3
0 / 0

[JBoss JIRA] Created: (ISPN-483) Send/receive buffer sizes configurable

by Galder Zamarreno (JIRA)

Send/receive buffer sizes configurable -------------------------------------- Key: ISPN-483 URL: https://jira.jboss.org/browse/ISPN-483 Project: Infinispan Issue Type: Feature Request Components: Cache Server Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.1.0.CR1 Make socket and send buffers sizes configurable for both Hot Rod client and server. -- 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

14 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (ISPN-489) Avoid reading cache name for default cache in Hot Rod

by Galder Zamarreno (JIRA)

Avoid reading cache name for default cache in Hot Rod ----------------------------------------------------- Key: ISPN-489 URL: https://jira.jboss.org/browse/ISPN-489 Project: Infinispan Issue Type: Task Components: Cache Server Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.1.0.CR1 Make talking to the default cache even more performant by avoiding "___defaultcache" string and instead if String length passed is 0, then we consider to be using the default cache. This requires changing the protocol definition accordingly and needs to verify that the Hot Rod client works as expected after these changes. -- 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

14 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (ISPN-491) Client and server not hashing on the same thing

by Galder Zamarreno (JIRA)

Client and server not hashing on the same thing ----------------------------------------------- Key: ISPN-491 URL: https://jira.jboss.org/browse/ISPN-491 Project: Infinispan Issue Type: Bug Components: Cache Server Affects Versions: 4.1.0.BETA2 Reporter: Galder Zamarreno Assignee: Galder Zamarreno Priority: Critical Fix For: 4.1.0.CR1 Yesterday while running a demo I spotted an issue with how distribution was working for Hot Rod clients. Basically, the client is calculating the hash code on the byte[] that's the key. However, in the server, the byte[] is wrapped behind a class called CacheKey and in this case, CacheKey's hashcode is computed and hash on that number is being calculated. This seem to be producing different results which means that the client is sending requests on a particular key to nodes that the server does not consider to be owner. There's two possibilities here: Either, the client wraps the byte[] around a CacheKey instance and calculate the hash on that, or the server abandons CacheKey and uses the byte[] directly as key. I don't think we can use the latter cos there's no such thing as a reasonable equals for arrays. IOW, you can't just expect to byte[] arrays to be equal if you call byteArray1.equals(byteArray2). You have to call Arrays.equals(byteArray1, byteArray2). Besides, the benefit of CacheKey is that it allows us to give a more meaningful toString representation [1] compared to standard byte[] toString. [1] override def toString = { new StringBuilder().append("CacheKey").append("{") .append("data=").append(Util.printArray(data, true)) .append("}").toString } -- 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

14 years, 7 months

1
3
0 / 0

[JBoss JIRA] Created: (ISPN-475) Upgrade Netty to latest version

by Galder Zamarreno (JIRA)

Upgrade Netty to latest version ------------------------------- Key: ISPN-475 URL: https://jira.jboss.org/browse/ISPN-475 Project: Infinispan Issue Type: Thirdparty Change Components: Cache Server Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.1.0.CR1 This is currently 3.2.0.Final but 3.2.1 will be released in the next few days. -- 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

14 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (ISPN-479) Reduce use of maps in Hot Rod to increase performance

by Galder Zamarreno (JIRA)

Reduce use of maps in Hot Rod to increase performance ----------------------------------------------------- Key: ISPN-479 URL: https://jira.jboss.org/browse/ISPN-479 Project: Infinispan Issue Type: Task Components: Cache Server Affects Versions: 4.1.0.BETA2 Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.1.0.CR1 There's no need for a map to resolve operation codes and flags, simply use a switch. 1.7% - 95,395 ms - 371,912 inv. org.infinispan.server.hotrod.RequestResolver$.toRequest (line\: 37) ... 1.3% - 71,870 ms - 262,761 inv. scala.Enumeration.apply (line\: 42) Similar thing for the version specific decoder but in this case, convert Decoder10 into a singleton object to get even more performance since its stateless and you avoid map lookups: 1.9% - 110 s - 404,990 inv. org.infinispan.server.hotrod.HotRodDecoder.getDecoder (line\: 54) -- 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

14 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (ISPN-476) Enable tcp no delay by default and make it configurable in servers

by Galder Zamarreno (JIRA)

Enable tcp no delay by default and make it configurable in servers ------------------------------------------------------------------ Key: ISPN-476 URL: https://jira.jboss.org/browse/ISPN-476 Project: Infinispan Issue Type: Feature Request Components: Cache Server Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.1.0.CR1 For increased performance of Hot Rod client and server, enable tcp no delay by default. Also, add configuration options to both client and server so that tcp no delay is configurable. -- 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

14 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (ISPN-477) Upgrade to Scala 2.8.0.RC3

by Galder Zamarreno (JIRA)

Upgrade to Scala 2.8.0.RC3 -------------------------- Key: ISPN-477 URL: https://jira.jboss.org/browse/ISPN-477 Project: Infinispan Issue Type: Thirdparty Change Components: Cache Server Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.1.0.CR1 Upgrade to Scala 2.8.0.RC3. Issues present in RC2 that lead to ISPN-436 do not appear to be present any more. -- 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

14 years, 7 months

1
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2010