September 2011 - infinispan-issues

[JBoss JIRA] Created: (ISPN-907) SSL access to Hot Rod

by Galder Zamarreño (JIRA)

SSL access to Hot Rod --------------------- Key: ISPN-907 URL: https://issues.jboss.org/browse/ISPN-907 Project: Infinispan Issue Type: Feature Request Components: Cache Server Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.0.0.BETA1, 5.0.0.Final Investigate and integrate Adrian's patch for Hot Rod server so that it can accessed via SSL. Email from Adrian: "While I remember heres a patch to add ssl for infinispan clients. I did it a couple of weeks ago, but I dont know when Ill have time to finish it off/polish it. It was based on head a few weeks ago, but I dont remember which version. :-( The horrible part is the way I had to modify all the parameter lists. It could really do with passing some config object instead. I dont know how to make "git diff" include new uncommitted files so Ive attached them seperately. See the test for how to use it, but it is basically set the config properties (with the relevant infinispan package prefixes) use_ssl=true key_store_file_name=jks file containing our key key_store_password=secret trust_store_file_name=jks file containing public keys we trust for authentication trust_store_password=another-secret Optionally you can get the server to authenticate the client as well need_client_auth=true which means the server will need a trust store. I've also left it so if you dont set the properties it will use the default implementations. But this doesnt work out of the box unless you enable the "anon" alogorithms on the server, they aren't enabled by default. Those dont authenticate, they just encrypt the traffic. The main thing left to do would be change the test to get maven to generate the key/trust store in a well defined place in "target". Other comments: * The code on the serrver will also work for other protocols as well, e.g. memcached if the client supports ssl * The ssl context construction is pretty similar in the client/server and could probably be shared if I knew where to put shared stuff in the codebase. :-) * There is some commented out bits where I think the client/server should really be adding socket timeouts. Otherwise network drops/splits could cause the connection to hang forever. There should at least be a connection timeout on the socket construction, if you dont want to implement a full blown ping to continually test the connection rather than just ping on start - which doesnt run until after the connection timeout is needed. * I had to modify the system property handling so you can have a default of "null". I only did this for Strings, might not be relevant for others? * Why doesnt the client side do system property replacement like the server? * Theres a lot of places in the code doing InputStream is = openStream(); useIt(is); but never close the stream. While this is probably ok in infinispans use cases it is not good practice to leave files open for the gc to close - that could take a while to happen and you are hogging system resources. Either useIt() should close the stream or the code should be InputStream is = openStream(); try { useIt(is); } finally { is.close(); } Feel free to post whatever parts of this message you like in the infinispan forum. :-)" -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

4
8
0 / 0

[JBoss JIRA] Created: (ISPN-1295) Deprecate transport properties and replace with configuration on transport itself

by Pete Muir (JIRA)

Deprecate transport properties and replace with configuration on transport itself --------------------------------------------------------------------------------- Key: ISPN-1295 URL: https://issues.jboss.org/browse/ISPN-1295 Project: Infinispan Issue Type: Feature Request Affects Versions: 5.0.0.CR8 Reporter: Pete Muir Assignee: Manik Surtani Fix For: 5.1.0.ALPHA1 Currently transport properties are detyped and confusing for users as it sounds like the should actually configure properties of the transport, not properties of the transport configuration. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

4
10
0 / 0

[JBoss JIRA] Created: (ISPN-820) Resolve {@link} links in configuration reference

by Galder Zamarreño (JIRA)

Resolve {@link} links in configuration reference ------------------------------------------------- Key: ISPN-820 URL: https://jira.jboss.org/browse/ISPN-820 Project: Infinispan Issue Type: Feature Request Reporter: Galder Zamarreño Assignee: Vladimir Blagojevic Fix For: 5.0.0.BETA1 Currently configuration reference documentation does not resolve {@link} links. It'd be nice if it'd point to the javadoc of the corresponding class if available! Examples: - Fully qualified class name of a class that looks up a reference to a {@link javax.transaction.TransactionManager}. The default provided is capable of locating the default TransactionManager in most popular Java EE systems, using a JNDI lookup. (Javadoc) - Fully qualified name of the class that the configured {@link org.infinispan.marshall.Externalizer} can marshall/unmarshall. Establishing the link between type marshalled and {@link org.infinispan.marshall.Externalizer} implementations enables users to provide their own marshalling mechanisms even for classes which they cannot modify or extend. (Javadoc) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

5
13
0 / 0

[JBoss JIRA] Created: (ISPN-1186) Document different approaches for working with cache statistics for local cache and remote cache (HotRod)

by Martin Gencur (JIRA)

Document different approaches for working with cache statistics for local cache and remote cache (HotRod) ---------------------------------------------------------------------------------------------------------- Key: ISPN-1186 URL: https://issues.jboss.org/browse/ISPN-1186 Project: Infinispan Issue Type: Task Affects Versions: 4.2.1.FINAL Reporter: Martin Gencur Assignee: Mircea Markus Priority: Optional Fix For: 5.0.0.CR6, 5.0.0.FINAL The documentation for Infinispan should mention different approaches for accessing remote cache (HotRod) and local (default) cache statistics. For example, there is not "evictions" statistics for remote cache. Maybe it would be enough to just mention different classes that hold these statistics (Stats and RemoteStatistics) and the way of getting them. It should be mentioned most likely somewhere under http://community.jboss.org/wiki/infinispan -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

4
13
0 / 0

[JBoss JIRA] Created: (ISPN-767) Make deadlock detection run over multiple caches

by Mircea Markus (JIRA)

Make deadlock detection run over multiple caches ------------------------------------------------ Key: ISPN-767 URL: https://jira.jboss.org/browse/ISPN-767 Project: Infinispan Issue Type: Feature Request Reporter: Mircea Markus Assignee: Manik Surtani Fix For: 5.2.0.Final right now deadlock detection runs on a per cache basis. Eg. following deadlock won't be detected: - N1,N2 two nodes, A and B are cache running on each of them. tx1 running on N1: N1.A.put(k1); N1.B.put(k2) tx2 running in N2: N2.B.put(k2); N2.A.put(k1) -- 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

11 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (ISPN-1419) Clean up ConfigurationOverrides to match what 5.1 supports

by Marius Bogoevici (JIRA)

Clean up ConfigurationOverrides to match what 5.1 supports ---------------------------------------------------------- Key: ISPN-1419 URL: https://issues.jboss.org/browse/ISPN-1419 Project: Infinispan Issue Type: Bug Components: Spring integration Affects Versions: 5.1.0.ALPHA2 Reporter: Marius Bogoevici Assignee: Marius Bogoevici Fix For: 5.1.0.BETA1 Currently, ConfigurationOverrides is accessing Configuration directly through a series of deprecated methods. Make this fully compatible with Infinispan 5.1 and use FluentConfiguration instead. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

4
13
0 / 0

[JBoss JIRA] Created: (ISPN-1068) Add usage support similar to the one included in Spring Data

by Marius Bogoevici (JIRA)

Add usage support similar to the one included in Spring Data ------------------------------------------------------------ Key: ISPN-1068 URL: https://issues.jboss.org/browse/ISPN-1068 Project: Infinispan Issue Type: Feature Request Reporter: Marius Bogoevici Assignee: Manik Surtani ... i.e. InfinispanTemplate/InfinispanCallback -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

5
20
0 / 0

[JBoss JIRA] Created: (ISPN-1353) Cluster wide atomic integer(should be unique and incremental between cache restarts) and atomic id(uuid+unique cache node id) generation

by Magnus Magnus (JIRA)

Cluster wide atomic integer(should be unique and incremental between cache restarts) and atomic id(uuid+unique cache node id) generation ---------------------------------------------------------------------------------------------------------------------------------------- Key: ISPN-1353 URL: https://issues.jboss.org/browse/ISPN-1353 Project: Infinispan Issue Type: Feature Request Reporter: Magnus Magnus Assignee: Manik Surtani Fix For: 5.1.0.FINAL, 5.2.0.FINAL Cluster wide atomic integer and atomic id(uuid+unique cache node id) generation should be supported. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

5
7
0 / 0

[JBoss JIRA] Created: (ISPN-924) Support Atomic arithmetic operations in the API

by Erik Salter (JIRA)

Support Atomic arithmetic operations in the API ----------------------------------------------- Key: ISPN-924 URL: https://issues.jboss.org/browse/ISPN-924 Project: Infinispan Issue Type: Feature Request Reporter: Erik Salter Assignee: Manik Surtani It would be useful if Infinispan supported cluster-wide atomic operations for java.lang.Number types in the API -- similar to the AtomicX API in Java. Right now, to cobble this functionality, we'd need to do something like: - Start a tx - Single-lock a key - Get and increment - Commit - And, of course, handle the cache exceptions =) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

4
5
0 / 0

[JBoss JIRA] Created: (ISPN-1342) Support for Near-Cache Pattern

by Peter Novak (JIRA)

Support for Near-Cache Pattern ------------------------------ Key: ISPN-1342 URL: https://issues.jboss.org/browse/ISPN-1342 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Affects Versions: 5.0.0.FINAL Reporter: Peter Novak Assignee: Manik Surtani Please create some support for near-cache pattern for distributed cache. Some detailed description could be found in Oracle Coherence documentation http://download.oracle.com/docs/cd/E13924_01/coh.340/e13819/nearcache.htm or in Cameron Purdy presentation http://frech.info/themen/CameronPurdy-DistributedCachingEssentialLessons.pdf It is based on combination of L1 caching in local JVM of application with combination of L2 cache based on distributed cache cluster on other servers. I tried to implement this myself, but HotRod does not support Client-side listeners (The UnsupportedOperationException is thrown). It could be cool, if I could register some kind of eviction listener on client side and use it for invalidation of records in local cache based on event from remote distributed cache (L2). Some kind of workaround was described in http://community.jboss.org/thread/166993 : "We don't have L1s yet, but you could implement Cache Listeners on the server side and use JMS to notify your clients and build an L1 that way." Thanks for so great cache like infinispan is. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

3
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues September 2011