Technical: MCF: Application Server startup script fails with out of memory: java heap space

Resolving The Problem

There are many things that could cause an app server to throw an out of memory exception, but if you have an existing implementation and suddenly you are seeing this issue, the most likely cause is that someone enabled the "yfs.logall" property in <INSTALL_DIR>/properties/customer_overrides.properties. Disable this flag by setting it to "N" or removing it.

Note: although we do not recommend directly modifying the yfs.properties file provided out of the box, this property may have also been added to yfs.properties, so if you don't find it in customer_overrides.properties, you can check there as well.

If you do not find yfs.logall defined in either place and you are still unable to start the application server, check that you have set your Java parameters as recommended in the MCF Installation Guide, Appendix A.

For more information on using customer_overrides.properties, refer to the MCF Properties Guide (or prior to MCF 8.5, refer to the Installation Guide)

If that also doesn't help, please contact Sterling Support for assistance.