We are using Bigmemory 4.0.3 and we are running into couple of issues.
we are not using the ehcache.xml to create the cache rather we are using the code to create the cache. We have configured the heap memory to be used 256MB and off-heap to be used to 512MB.
One of our tester started our application and we were creating the cache at the start of our application. At the startup, system had < 512MB of RAM free and the startup threw the attached exception.
1. Is this deadlock known issue already in bigmemory ?
2. Whether Bigmemory need the configured offheap memory in RAM at the time of creating the cache itself ? If so, is there any way to say create the cache now and throw the exception when there is no enough memory to store the data ?
3. if there is no enough RAM for the offheap storage, why bigmemory cant use the swap space ?