November 2011 - infinispan-issues

[JBoss JIRA] Created: (ISPN-1117) Make use of JGroups Exclusion Lists where possible

by Manik Surtani (JIRA)

Make use of JGroups Exclusion Lists where possible -------------------------------------------------- Key: ISPN-1117 URL: https://issues.jboss.org/browse/ISPN-1117 Project: Infinispan Issue Type: Feature Request Components: RPC Affects Versions: 5.0.0.FINAL Reporter: Manik Surtani Assignee: Vladimir Blagojevic Fix For: 5.1.0.BETA1, 5.1.0.Final See JGRP-1192 - this can be used to minimise the messages on the wire. Should only be used if UDP multicast is available though. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (ISPN-201) make JDBC cache store use DB transactions for commit/rollback

by Mircea Markus (JIRA)

make JDBC cache store use DB transactions for commit/rollback ------------------------------------------------------------- Key: ISPN-201 URL: https://jira.jboss.org/jira/browse/ISPN-201 Project: Infinispan Issue Type: Feature Request Components: Loaders and Stores Reporter: Mircea Markus Assignee: Manik Surtani Fix For: 4.0.0.GA current impl of JDBC cache store does not use DB transaction (nor local transactions/Connection.setAutocommit(false)) for storing the modifications created within a transaction. This might leave the store in an inconsistent state one operation fails during commit. This should be changed to either 1. use local transactions or 2. register the driver as an XAResource and rely on the TM to manage the boundaries. I would go for 1, as it would be more consistent with other CStore implementation (different cache store interceptor should be used for managing the 2'nd approach). -- 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

11 years, 5 months

3
7
0 / 0

[JBoss JIRA] Created: (ISPN-1296) Add typed (fluent) version of JGroups configuration

by Pete Muir (JIRA)

Add typed (fluent) version of JGroups configuration --------------------------------------------------- Key: ISPN-1296 URL: https://issues.jboss.org/browse/ISPN-1296 Project: Infinispan Issue Type: Feature Request Affects Versions: 5.0.0.CR8 Reporter: Pete Muir Assignee: Manik Surtani Fix For: 5.1.0.ALPHA1 Probably should add this to JGroups itself -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

6
11
0 / 0

[JBoss JIRA] Created: (ISPN-1396) Make all ExecutorServices configurable via global configuration

by Galder Zamarreño (JIRA)

Make all ExecutorServices configurable via global configuration --------------------------------------------------------------- Key: ISPN-1396 URL: https://issues.jboss.org/browse/ISPN-1396 Project: Infinispan Issue Type: Enhancement Components: Configuration Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.1.0.BETA2 Several executor services are not configurable out of the box, which could complicate AS7 management. For example: - RehashExecutor (BaseStateTransferManagerImpl, see ISPN-1194) - LockBreakingService (in TransactionTable) - CoalescedAsyncStore (in AsyncStore) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

7
14
0 / 0

[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] (ISPN-1523) Remote nodes send duplicate invalidation messages

by Dan Berindei (Created) (JIRA)

Remote nodes send duplicate invalidation messages ------------------------------------------------- Key: ISPN-1523 URL: https://issues.jboss.org/browse/ISPN-1523 Project: Infinispan Issue Type: Bug Components: Distributed Cache Reporter: Dan Berindei Assignee: Manik Surtani I though only the originator should send invalidation messages, but I'm seeing these messages in the log: {noformat} 2011-11-11 11:10:27,608 TRACE (OOB-2,Infinispan-Cluster,NodeD-8993) [org.infinispan.interceptors.DistributionInterceptor] Put occuring on node, requesting cache invalidation for keys [k1]. Origin of command is remote 2011-11-11 11:10:27,608 TRACE (OOB-3,Infinispan-Cluster,NodeA-31187) [org.infinispan.interceptors.DistributionInterceptor] Put occuring on node, requesting cache invalidation for keys [k1]. Origin of command is remote 2011-11-11 11:10:27,608 TRACE (OOB-2,Infinispan-Cluster,NodeD-8993) [org.infinispan.distribution.L1ManagerImpl] Invalidating L1 caches for keys [k1] 2011-11-11 11:10:27,608 TRACE (OOB-3,Infinispan-Cluster,NodeA-31187) [org.infinispan.distribution.L1ManagerImpl] Invalidating L1 caches for keys [k1] {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

8
12
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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2011