May 2010 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-447) Asking for a cache that doesn't exists in other nodes freezes Infinispan

by Oswaldo Cavalcanti Dantas Junior (JIRA)

Asking for a cache that doesn't exists in other nodes freezes Infinispan ------------------------------------------------------------------------ Key: ISPN-447 URL: https://jira.jboss.org/browse/ISPN-447 Project: Infinispan Issue Type: Bug Components: Distributed Cache Affects Versions: 4.1.0.BETA1 Reporter: Oswaldo Cavalcanti Dantas Junior Assignee: Manik Surtani Attachments: infinispan-test.zip I'm evaluating some of the clustering possibilities with Infinispan and I might have found a bug introduced somewhere in 4.1.x (no problems occur when repeating the same procedures with 4.0.0.Final). I'll attach a simple maven test case where I isolated the freezing conditions. Basically, after starting a test in debug mode twice with a breakpoint after trying to get a cache that doesn't exist on the first VM, the second freezes with the following stack (more details on the attached InfinispanTest class): Thread [main] (Suspended) Unsafe.park(boolean, long) line: not available [native method] LockSupport.park(Object) line: 158 FutureTask$Sync(AbstractQueuedSynchronizer).parkAndCheckInterrupt() line: 747 FutureTask$Sync(AbstractQueuedSynchronizer).doAcquireSharedInterruptibly(int) line: 905 FutureTask$Sync(AbstractQueuedSynchronizer).acquireSharedInterruptibly(int) line: 1217 FutureTask$Sync.innerGet() line: 218 FutureTask<V>.get() line: 83 DistributionManagerImpl.waitForJoinToComplete() line: 144 NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] NativeMethodAccessorImpl.invoke(Object, Object[]) line: 39 DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 25 Method.invoke(Object, Object...) line: 597 ReflectionUtil.invokeAccessibly(Object, Method, Object[]) line: 170 AbstractComponentRegistry$PrioritizedMethod.invoke() line: 852 ComponentRegistry(AbstractComponentRegistry).internalStart() line: 672 ComponentRegistry(AbstractComponentRegistry).start() line: 574 ComponentRegistry.start() line: 148 CacheDelegate<K,V>.start() line: 291 DefaultCacheManager.createCache(String) line: 446 DefaultCacheManager.getCache(String) line: 409 InfinispanTest.test() line: 61 NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] NativeMethodAccessorImpl.invoke(Object, Object[]) line: 39 DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 25 Method.invoke(Object, Object...) line: 597 FrameworkMethod$1.runReflectiveCall() line: 44 FrameworkMethod$1(ReflectiveCallable).run() line: 15 FrameworkMethod.invokeExplosively(Object, Object...) line: 41 InvokeMethod.evaluate() line: 20 BlockJUnit4ClassRunner.runChild(FrameworkMethod, RunNotifier) line: 76 BlockJUnit4ClassRunner.runChild(Object, RunNotifier) line: 50 ParentRunner$3.run() line: 193 ParentRunner$1.schedule(Runnable) line: 52 BlockJUnit4ClassRunner(ParentRunner<T>).runChildren(RunNotifier) line: 191 ParentRunner<T>.access$000(ParentRunner, RunNotifier) line: 42 ParentRunner$2.evaluate() line: 184 RunBefores.evaluate() line: 28 BlockJUnit4ClassRunner(ParentRunner<T>).run(RunNotifier) line: 236 JUnit4TestClassReference(JUnit4TestReference).run(TestExecution) line: 46 TestExecution.run(ITestReference[]) line: 38 RemoteTestRunner.runTests(String[], String, TestExecution) line: 467 RemoteTestRunner.runTests(TestExecution) line: 683 RemoteTestRunner.run() line: 390 RemoteTestRunner.main(String[]) line: 197 Probably there is a simpler, more elegant way to test this condition (one that could be used in a official test case) but this was the fastest way for me to reproduce the bug without going too deep in the Infinispan internals. -- 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, 11 months

3
15
0 / 0

[JBoss JIRA] Created: (ISPN-432) Add test to verify that a Hot Rod request to an undefined cache fails

by Galder Zamarreno (JIRA)

Add test to verify that a Hot Rod request to an undefined cache fails --------------------------------------------------------------------- Key: ISPN-432 URL: https://jira.jboss.org/jira/browse/ISPN-432 Project: Infinispan Issue Type: Task Reporter: Galder Zamarreno Assignee: Galder Zamarreno Priority: Minor Fix For: 4.1.0.CR1 Add test to verify that a Hot Rod request to an undefined cache fails -- 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, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (ISPN-461) Disable idle timeout by default in Hot Rod and Memcached servers

by Galder Zamarreno (JIRA)

Disable idle timeout by default in Hot Rod and Memcached servers ---------------------------------------------------------------- Key: ISPN-461 URL: https://jira.jboss.org/browse/ISPN-461 Project: Infinispan Issue Type: Task Components: Cache Server Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.1.0.CR1 Disable idle timeout by default in Hot Rod and Memcached servers -- 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, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (ISPN-468) Wrap any log calls in Memcached/HotRod servers around if enabled calls

by Galder Zamarreno (JIRA)

Wrap any log calls in Memcached/HotRod servers around if enabled calls ---------------------------------------------------------------------- Key: ISPN-468 URL: https://jira.jboss.org/browse/ISPN-468 Project: Infinispan Issue Type: Task Components: Cache Server Affects Versions: 4.1.0.BETA1 Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.1.0.CR1 While profiling Hot Rod, I keep seeing time being spend in these: 2.3% - 25,569 ms - 140,862 inv. scala.LowPriorityImplicits.genericWrapArray (line\: 56) ... 2.2% - 24,713 ms - 140,862 inv. scala.LowPriorityImplicits.genericWrapArray (line\: 231) These appear to come from trying to create arrays when for log messages, i.e.: trace("Decoded header {0}", header) trace method definition: def trace(msg: => String, params: Any*) = if (log.isTraceEnabled) log.trace(msg, params.map(_.asInstanceOf[AnyRef]) : _*) So, change all trace calls to be protected by "if (log.isTraceEnabled)" to avoid wasteful creation of arrays. -- 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, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (ISPN-414) UNORDERED eviciton does not work

by Vladimir Blagojevic (JIRA)

UNORDERED eviciton does not work -------------------------------- Key: ISPN-414 URL: https://jira.jboss.org/jira/browse/ISPN-414 Project: Infinispan Issue Type: Bug Affects Versions: 4.1.0.ALPHA3, 4.1.0.ALPHA2 Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Fix For: 4.1.0.BETA1 EvictionStrategy.UNORDERED does not properly setup eviction mechanism and is treated like EvictionStrategy.NONE (see DataContainerFactory.java). Options: a) treat it as LRU b) implement unordered element selection for eviction c) deprecate UNORDERED -- 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, 11 months

3
6
0 / 0

[JBoss JIRA] Created: (ISPN-453) GUI demo build fails due to unable to locate log4j

by Galder Zamarreno (JIRA)

GUI demo build fails due to unable to locate log4j -------------------------------------------------- Key: ISPN-453 URL: https://jira.jboss.org/browse/ISPN-453 Project: Infinispan Issue Type: Bug Affects Versions: 4.1.0.BETA1 Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.1.0.CR1 If you wipe your maven2 repo, you'll find that GUI demo does not build and this is related to the maven repo changes. Basically, the GUI demo depends on log4j 1.2.15 but we're not using the default one. Instead we're depending on http://repository.jboss.org/maven2/apache-log4j/log4j/1.2.15/ Now, the reason for that I suspect is the fact that if you depend on the standard log4j 1.2.15, you get dependency failures like this: Missing: ---------- 1) com.sun.jdmk:jmxtools:jar:1.2.1 Try downloading the file manually from: http://java.sun.com/products/JavaManagement/download.html Then, install it using the command: mvn install:install-file -DgroupId=com.sun.jdmk -DartifactId=jmxtools -Dversion=1.2.1 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.sun.jdmk -DartifactId=jmxtools -Dversion=1.2.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.infinispan:infinispan-gui-demo:jar:4.1.0-SNAPSHOT 2) log4j:log4j:jar:1.2.15 3) com.sun.jdmk:jmxtools:jar:1.2.1 2) com.sun.jmx:jmxri:jar:1.2.1 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=com.sun.jmx -DartifactId=jmxri -Dversion=1.2.1 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.sun.jmx -DartifactId=jmxri -Dversion=1.2.1 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.infinispan:infinispan-gui-demo:jar:4.1.0-SNAPSHOT 2) log4j:log4j:jar:1.2.15 3) com.sun.jmx:jmxri:jar:1.2.1 ---------- 2 required artifacts are missing. for artifact: org.infinispan:infinispan-gui-demo:jar:4.1.0-SNAPSHOT ---------- As http://unitstep.net/blog/2009/05/18/resolving-log4j-1215-dependency-probl... explains, these appear to be optional dependencies that log4j should have set. Issues like this might explain why we ended up building and putting our own 1.2.15 version in the old repository. The point is, what do we do about it? Any particular reason why the demo depends on version 1.2.15? -- 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, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (ISPN-437) Hotrod server optimisation: use SKIP_REMOTE_LOOKUP if no return values are needed

by Mircea Markus (JIRA)

Hotrod server optimisation: use SKIP_REMOTE_LOOKUP if no return values are needed --------------------------------------------------------------------------------- Key: ISPN-437 URL: https://jira.jboss.org/jira/browse/ISPN-437 Project: Infinispan Issue Type: Feature Request Components: Cache Server Reporter: Mircea Markus Assignee: Manik Surtani Fix For: 4.1.0.CR1 it would be a good optimisation for the HR server to use SKIP_REMOTE_LOOKUP flag on put/remove/replace if I don't pass an force return value to HR server -- 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, 11 months

2
5
0 / 0

[JBoss JIRA] Created: (ISPN-443) Errors/typos in startServer.sh

by John Ament (JIRA)

Errors/typos in startServer.sh ------------------------------ Key: ISPN-443 URL: https://jira.jboss.org/browse/ISPN-443 Project: Infinispan Issue Type: Bug Components: Cache Server Affects Versions: 4.1.0.BETA1 Environment: Infinispan 4.1 Beta 1 on opensuse Reporter: John Ament Assignee: Manik Surtani There are a couple of errors in the startServer.sh script. For -i, --idle_timeout=<num> Idle read timeout, in seconds, used to detect stale connections (default: 60 seconds). If no new messages have been read within this time, the server disconnects the channel. Passing 0 disables idle timeout. if I pass -i 0 ./startServer.sh -r hotrod -p 11311 -i 0 May 16, 2010 9:17:50 AM org.infinispan.util.logging.AbstractLogImpl info INFO: Start main with args: -r, hotrod, -p, 11311, -i, 0 startServer: invalid option -- i There is a typo for -r -r, --protocol= Protocol to understand by the server. This is a mandatory option and you should choose one of the two options [memcached|hotrod|websocket] There are 3 protocols listed, not two options. -- 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, 11 months

4
7
0 / 0

[JBoss JIRA] Created: (ISPN-440) RemoteCache failure if RemoteCacheManager not started

by Mircea Markus (JIRA)

RemoteCache failure if RemoteCacheManager not started ------------------------------------------------------ Key: ISPN-440 URL: https://jira.jboss.org/jira/browse/ISPN-440 Project: Infinispan Issue Type: Bug Components: RPC Affects Versions: 4.1.0.BETA1 Reporter: Mircea Markus Assignee: Mircea Markus If the RemoteCacheManager is not started then an misleading exception is being thrown back to the user whenever trying to invoke a method on the remote cache: "org.infinispan.client.hotrod.exceptions.HotRodClientException: Could not instantiate class: null". This should be replaced with a proper exception being replaced, stating to the user that RemoteCacheManager needs to be started before using the cache. -- 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, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (ISPN-409) CloudCacheStore GZipInputStream generates EOFException

by Phil vd (JIRA)

CloudCacheStore GZipInputStream generates EOFException ------------------------------------------------------ Key: ISPN-409 URL: https://jira.jboss.org/jira/browse/ISPN-409 Project: Infinispan Issue Type: Bug Reporter: Phil vd Assignee: Manik Surtani JDK's GZipInpuStream contains an unfixed bug and sometimes raise an EOFException (the fix is to ignore this exception). Switched to Commons BZip2InputStream instead. -- 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, 11 months

3
13
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2010