July 2010 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-524) Document and link property based attribute default values

by Galder Zamarreno (JIRA)

Document and link property based attribute default values --------------------------------------------------------- Key: ISPN-524 URL: https://jira.jboss.org/browse/ISPN-524 Project: Infinispan Issue Type: Task Components: Configuration Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.1.0.CR1 Document property based attribute default values and linked it from generated configuration documentation. -- 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, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (ISPN-502) async replication happening in the same thread

by Mircea Markus (JIRA)

async replication happening in the same thread ---------------------------------------------- Key: ISPN-502 URL: https://jira.jboss.org/browse/ISPN-502 Project: Infinispan Issue Type: Bug Affects Versions: 4.1.0.BETA1 Reporter: Mircea Markus Assignee: Manik Surtani Fix For: 4.1.0.CR1 As per the logs. -- 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, 5 months

2
7
0 / 0

[JBoss JIRA] Created: (ISPN-490) hotrod client:cache name on write on

by Mircea Markus (JIRA)

hotrod client:cache name on write on -------------------------------------- Key: ISPN-490 URL: https://jira.jboss.org/browse/ISPN-490 Project: Infinispan Issue Type: Feature Request Reporter: Mircea Markus Assignee: Manik Surtani -- 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, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (ISPN-457) investigate result of TCP connection timeout on client call

by Mircea Markus (JIRA)

investigate result of TCP connection timeout on client call ----------------------------------------------------------- Key: ISPN-457 URL: https://jira.jboss.org/browse/ISPN-457 Project: Infinispan Issue Type: Bug Affects Versions: 4.1.0.BETA1 Reporter: Mircea Markus Assignee: Manik Surtani Fix For: 4.1.0.BETA1 check that a connection that timeouts on a client call (and not while being checked within the pool) is no longer used/passed to other clients. Also suggest configuration parameters based on the configured TCP timeout. -- 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, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (ISPN-480) JDBCBinaryCacheStore generates CacheLoaderException

by Franck Garcia (JIRA)

JDBCBinaryCacheStore generates CacheLoaderException --------------------------------------------------- Key: ISPN-480 URL: https://jira.jboss.org/browse/ISPN-480 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 4.1.0.BETA2 Environment: linux ubuntu Reporter: Franck Garcia Assignee: Manik Surtani I tried to copy a Lucene FSDirectory containing 6.3 M documents over an Infinispan Directory using the Lucene Directory.copy method. I used JdbcBinaryCacheStore as my store/loader. The following exception is thrown: 2010-05-27 11:35:16,263 ERROR (org.infinispan.loaders.jdbc.DataManipulationHelper)[luceneIndex-JdbcBinaryCacheStore-0:] Failed clearing JdbcBinaryCacheStore java.sql.BatchUpdateException: No value specified for parameter 3 at com.mysql.jdbc.PreparedStatement.executeBatch(PreparedStatement.java:1404) at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeBatch(NewProxyPreparedStatement.java:1723) at org.infinispan.loaders.jdbc.binary.JdbcBinaryCacheStore.purgeInternal(JdbcBinaryCacheStore.java:325) at org.infinispan.loaders.AbstractCacheStore$2.run(AbstractCacheStore.java:86) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) (only 2 params are passed but the statement expects 3) -- 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, 5 months

2
6
0 / 0

[JBoss JIRA] Created: (ISPN-496) TimeoutException sometimes thrown when clustered Hot Rod server is stopped

by Galder Zamarreno (JIRA)

TimeoutException sometimes thrown when clustered Hot Rod server is stopped -------------------------------------------------------------------------- Key: ISPN-496 URL: https://jira.jboss.org/browse/ISPN-496 Project: Infinispan Issue Type: Bug Components: Cache Server Affects Versions: 4.1.0.BETA2 Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.1.0.CR1 When shutting down Hot Rod servers, I sometimes see exceptions like this: Exception in thread "Thread-1" java.lang.RuntimeException: Exception encountered in shutting down the server at org.infinispan.server.core.ShutdownHook.run(Main.scala:296) Caused by: java.util.concurrent.ExecutionException: org.infinispan.util.concurrent.TimeoutException: Replication timeout for ip-10-196-170-80-39595 at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222) at java.util.concurrent.FutureTask.get(FutureTask.java:83) at org.infinispan.server.core.ShutdownHook.run(Main.scala:292) Caused by: org.infinispan.util.concurrent.TimeoutException: Replication timeout for ip-10-196-170-80-39595 at org.infinispan.remoting.transport.jgroups.JGroupsTransport.invokeRemotely(JGroupsTransport.java:422) at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:100) at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:124) at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:229) at org.infinispan.remoting.rpc.RpcManagerImpl.invokeRemotely(RpcManagerImpl.java:216) at org.infinispan.remoting.rpc.RpcManagerImpl.broadcastRpcCommand(RpcManagerImpl.java:199) at org.infinispan.remoting.rpc.RpcManagerImpl.broadcastRpcCommand(RpcManagerImpl.java:192) at org.infinispan.interceptors.ReplicationInterceptor.handleCrudMethod(ReplicationInterceptor.java:114) at org.infinispan.interceptors.ReplicationInterceptor.visitReplaceCommand(ReplicationInterceptor.java:98) at org.infinispan.commands.write.ReplaceCommand.acceptVisitor(ReplaceCommand.java:58) at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:118) at org.infinispan.interceptors.LockingInterceptor.visitReplaceCommand(LockingInterceptor.java:232) at org.infinispan.commands.write.ReplaceCommand.acceptVisitor(ReplaceCommand.java:58) at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:118) at org.infinispan.interceptors.base.CommandInterceptor.handleDefault(CommandInterceptor.java:132) at org.infinispan.commands.AbstractVisitor.visitReplaceCommand(AbstractVisitor.java:65) at org.infinispan.commands.write.ReplaceCommand.acceptVisitor(ReplaceCommand.java:58) at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:118) at org.infinispan.interceptors.TxInterceptor.enlistWriteAndInvokeNext(TxInterceptor.java:183) at org.infinispan.interceptors.TxInterceptor.visitReplaceCommand(TxInterceptor.java:142) at org.infinispan.commands.write.ReplaceCommand.acceptVisitor(ReplaceCommand.java:58) at org.infinispan.interceptors.base.CommandInterceptor.invokeNextInterceptor(CommandInterceptor.java:118) at org.infinispan.interceptors.InvocationContextInterceptor.handleAll(InvocationContextInterceptor.java:58) at org.infinispan.interceptors.InvocationContextInterceptor.handleDefault(InvocationContextInterceptor.java:39) at org.infinispan.commands.AbstractVisitor.visitReplaceCommand(AbstractVisitor.java:65) at org.infinispan.commands.write.ReplaceCommand.acceptVisitor(ReplaceCommand.java:58) at org.infinispan.interceptors.InterceptorChain.invoke(InterceptorChain.java:271) at org.infinispan.CacheDelegate.replace(CacheDelegate.java:438) at org.infinispan.CacheSupport.replace(CacheSupport.java:96) at org.infinispan.server.hotrod.HotRodServer.removeSelfFromTopologyView(HotRodServer.scala:116) at org.infinispan.server.hotrod.HotRodServer.stop(HotRodServer.scala:103) at org.infinispan.server.core.ShutdownHook$$anon$4.call(Main.scala:286) at org.infinispan.server.core.ShutdownHook$$anon$4.call(Main.scala:284) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Try to find out what's causing it. One alternative might be to log them silently cos if the view cannot be updated when the server is stopped, the crashed member detector will discover in next view that the server has crashed and will remove it then. -- 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, 5 months

1
2
0 / 0

[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

14 years, 5 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

14 years, 5 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

14 years, 5 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

14 years, 5 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2010