I have an application that runs fine using Default Role, I am trying to customize it with MDS. Every time I run it in Customization Developer Role, with minimal changes (1 new VO attribute to test), I am getting this error (java.lang.OutOfMemoryError: GC overhead limit exceeded). Shouldn't the system requirements for base and customized projects be the same? Is there any special settings needed to run the customized project?
- I am using an external properties file to specify layer values
- Same layers key/value are defined in "customization.properties" and "CustomizationLayerValues.xml"
- Customization done only on Site layer
did not see this (you don't name a JDeveloper version, so hard to tell if I am using the same though). However, have a look here
You might be getting OutOfMemoryError from JDeveloper IDE. "Project Properties->Run/Debug/Profile->Java Options" do not specify the Java options of the JDeveloper IDE but the ones for the run target when it is being run from inside JDeveloper. IDE's Java options can be specified in <JDevHome>/jdeveloper/jdev/jdev.conf file and in <JDevHome>/jdeveloper/ide/ide.conf file. Have a look at these config files and modify the necessary memory options as appropriate.
I've upgraded my machine from 4Gb to 8Gb RAM and allowed Jdev to use more memory by changing the options below:
Now my application runs fine in Customization Developer role as well. It looks like Jdev needs at least 4096Gb to be able to run it.
In my opinion, setting MaxPermSize to 3072M is too much. It is not a problem to set it to such a high value, but in my opinion 3072M is unnecessarily high. 1024M should be enough.
Also, note that <JDevHome>/jdeveloper/jdev/jdev.conf starts with a directive to include<JDevHome>/jdeveloper/ide/ide.conf, so the settings of jdev.conf override the eventual corresponding settings in ide.conf (e.g. there is no need to set -Xmx5120M in your ide.conf).
I lowered the MaxPermSize to 1024M and it seemed to not have affected anything so that will keep it low, as you adviced. Like you said, I noticed that changing the ide.conf did not really affect Jdev behavior, what is the directive to include the ide.conf on the jdev.conf that you mentioned?