June 2010 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-487) Log byte arrays partially in Hot Rod client

by Galder Zamarreno (JIRA)

Log byte arrays partially in Hot Rod client ------------------------------------------- Key: ISPN-487 URL: https://jira.jboss.org/browse/ISPN-487 Project: Infinispan Issue Type: Task Components: Cache Server Reporter: Galder Zamarreno Assignee: Mircea Markus Fix For: 4.1.0.CR1 In SerializationMarshaller I see this: if (log.isTraceEnabled()) { log.trace("Unmarshalled bytes: " + Arrays.toString(bytes) + " and returning object: " + o); } Using Arrays.toString() is Ok for most cases but if the serialized version is too big, it'd be hard to read trace logs. Instead, you should prob use a similar method to the one used by the HotRod/Memcached or when lazy deserialization is used where I call o.i.u.Util.printArray. This methods prints the byte array partially, only the first 10 bytes I believe, and if -Dinfinispan.arrays.debug=true is passed, it then prints the full array. -- 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, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (ISPN-478) Create a high level server modules wiki

by Galder Zamarreno (JIRA)

Create a high level server modules wiki --------------------------------------- Key: ISPN-478 URL: https://jira.jboss.org/browse/ISPN-478 Project: Infinispan Issue Type: Task Components: Cache Server Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.1.0.CR1 Create a high level server modules wiki inspired by http://community.jboss.org/message/543042#543042 and other pieces of information. -- 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
2
0 / 0

[JBoss JIRA] Created: (ISPN-511) The Expiration Algorithms have an unexpected way to manage the parameter maxEntries

by Nicolas Filotto (JIRA)

The Expiration Algorithms have an unexpected way to manage the parameter maxEntries ----------------------------------------------------------------------------------- Key: ISPN-511 URL: https://jira.jboss.org/browse/ISPN-511 Project: Infinispan Issue Type: Bug Components: Eviction Affects Versions: 4.1.0.BETA2, 4.0.0.Final Reporter: Nicolas Filotto Assignee: Manik Surtani The cache size should not exceed the value of the parameter maxEntries however in practice it does. See more details at http://community.jboss.org/message/549731. The Test Case has been added. -- 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

4
6
0 / 0

[JBoss JIRA] Created: (ISPN-513) hotrod client:optimize serialization of key/values

by Mircea Markus (JIRA)

hotrod client:optimize serialization of key/values -------------------------------------------------- Key: ISPN-513 URL: https://jira.jboss.org/browse/ISPN-513 Project: Infinispan Issue Type: Feature Request Components: Cache Server Affects Versions: 4.1.0.BETA2 Reporter: Mircea Markus Assignee: Manik Surtani Fix For: 4.1.0.CR1 At the moment the keys and values are being serialized into an byte[] before being send over the wire. For the values, the serialization is possible when writing data over the wire, in the socket's output stream (instead of doing it before and keeping it in an byte[]). This should reduce the noise of creating too many byte[]. -- 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
3
0 / 0

[JBoss JIRA] Created: (ISPN-515) Create Infinispan core architecture docs on wiki

by Manik Surtani (JIRA)

Create Infinispan core architecture docs on wiki ------------------------------------------------ Key: ISPN-515 URL: https://jira.jboss.org/browse/ISPN-515 Project: Infinispan Issue Type: Task Components: Core API Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 4.1.0.CR1 Lots of people have asked for this, plus it helps with contributions -- 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-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

13 years, 10 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

13 years, 10 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

13 years, 10 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

13 years, 10 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

13 years, 10 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2010