So I have a server that has 3.5GB ram allocated to java and there was been random crashes. There is nothing in the server log that gives any java error the only thing I can find is this: using centos /var/log/messages: Code: Aug 19 17:37:00 Develop kernel: [3957161.011493] OOM killed process 23734 (java) vm:6581876kB, rss:4038096kB, swap:0kB OOM stands for out of memory but at any given time the server is only using at max 1.5gb ram so that is not it. I did some more research and found that it could be java not being able to use more threads so I added "-Xss128k" to the start up but it didn't seem to fix anything. So if anyone has any idea that would be great
-Xss sets the default thread size for java to try and solve the issue I am having which I believe is thread related since java is clearly not running out of memory. My start-up arguments are: Code: java -Djline.terminal=jline.UnsupportedTerminal -server -XX:+UseG1GC -XX:MaxGCPauseMillis=100 -XX:ParallelGCThreads=2 -XX:ConcGCThreads=2 -XX:+AggressiveOpts -Xss128k -Xmx3328M -jar craftbukkit.jar
You doing any WorldEdit? There are certain operations that can chew up a hunk of memory quick. I used to be able to crash mine real quick if I was regenerating a lot of chunks, and I think copying/pasting large areas can do similar. Maybe a plugin list would help us too. You could try installing http://dev.bukkit.org/server-mods/lagmeter/ and setting the log interval to something small (also enabled). It may catch a surge in memory usage prior to a crash.
i used to but I switched to this plugin to get rid of lag issues http://dev.bukkit.org/server-mods/pylamo-restoration-system/files/?sort=name Yes I do as stated in my first post. I was doing a bit more research and apparently even though command book states that the server memory usage is staying low the java process is slowly increasing memory usage. I removed 3 plugins that I didn't need for the server but it didn't seem to do much. When the server crashes again I set it to do a heap dump that hopefully will tell us something. Edit: I updated NoCheatPlus to the latest dev build and everything seems to be running normal again. Seems like there was a memory leak in version 3.7.0