Note that there are some explanatory texts on larger screens.

plurals
  1. POOut of memory with tomcat 6 on RedHat but not in debian
    primarykey
    data
    text
    <p>I am using liferay 6.0.6 with tomcat 6 and using terracotta 3.5.4. The terracotta installation in on another server and works fine.</p> <p>The debian and redhat systems are virtual machines and use the exact same virtual hardware. 1 cpu , 4gb ram, both 64bit OS.</p> <pre><code>java version "1.6.0_24" OpenJDK Runtime Environment (IcedTea6 1.11.3) (rhel-1.48.1.11.3.el6_2-x86_64) OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode) </code></pre> <p>If im using a debian system and boot the application then it everything works as expected.</p> <p>If im using the redhat system then i get an error :</p> <pre><code>java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method) at java.lang.Thread.start(Thread.java:657) at java.util.Timer.&lt;init&gt;(Timer.java:176) at com.tc.object.locks.ClientLockManagerImpl.&lt;init&gt;(ClientLockManagerImpl.java:39) at com.tc.object.StandardDSOClientBuilder.createLockManager(StandardDSOClientBuilder.java:190) at com.tc.object.DistributedObjectClient.start(DistributedObjectClient.java:639) at com.tc.object.bytecode.ManagerImpl$2.execute(ManagerImpl.java:263) at com.tc.lang.StartupHelper.startUp(StartupHelper.java:39) at com.tc.object.bytecode.ManagerImpl.startClient(ManagerImpl.java:281) at com.tc.object.bytecode.ManagerImpl.init(ManagerImpl.java:202) at com.tc.object.bytecode.ManagerImpl.init(ManagerImpl.java:190) at com.tc.object.bytecode.hook.impl.DSOContextImpl.createStandaloneContext(DSOContextImpl.java:179) at org.terracotta.express.StandaloneL1Boot.call(StandaloneL1Boot.java:190) at org.terracotta.express.ClientImpl.&lt;init&gt;(ClientImpl.java:309) at org.terracotta.express.ClientFactoryImpl.newClient(ClientFactoryImpl.java:232) at org.terracotta.express.ClientFactoryImpl.createClient(ClientFactoryImpl.java:225) at org.terracotta.express.ClientFactoryImpl.createClient(ClientFactoryImpl.java:212) at org.terracotta.express.ClientFactoryImpl.getOrCreateClient(ClientFactoryImpl.java:190) at org.terracotta.express.ClientFactory.getOrCreateClient(ClientFactory.java:28) at net.sf.ehcache.terracotta.StandaloneTerracottaClusteredInstanceFactory.&lt;init&gt;(StandaloneTerracottaClusteredInstanceFactory.java:37) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) </code></pre> <p>The weirdest part of this error is that memory is not used. I have set the Xmx at 3500m but the memory usage never climbs above 2.3gb.</p> <p>I've been searching for a possible cause and found this : <a href="https://stackoverflow.com/questions/116640/low-java-single-process-thread-limit-in-red-hat-linux">Low Java single process thread limit in Red Hat Linux</a></p> <p>So i changed my ulimit -n and ulimit -u to 80000 but still nothing changes.</p> <p>I then edited my /etc/security/limits.conf</p> <pre><code>* soft nproc 81920 * hard nproc 81920 * soft nofile 81920 * hard nofile 81920 </code></pre> <p>I also edited /etc/sysctl.conf</p> <pre><code>fs.file-max = 100000 </code></pre> <p>then i rebooted.</p> <p>I also added -Xms=2g to my setenv.sh</p> <p>I increased -Xss to -Xss5000k</p> <p>I run echo 200000 > /proc/sys/kernel/threads-max</p> <p>But the same error still comes up. Any ideas ?</p> <p>free -m at begining of booting</p> <pre><code> total used free shared buffers cached Mem: 3963 1027 2935 0 25 748 -/+ buffers/cache: 253 3709 Swap: 2047 18 2029 </code></pre> <p>free -m just before crash</p> <pre><code> total used free shared buffers cached Mem: 3963 2897 1065 0 31 823 -/+ buffers/cache: 2043 1920 Swap: 2047 18 2029 </code></pre> <p>Update : i also tried with a machine with 8gb ram and the same result appears.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload