How To Speed Up Application Undeployment in JDeveloper 11g R2

There was new patch set released this week for JDeveloper 11g R2, its called (11.1.2.1.0). I had a quick look, there are still few issues left from previos release (11.1.2.0.0), but overall this new update looks better and more stable.

Update: Same applies for JDeveloper 11g R1.

This post describes issue related to long application undeployment time. Reproduced when running on embedded WLS directly from JDev. I had this issue in (11.1.2.0.0), same reproduced with (11.1.2.1.0).

Sample app is fairly basic, it contains one ADF BC AM, read-only VO and one JSF page - ADFAppADFBCSimple11R21.zip:

As per documentation chapter 9.3 Configuring Your Application Module Database Connection, 11g R2 differently than 11g R1, automatically assigns JDBC Data Source name for newly created AM - java:comp/env/jdbc/HrDSDS:

This is good, but once we need to restart application, or even stop it from JDev:

It takes in average 2 minutes to undeploy ADF app. It says - resource pool shutting down, ignoring 1 resource still in use by applications:

If we switch to JDBC URL type and provide connection name, as it was by default in 11gR1:

As we can see from the log, when connection is changed to be JDBC URL type, application is undeployed just in 2 seconds:

2 minutes vs. 2 seconds, I guess difference is obvious? :)

Let's dig deeper.

We can remove data source prefix and leave only - jdbc/HrDSDS:

This would need to define data source on WebLogic manually, when we have prefix java:comp/env/ it means JDev will create temporary data source automatically. I have defined jdbc/HrDSDS manually:

Application is undeployed fast as well, same as using JDBC URL - around 2 seconds:

Lesson learned - in 11g R2, until it will be fixed - don't use auto generated prefix name java:comp/env for data sources. Always define data sources manually on WebLogic or use JDBC URL, as it was default in 11g R1.