2 of 2 people found this helpful
The process-controller shouldn't need that much memory for sure. The host-controller neither, however that also depends a bit if you are using a monitoring solution like RHQ / JON.
Thanks for the response.
I have decided to move away from the domain setup for now. The problem I had with it, is that all the profiles are located in the domain.xml and if I want to have for example a different datasource for each server, I had to create a different profile for each or make all the datasources available for all servers.
So I am now working with standalone mode.
My current problem is that it uses standalone.conf, where all the heap settings are specified, but I want to use only one set of JBoss binaries and use the externally located configurations for each server I start up.
Problem is, it always uses the same standalone.conf so I am currently unable to set -Xmx or -Xms. According to the documentation (https://docs.jboss.org/author/display/AS7/Admin+Guide#AdminGuide-JVMsettings) it should be possible to use command-line arguments, but that is not the case. (also mentioned in this thread: https://community.jboss.org/message/634320)
Does anybody have an idea on how to make it work? I don't want to run each application server with the same heap settings.
I've solved it like this:
- created a script file which sets the JAVA_OPTS
- load that script (". /path/to/server.conf") in bash
- then execute the standalone.sh
So now each of my servers had a separate directory containing a server.conf file with the memory settings that gets loaded when I execute the start script.
I have a similar situation with multiple processes - domain controllers process controllers plus the instance on a VM where memory is tight. Are there any guidelines to indicate how much I can reduce this allocation?