[JBoss JIRA] (ISPN-1909) FileCacheStore does not work correctly with NFS
by Martin Gencur (JIRA)
Martin Gencur created ISPN-1909:
-----------------------------------
Summary: FileCacheStore does not work correctly with NFS
Key: ISPN-1909
URL: https://issues.jboss.org/browse/ISPN-1909
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Reporter: Martin Gencur
Assignee: Manik Surtani
I'm getting the following exception when running Infinispan testsuite on Solaris with NFS (Network File System):
{code}
java.lang.IllegalArgumentException: bucketId: .nfs073116 (expected: integer)
at org.infinispan.loaders.bucket.Bucket.setBucketId(Bucket.java:77)
at org.infinispan.loaders.file.FileCacheStore.loadBucket(FileCacheStore.java:323)
at org.infinispan.loaders.file.FileCacheStore.loopOverBuckets(FileCacheStore.java:101)
at org.infinispan.loaders.bucket.BucketBasedCacheStore.loadAllLockSafe(BucketBasedCacheStore.java:180)
at org.infinispan.loaders.LockSupportCacheStore.loadAll(LockSupportCacheStore.java:138)
at org.infinispan.loaders.BaseCacheStoreTest.testStreamingAPI(BaseCacheStoreTest.java:561)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:644)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:546)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:700)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1002)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:137)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:121)
at org.testng.TestRunner.runWorkers(TestRunner.java:909)
at org.testng.TestRunner.privateRun(TestRunner.java:618)
at org.testng.TestRunner.run(TestRunner.java:499)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:332)
at org.testng.SuiteRunner.access$000(SuiteRunner.java:33)
at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:358)
at org.testng.internal.thread.ThreadUtil$CountDownLatchedRunnable.run(ThreadUtil.java:142)
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:662)
{code}
More FileCacheStore tests fail because of this problem: https://hudson.qa.jboss.com/hudson/view/EDG6/view/EDG-QE/job/edg-60-commu...
I was not sure what this means and found this explanation on the internet:
The .nfsxxxx files are used by NFS clients to manage
the deletion of open files. If an open file is deleted
then the client renames it to .nfsxxxx. If the last
open to this file is closed then the client should
send a request to remove it. If the client crashes
before it can clean up then you'll be left with these
files.
I think Infinispan should count with using NFS ans ignore the files with .nsf prefix when loading all buckets into memory.
--
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
12 years, 10 months
[JBoss JIRA] (ISPN-1834) Improve the way custom objects are injected into ExtendedModuleCommandFactory impls
by Galder Zamarreño (JIRA)
Galder Zamarreño created ISPN-1834:
--------------------------------------
Summary: Improve the way custom objects are injected into ExtendedModuleCommandFactory impls
Key: ISPN-1834
URL: https://issues.jboss.org/browse/ISPN-1834
Project: Infinispan
Issue Type: Enhancement
Reporter: Galder Zamarreño
Assignee: Manik Surtani
Fix For: 6.0.0.FINAL
Retrieving the ExtendedModuleCommandFactory associated with a cache manager is a PITA right now, you have to do:
{code}GlobalComponentRegistry globalCr = cache.getComponentRegistry().getGlobalComponentRegistry();
// TODO: This is a hack, make it easier to retrieve in Infinispan!
return (CacheCommandFactory) ((Map) globalCr.getComponent("org.infinispan.modules.command.factories"))
.values().iterator().next();
{code}
Provide a cleaner way of initialising cache command factories for custom objects that the factory can plug into the remote commands. Example: evict all in 2LC where commands need to know the cache region (a Hibernate construct) on which to operate on.
--
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
12 years, 10 months
[JBoss JIRA] (ISPN-1611) Hotrod server memory leak after enable idle timeout
by hs z (Created) (JIRA)
Hotrod server memory leak after enable idle timeout
---------------------------------------------------
Key: ISPN-1611
URL: https://issues.jboss.org/browse/ISPN-1611
Project: Infinispan
Issue Type: Bug
Components: Cache Server
Affects Versions: 5.1.0.CR1
Reporter: hs z
Assignee: Manik Surtani
i set --idle_timeout=15 as param, threads count and memory usage always grow, i got a heap dump and found many netty HashedWheelTimer instances cost much memory.
in HashedWheelTimer javadoc, it says: "Do not create many instances. HashedWheelTimer creates a new thread whenever it is instantiated and started. Therefore, you should make sure to create only one instance and share it across your application. One of the common mistakes, that makes your application unresponsive, is to create a new instance in ChannelPipelineFactory, which results in the creation of a new thread for every connection.". but in infinispan NettyChannelPipelineFactory.scala, there is "timer = new HashedWheelTimer", it's misused.
--
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
12 years, 10 months
[JBoss JIRA] (ISPN-1621) SharedResourceMisuseDetector warning
by Michal Linhard (Created) (JIRA)
SharedResourceMisuseDetector warning
------------------------------------
Key: ISPN-1621
URL: https://issues.jboss.org/browse/ISPN-1621
Project: Infinispan
Issue Type: Bug
Components: Cache Server
Affects Versions: 5.1.0.CR1
Reporter: Michal Linhard
Assignee: Manik Surtani
Priority: Minor
This warning message can be seen when starting EDG
{code}
node1:
09:07:45,110 WARNING [org.jboss.netty.util.internal.SharedResourceMisuseDetector] (MemcachedServerMaster-2 ([id: 0x4d815146, /10.16.90.106:11222])) You are creating too many HashedWheelTimer instances. HashedWheelTimer is a shared resource that must be reused across the application, so that only a few instances are created.
node2:
09:07:45,381 WARNING [org.jboss.netty.util.internal.SharedResourceMisuseDetector] (HotRodServerMaster-2 ([id: 0x35612600, /10.16.90.107:11222])) You are creating too many HashedWheelTimer instances. HashedWheelTimer is a shared resource that must be reused across the application, so that only a few instances are created.
node3:
09:07:45,526 WARNING [org.jboss.netty.util.internal.SharedResourceMisuseDetector] (HotRodServerMaster-2 ([id: 0x4263f6ea, /10.16.90.108:11222])) You are creating too many HashedWheelTimer instances. HashedWheelTimer is a shared resource that must be reused across the application, so that only a few instances are created.
node4:
09:07:48,125 WARNING [org.jboss.netty.util.internal.SharedResourceMisuseDetector] (HotRodServerMaster-2 ([id: 0x7d05e560, /10.16.90.109:11222])) You are creating too many HashedWheelTimer instances. HashedWheelTimer is a shared resource that must be reused across the application, so that only a few instances are created.
{code}
EDG build: http://hudson.qa.jboss.com/hudson/view/EDG6/view/EDG-QE/job/edg-60-build-...
huson job with the issue: http://hudson.qa.jboss.com/hudson/view/EDG6/view/EDG-REPORTS-PERF/job/edg...
--
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
12 years, 10 months