GC overhead limit exceeded

[vai]

when I start the server using safemode, I think it does not give me enough memory to load up all the plugins. I am using a linux box with centos and I believe it is not a service on the remote box.

[tcarr]

There are several ways to run ES5 from a Linux script. See Running ElectroServer. If you use one of the "java jar" scripts, you can specify the JVM's heap size by adding -Xmx64M (or whatever amount of Mb you want to give it) to the other options on the java jar line.

If you want to revert your ES Admin's heap size instead of fooling with the command line and safemode, I can tell you how to use DbUtility to do that.

[vai]

if i use java -jar -Xms128M -Xmx128M lib/ElectroServer5-bootstrap.jar -mode StandAlone -config config/Configuration.xml, the server starts properly .. but if I set the heap size to 128M through es5 admin, the server does not start.

[tcarr]

It sounds like your default JVM might be grabbing too much memory for the bootstrap process, or else that the ES Admin's settings were not made correctly. Can you give me a screen shot of the ES Admin's general settings, showing both the heap and command line boxes? and the ElectroServer5.log file for when you try to start ES5 without the java jar script, so that I can see the amount of memory that JVM is grabbing for the bootstrapper.

Or you can just shrug and decide to use the java jar script. I use that kind of script all the time myself. If you use that and then use the ES Admin's Restart button, does it start correctly?

[vai]

ESCapture.jpg


i had started my server the last time using java jar script .. so i just restarted it from es5 admin and it did come up fine.

[vai]

Attachment 227


i had started my server the last time using java jar script .. so i just restarted it from es5 admin and it did come up fine.

[tcarr]

It sounds like the problem is that 128M is close to the limit of the available memory on the box. The bootstrap process takes some memory, then there isn't 128M left for the main ES5 process. You can experiment with smaller amounts until you find one that works for you, or you can just continue to use the java jar start script.

(or find a way to get more memory on your host - either killing other processes or moving to another server that has more RAM, etc)

[vai]

If i start the server with "java -jar -Xms128M -Xmx128M lib/ElectroServer5-bootstrap.jar -mode StandAlone -config config/Configuration.xml" isn't it 128M minimum that it would get?

[tcarr]

If you don't use the "-safemode" option on your java jar line, this reserves 128M for the bootstrap process, which then tries to create the main process but there isn't enough memory for it. If you add "-safemode" then it's just a single process and it ignores the ES Admin's command line parameters. When you use the Restart button on the ES Admin, it stays in the main process thread, shutting down and then starting again without making another process.

[vai]

two more questions
1) do the bootstrap and main process share 128M ?
2) what does the max heap size set (in es5 admin tool) .. right now in my startup script I have java -jar -Xms128M -Xmx128M lib/ElectroServer5-bootstrap.jar -mode StandAlone -config config/Configuration.xml and in the max heap size in es5 admin tool it says 64MB.

Many Thanks!