June 2010 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-368) Remove code duplication in certain JDBC configuration classes

by Manik Surtani (JIRA)

Remove code duplication in certain JDBC configuration classes ------------------------------------------------------------- Key: ISPN-368 URL: https://jira.jboss.org/jira/browse/ISPN-368 Project: Infinispan Issue Type: Task Components: Loaders and Stores Affects Versions: 4.0.0.Final Reporter: Manik Surtani Assignee: Mircea Markus Priority: Minor Fix For: 4.1.0.CR1, 4.1.0.Final JdbcStringBasedCacheStoreConfig, JdbcBinaryCacheStoreConfig and JdbcMixedCacheStoreConfig duplicate a lot of code, including javadocs. Could these not inherit from an abstract superclass? -- 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, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (ISPN-481) Add Reader versions of InfinispanConfiguration factory methods

by Paul Ferraro (JIRA)

Add Reader versions of InfinispanConfiguration factory methods -------------------------------------------------------------- Key: ISPN-481 URL: https://jira.jboss.org/browse/ISPN-481 Project: Infinispan Issue Type: Feature Request Components: Configuration Affects Versions: 4.1.0.BETA2 Reporter: Paul Ferraro Assignee: Manik Surtani Priority: Minor 'Tis a bit awkward/inefficient to parse an Infinispan configuration from a string. Currently, I would have to do something like: InfinispanConfiguration.newInfinispanConfiguration(new ByteArrayInputStream(config.getBytes())); Since we're expecting character data anyway, it would be nice to add reader versions of the factory methods to the api, e.g. InfinispanConfiguration.newInfinispanConfiguration(Reader reader) That way, I can do: InfinispanConfiguration.newInfinispanConfiguration(new StringReader(config)); The InputStream factory methods can then delegate to the Reader factory methods via InputStreamReader. -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (ISPN-520) Null keys should be checked very early on (in the CacheDelegate) and a meaningful exception thrown.

by Manik Surtani (JIRA)

Null keys should be checked very early on (in the CacheDelegate) and a meaningful exception thrown. --------------------------------------------------------------------------------------------------- Key: ISPN-520 URL: https://jira.jboss.org/browse/ISPN-520 Project: Infinispan Issue Type: Bug Components: Core API Affects Versions: 4.1.0.BETA2 Reporter: Manik Surtani Assignee: Manik Surtani Priority: Critical Fix For: 4.1.0.CR1, 4.1.0.Final See subject. -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (ISPN-473) Hot Rod client max concurrent connections is too small

by Galder Zamarreno (JIRA)

Hot Rod client max concurrent connections is too small ------------------------------------------------------ Key: ISPN-473 URL: https://jira.jboss.org/browse/ISPN-473 Project: Infinispan Issue Type: Bug Components: Cache Server Affects Versions: 4.1.0.BETA2 Reporter: Galder Zamarreno Assignee: Mircea Markus Fix For: 4.1.0.CR1 A default value of 2 for maximum concurrent connections in Hot Rod client is far too small (maxAlive property). It should be much bigger. Same for maxIdle -- 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, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (ISPN-519) Update to Scala 2.8.0.RC7

by Galder Zamarreno (JIRA)

Update to Scala 2.8.0.RC7 ------------------------- Key: ISPN-519 URL: https://jira.jboss.org/browse/ISPN-519 Project: Infinispan Issue Type: Thirdparty Change Components: Cache Server Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.1.0.CR1 There has been several Scala releases since RC3. Currently, this is 2.8.0.RC7. Upgrate Infinispan to this version or higher. -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (ISPN-488) add a retry to hotrod operations

by Mircea Markus (JIRA)

add a retry to hotrod operations --------------------------------- Key: ISPN-488 URL: https://jira.jboss.org/browse/ISPN-488 Project: Infinispan Issue Type: Feature Request Components: Cache Server Affects Versions: 4.1.0.BETA2, 4.1.0.BETA1 Reporter: Mircea Markus Assignee: Manik Surtani Fix For: 4.1.0.CR1 >From an email from Galder: Hi Mircea, I'm playing around with Hot Rod client/server for JUDCon demo and I've found this. The demo consists of: 1. Start a server 2. Connect with client and do a put 3. Make several get calls on that server 4. Start a new node, clustered with replication and state transfer on. 5. Make several calls, the calls are being load balanced in round robin fashion. 6. Shutdown the first node and make a get call. This throws: Exception in thread "main" HotRodServerException{messageId=0, errorStatusCode=0} org.infinispan.client.hotrod.exceptions.TransportException: java.io.IOException: Broken pipe at org.infinispan.client.hotrod.impl.transport.VHelper.writeVLong(VHelper.java:48) at org.infinispan.client.hotrod.impl.transport.tcp.TcpTransport.writeVLong(TcpTransport.java:57) at org.infinispan.client.hotrod.impl.protocol.HotRodOperationsHelper.writeHeader(HotRodOperationsHelper.java:30) at org.infinispan.client.hotrod.impl.protocol.HotRodOperationsImpl.sendKeyOperation(HotRodOperationsImpl.java:256) at org.infinispan.client.hotrod.impl.protocol.HotRodOperationsImpl.get(HotRodOperationsImpl.java:39) at org.infinispan.client.hotrod.impl.RemoteCacheImpl.get(RemoteCacheImpl.java:276) at replication.GetOnReadLoop$.main(GetOnReadLoop.scala:19) at replication.GetOnReadLoop.main(GetOnReadLoop.scala) Caused by: java.io.IOException: Broken pipe at sun.nio.ch.FileDispatcher.write0(Native Method) at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:29) at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:104) at sun.nio.ch.IOUtil.write(IOUtil.java:75) at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:334) at java.nio.channels.Channels.write(Channels.java:60) at java.nio.channels.Channels.access$000(Channels.java:47) at java.nio.channels.Channels$1.write(Channels.java:134) at java.io.OutputStream.write(OutputStream.java:58) at java.nio.channels.Channels$1.write(Channels.java:115) at org.infinispan.io.UnsignedNumeric.writeUnsignedLong(UnsignedNumeric.java:134) at org.infinispan.client.hotrod.impl.transport.VHelper.writeVLong(VHelper.java:46) ... 7 more Shouldn't have this been swallowed by the client and shouldn't have it tried on the other node? This happens if a server shuts down. After a failure the connection is cleaned. A workaround for this should be "testOnBorrow" which would first test the connection when fetching it from the 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

13 years, 10 months

3
4
0 / 0

[JBoss JIRA] Updated: (ISPN-39) Distributed executors

by Manik Surtani (JIRA)

[ https://jira.jboss.org/browse/ISPN-39?page=com.atlassian.jira.plugin.syst... ] Manik Surtani updated ISPN-39: ------------------------------ Assignee: (was: Manik Surtani) > Distributed executors > --------------------- > > Key: ISPN-39 > URL: https://jira.jboss.org/browse/ISPN-39 > Project: Infinispan > Issue Type: Feature Request > Components: RPC > Reporter: Manik Surtani > Fix For: 5.0.0.BETA1, 5.0.0.Final > > > A new API to allow users to provide a Runnable/Callable and a set of keys to run this on, and the ability to move the code to where the data is and execute it there, returning results (if any) across a network. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (ISPN-485) Migration Tools - Coherence migration pointing to wrong .xslt file

by Gisella Saavedra (JIRA)

Migration Tools - Coherence migration pointing to wrong .xslt file ------------------------------------------------------------------ Key: ISPN-485 URL: https://jira.jboss.org/browse/ISPN-485 Project: Infinispan Issue Type: Bug Components: Migration tools Affects Versions: 4.1.0.BETA2, 4.1.0.BETA1 Reporter: Gisella Saavedra Assignee: Manik Surtani Priority: Critical 1. the class org.infinispan.config.parsing.ConfigFilesConvertor has the incorrect xslt file for method transformFromCoherence35x(). It is using the ehcache .xslt transformer file instead of the coherence one. 2. Also, it would be very helpful if the coherence cache-config.dtd is placed in a resources or bin directory. Otherwise, instructions should be given as to where to put these files conveniently. -- 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, 10 months

2
8
0 / 0

[JBoss JIRA] Created: (ISPN-495) Incorrect directory structure in cachestore/remote

by Galder Zamarreno (JIRA)

Incorrect directory structure in cachestore/remote -------------------------------------------------- Key: ISPN-495 URL: https://jira.jboss.org/browse/ISPN-495 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 4.1.0.BETA2 Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.1.0.CR1 >From Trustin: The test classes in cachestore-remote are stored in the wrong directory: src/test/java/org.infinispan.loaders.remote where it should be in: src/test/java/org/infinispan/loaders/remote What's funny is what Eclipse says about this problem: The declared package "org.infinispan.loaders.remote" does not match the expected package "org.infinispan.loaders.remote" Hence, it took be quite a while to figure out why. :) -- 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, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (ISPN-123) Build demo and blog about using Infinispan on EC2

by Manik Surtani (JIRA)

Build demo and blog about using Infinispan on EC2 ------------------------------------------------- Key: ISPN-123 URL: https://jira.jboss.org/jira/browse/ISPN-123 Project: Infinispan Issue Type: Feature Request Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 4.0.0.BETA1, 4.0.0.GA This will require the use of FILE_PING in JGroups 2.8 as a discovery mechanism. Critical to show the world that Infinispan + JGroups *can* do auto-discovery on EC2. Potentially also use S3 as a cache store for this demo. -- 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, 10 months

3
12
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2010