Performance tuning of Jdeveloper 12c

Very frequent we get issues of JDeveloper hangs.Then you need to close JDeveloper and restart. if you are developing and debugging, this problem occurs more frequently.This post tell how to make your jdeveloper with better performance.

Jdeveloper –

1) Go to MW_HOME \jdeveloper\ide\bin\ide.conf and increase the Max heap size (Xmx).

//Set this option depend on your system configuration.I have 16gb ram, I prefer to set this.
AddVMOption -Xms2048M
AddVMOption -Xmx4096M

2) Go to MW_HOME \jdeveloper\jdev\bin\jdev.conf and set the following parameters

// Increase your MaxPermSize
AddVMOption -XX:MaxPermSize=1024M

//Adds a memory monitor which helps in check current heap used by jdeveloper

AddVMOption -DMainWindow.MemoryMonitorOn=true

//ADD the following JVM options towards the end of file
AddVMOption -XX:+UseStringCache
AddVMOption -XX:+OptimizeStringConcat
AddVMOption -XX:+UseCompressedStrings
AddVMOption -XX:+UseCompressedOops
AddVMOption -XX:+AggressiveOpts
AddVMOption -XX:+UseConcMarkSweepGC
AddVMOption -DVFS_ENABLE=true
AddVMOption -Dsun.java2d.ddoffscreen=false
AddVMOption -XX:+UseParNewGC
AddVMOption -XX:+CMSIncrementalMode
AddVMOption -XX:+CMSIncrementalPacing
AddVMOption -XX:CMSIncrementalDutyCycleMin=0
AddVMOption -XX:CMSIncrementalDutyCycle=10


3 ) Disable the SVN versioning system that is built into JDeveloper.Uncheck the checkbox for Subversion for example support for GIT

4) Reduce ON-Save and AFTER-Save Actions
Go To Tools >> Preferences >> Code Editor >> Save Actions
Remove “Build After Save”



After that, Please restart jdeveloper.Your jdeveloper will give better performance

Running Oracle ADF application on High availability (HA) architecture

Oracle ADF is used to build large enterprise application. And if you want to have your application to run on high availabilty then you should understand what is High Availability (HA) .

What is High Availability –
High availability refers to the ability of users to access a system without loss of service. Deploying a high availability system minimizes the time when the system is down, or unavailable and maximizes the time when it is running, or available. This section provides an overview of high availability from a problem-solution perspective. With HA , even for new deployment you will never have down time.

Normally in large enterprise application , you don’t want your system to be down..Application deployed in cluster environment. If one of the server down then the user session should replicate to another cluster . Now , we have Oracle HTTP Server (OHS) or Apache plugin is to used to get single URL and manage internally to replicate the session and send request if one of cluster is fail.

How a web server handle request


Cluster- Group of managed server running to provide scalability and reliability. In this multiple wls instance simultaneously and working together.Cluster is part of WLS domain . A domain can have multiple cluster


Architecture of Weblogic HA

apache web server

Now the important point for developer – Few points designing and developing Oracle ADF application for HA.
There are 6 types of memory scopes. Read more on ADF memory scopes

When the Fusion web application runs in a clustered environment, a portion of the application’s state is serialized and copied to another server or a data store at the end of each request so that the state is available to other servers in the cluster.If it not serialized then user will lose data upon fail-over.

WebLogic duplicates those sessions by serializing the objects in the session and than transfers it to the secondary machine. Only the object that are stored in the session will be replicated. From an ADF perspective this means that managed bean with pageFlowScope and above will be replicated.It is very well defined in Oracle documentation and A-team article.

Configuring Oracle ADF development for High Availability

=> Changes in Application server-

While doing development Jdeveloper integrated server will not throw any errors by default. Add this parameter in server has to be run with the following JVM parameter:


Note that this check is disabled by default to reduce runtime overhead. Do not use this after your testing is complete.

-> Changes in ADF code

-> Please make sure that managed beans used in ADF application with a scope greater than one request should be serializable ( implement the interface). Specifically, beans stored in session scope, page flow scope, and view scope need to be serializable.

– All pageflowscope and viewscope managed beans should not contain UI bindings. In essence, component bindings should live for a http request (request scope or backingBean scope). Any state or data you need for a longer duration can be saved in a pageflowscope bean separately.

– Make sure Oracle ADF is aware of changes to managed beans stored in ADF scopes (view scope and page flow scope) and enable the tracking of changes to ADF memory scopes.

use below code to notify ADF

controllerContext ctx = ControllerContext.getInstance();


-> Configuring Application Modules

– Right-click the application module and select Configurations.Click Edit.Click the Pooling and Scalability tab.
Select the Failover Transaction State Upon Managed Release checkbox.

<AppModuleConfig ...
 <AM-Pooling jbo.dofailover="true"/>

-> Configuring weblogic.xml

In weblogic.xml file, add entry as below persistent-store-type definition to the session-descriptor element like below



-> Configuring adf-config.xml

In adf-config.xml file, add entry as like below

<adf-controller-config xmlns="">


Happy Learning with Vinay In techartifact.


Jdeveloper bug with AdfKeyStroke.ENTER_KEY in IE and Mozilla

Hi All,

If you are facing an error of JS like and you are handling enter key using AdfKeyStroke.ENTER_KEY

Mozilla Firefox



Message: ‘undefined’ is null or not an object

Don’t be afraid, its not your fault. It is happening in jdeveloper .
Cause- Might be when we use AdfKeyStroke.ENTER_KEY, it generates some internal JS event by framework, which can cause this issue.

In all other version , it is working fine.So if you upgrade your application to Jdeveloper
and you got this error, Raise an SR to Oracle.There is already bug raise by Oracle . Bug # 19137193

Till the next post, happy coding….