I posted this to the users list first and am re-composing my email for
the Dev list per Scott's suggestion...
I am running SipX on CentOS 5.4 running within an OpenVZ container. For
those who are unfamiliar with OpenVZ, it's a container-style
virtualization platform. The issue I am running into is that Sun's JRE
just loves to allocate virtual memory. For every instance of java, 200mb
of virtual memory is allocated on my setup. Why is this a problem?
OpenVZ does not present guest operating systems any swap space. Thus, it
has to allocate everything from what the guest sees as physical memory.
Starting sipx 4.0.4 consumes about 1.4GB of RAM.
When I upgraded to 4.2, I was suddenly out of memory because of the
extra java processes that it launches. I cannot allocate more than 2GB
of RAM for this right now and switching to Xen or KVM is not really in
the cards.
I've searched high and low for a method to stop Java from thinking it
needs 200MB of resource allocation and have had minimal success. Forcing
jre.cfg to use -client instead of -server reduced usage by only about
150MB. I've tried a wide gamut of -X options but I can't seem to control
Java at all.
I recently installed IBM's j9 and configured it as an alternative, but
starting the sipxecs service results in five java processes spiraling
out of control...
Does anyone have any suggestions or am I out of luck?
-- Robert
_______________________________________________
sipx-users mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/
