|Performance and stability of JDeveloper 11gR2 vs. 11gR1||Frank Houweling||3/12/12 10:33 AM|
I would like your thoughts on the performance and stability of
JDeveloper 11gR2 vs. 11gR1.
For 5 months now we are building an ADF application in 11gR2
(currently 126.96.36.199) and we daily experience performance and stability
problems with this version of JDeveloper. Although 11gR2 starts up
quickly, compared to the first release we have worked with (188.8.131.52
and 184.108.40.206) we have a strong impression that the 220.127.116.11 release
has proportionally more errors and is less stable. One of our
customers, also developing in 11gR2, experiences the same. Currently,
our project members are discussing and investigating whether it might
be better to go back to the latest 11gR1 version to be certain that
we'll have a stable production environment. Some of our issues
-Many times when we run the project we get 'An unexpected error has
occurred in JDeveloper' error
-Very often during debugging, the debugger goes suddenly to the Timer
class and opens this class in JDeveloper
-Redeploying is still slow, even after we modify the datasource string
as described in: http://andrejusb.blogspot.com/2011/09/how-to-speed-up-application.html
-We have some indications of a memory leak; we see the Java heap size
increasing during each redeployment and often a we get an
-I've read the comparison between 11gR2 and 11gR1 in
https://forums.oracle.com/forums/thread.jspa?threadID=2329130 , but I
do not read people mentioning the issues we have
-Are you experiencing the same performance and stability issues as we
do in 11gR2 ?
-Do you know any ADF applications that are successfully running on a
11gR2 production environment and do perform well for many concurrent
|Re: [ADF EMG] Performance and stability of JDeveloper 11gR2 vs. 11gR1||Mark Robinson||3/13/12 10:08 AM|
I haven't had any performance issues myself although I have noticed several bugs in JDeveloper.
I, too, frequently get 'An unexpected error has occurred in JDeveloper' often when I deploy to debug or open the persistence.xml file.
The OutOfMemoryException is a long-time known issue in WLS. It is particularly noticeable when you use Hudson to do automated builds.
One issue I find really problematic is that JDev caches some of the build data isn't entirely correct in its handling. Often JDev will not rebuild stale files, this mostly occurs when you do an update from a source control system.
|Re: [ADF EMG] Performance and stability of JDeveloper 11gR2 vs. 11gR1||shay shmeltzer||3/14/12 10:56 AM|
A couple of notes about the out of memory after several deploys.
You might want to try and increase the memory allocated to JDeveloper in the jdev.conf file.
Other parameters that some people found helpful for performance here:
Also in general with 11.1.2 you shouldn't need to do many redeployments because of the hot-deployment feature - which allows you to save/recompile and reload your page in the browser for most of the changes to existing pages.
|Re: [ADF EMG] Performance and stability of JDeveloper 11gR2 vs. 11gR1||Renan de Castro||3/20/12 2:53 PM|
I experienced a lot of problems while trying to run JDeveloper 18.104.22.168 with a 64bit JDK (1.6.31), a good example is that you can't
use the fast swap feature on Weblogic, it will run on a "Cannot attach to a process 32-bits" error.
Also, we experienced less performance and bug issues with the 32-bits version of JDK (both for JDeveloper and Weblogic).
For example, after a SVN Update there is a great chance of some strange compilation error that needs a JDeveloper restart just to delete the .data folder and all its garbage (except for the History files inside it, it saved my life twice).
Renan Monteiro de Castro - Linkedin
|Re: Performance and stability of JDeveloper 11gR2 vs. 11gR1||Hyangelo||3/26/12 7:06 AM|
The part about WebLogic conking out after several deploys is very true and is one of the many annoying things that sometimes drive me mad about WebLogic and JDeveloper. If I were to be given a dollar every time JDev throws an unexpected exception or weblogic runs out of memory, I'd be able to buy a gizillion more ram to feed my local weblogic server.
I've gotten used to it by now but when I was starting with the JDev/ADF/WebLogic ecosystem and coming from eclipse/<insert relatively lighter frameworks here>/Tomcat everything felt as slow as molasses. What is worse is that WebLogic takes a while to restart especially if I have some webservices deployed to it. It takes an unholy amount of memory at startup as well. I understand that comparing weblogic with tomcat isn't really fair since Tomcat isn't exactly an application server but Oracle has to do something about this if they want developers to actually like working with ADF. don't get me wrong, I like ADF now. It was an acquired taste for me. But it was a bitter start and the issues outlined above(exceptions, oom, obese development app server) gave me constant, consistent daily grief.
|RE: [ADF EMG] Re: Performance and stability of JDeveloper 11gR2 vs. 11gR1||Oracle ITself||3/26/12 7:21 AM|
i totally agree with you regarding Memory problems in Integrated & Stand Alone Weblogic Servers and Oracle has to do something .. as per my experience in Oracle ADF & Wls .. until now we suffer from this Memory issue ..
Regarding the Stability : 11G R1 still better than R2 until nowm at least from my point of view !!, some of problems solved in 11.1.3 & 4 repeated again in 11G R2 !!
and at the same time we face a lot of bugs after we decided to transfer our project from 22.214.171.124 to 126.96.36.199 ..
we contacted Oracle and send them some of theses bugs and they decided that it is really bugs by their Testing Team and many of them will be solved by in coming Release 188.8.131.52 (we are waiting for it now) ..
Note : Oracle will publish new release 184.108.40.206 in coming 2 Months (as per Oracle Team Reply to us) ..
Senior Oracle ADF & SOA Consultant at Confidential Company
Kingdom Of Saudi Arabia
Tel : KSA: +966545874498 Egy : +201150052059
Mail : Oracle...@Hotmail.com
LinkedIn : http://sa.linkedin.com/pub/wael-abdeen/12/624/996
FaceBook : http://www.facebook.com/profile.php?id=1272993189
Date: Mon, 26 Mar 2012 07:06:43 -0700
Subject: [ADF EMG] Re: Performance and stability of JDeveloper 11gR2 vs. 11gR1
|Re: [ADF EMG] Re: Performance and stability of JDeveloper 11gR2 vs. 11gR1||Chris Muir||3/26/12 4:58 PM|
Does anyone have bug numbers for the WLS memory problem(s)?
On 26 March 2012 22:21, Oracle ITself <oracle...@hotmail.com> wrote:> Mail : Oracle_ITself@Hotmail.com
|Re: [ADF EMG] Re: Performance and stability of JDeveloper 11gR2 vs. 11gR1||Jang Vijay Singh||3/27/12 12:36 AM|
I have noticed intermittent problems with the debugger which tends to freeze - yet to isolate the issue and reproduce it.
Other than that, jdev 11gR2 perf seems to be good- more so after applying jdec.conf changes suggested earlier in this thread.
There is it seems a known issue with memory leaks on redeployments (which might also impact the integrated instance) but that sorts itself after deleting existing app on wls before redeploying as i found on forums/blogs.
Sent from my iPhone
|Re: [ADF EMG] Re: Performance and stability of JDeveloper 11gR2 vs. 11gR1||Hyangelo||3/27/12 10:31 AM|
Did my best to search in Oracle Support and the best that I could find is this: 8131207 - REPETITIVE REDEPLOYING AN EAR USING ANT SCRIPT RESULTS IN OOM
OT: Searching through oracle support reminded me of one other thing that Oracle definitely needs to do to improve ADF: expose the bug parade publicly even if it is just read only. Make it indexable and searchable through google. That should help developers find out easier if the issue they are seeing is a known issue or not since the first reasonable place to start searching would be on google. Searching for a bug in Oracle Support is quite unsavory and a pain in the ass. I wonder if Oracle bothered applying their 'usability expertise' on that service?
|Re: [ADF EMG] Re: Performance and stability of JDeveloper 11gR2 vs. 11gR1||Chris Muir||3/27/12 5:50 PM|
Thanks for searching for the bug. Note the bug is specific to Ant
deployments to WLS. It also looks like the bug was originally
recorded in BEA's systems and when ported to Oracle bugs database, it
was graded as severity 3. It hasn't been looked at again since then.
Unless a more recent or relevant bug is found and posted here, my
As for the quality of Oracle Support services, this is beyond the
|Re: Performance and stability of JDeveloper 11gR2 vs. 11gR1||Jan Vervecken||4/16/12 12:14 PM|
- about "Does anyone have bug numbers for the WLS memory problem(s)?"
-- Today I noticed bug 13964205, "WLS GETS OOME IF ADF APPLICATION IS
> On 26 March 2012 22:21, Oracle ITself <oracle_its...@hotmail.com> wrote:> > Mail : Oracle_ITs...@Hotmail.com
> > LinkedIn :http://sa.linkedin.com/pub/wael-abdeen/12/624/996> > From: hyang...@gmail.com
> >https://forums.oracle.com/forums/thread.jspa?threadID=2329130, but I
|Re: [ADF EMG] Re: Performance and stability of JDeveloper 11gR2 vs. 11gR1||Chris Muir||4/16/12 6:20 PM|
Thanks for the follow up Jan.
This bug links to the none-published bug 13726772 which is flagged as
I know you'll ask why bug 13726772 was not published. In this case
I've recorded this bug as issue ADFEMG-16 in Jira such that we can
|Re: [ADF EMG] Re: Performance and stability of JDeveloper 11gR2 vs. 11gR1||Hyangelo||4/17/12 6:16 AM|
P.S. Is it really necessary to some make ADF/JDev/WLS bugs private/unpublished? I think it this particular practice is unfair to us developers and making the bug parade public and searchable from google will be a really big help.
|Re: [ADF EMG] Re: Performance and stability of JDeveloper 11gR2 vs. 11gR1||Chris Muir||4/17/12 6:38 AM|
Understood, in fact I even blogged the same sometime back about Google. But suggesting such in this forum won't get change to Oracle's support policies.
|Re: Performance and stability of JDeveloper 11gR2 vs. 11gR1||Jan Vervecken||4/17/12 11:58 AM|
- about "... this is one of my top productivity sink holes on a day to
day basis ..."
-- If you think you are hitting bug 13964205 you could express your
interest to have it fixed by leaving a comment at http://java.net/jira/browse/ADFEMG-16
or in an Oracle service request.
- about "... making the bug parade public and searchable ..."
-- Although new, currently http://java.net/projects/adfemg and its
JIRA issue tracker is the closest to that there is I think.
> P.S. Is it really necessary to *some* make ADF/JDev/WLS bugs
|Re: Performance and stability of JDeveloper 11gR2 vs. 11gR1||Hyangelo||4/18/12 5:13 AM|
Yes, I agree. I don't think posting here or in OTN or anywhere can change Oracle's policy. Personally, this is one of the primary downside of using ADF as opposed to other open-source alternatives.
|Re: [ADF EMG] Re: Performance and stability of JDeveloper 11gR2 vs. 11gR1||Prasad Narahari||7/30/12 7:01 PM|
We have an ADF application developed and running on 220.127.116.11, Our external customers are reporting IE9 browser compatability issues occasionally. So, we have decided to upgrade to either 18.104.22.168 or 22.214.171.124.
My search for 126.96.36.199 in this Google group resulted in this thread which is talking about performance issues and stability issues.
Many people mentioned these problems being part of 188.8.131.52. I am curious to hear if any body has any experiences with 184.108.40.206
Not sure if it is worth going for 220.127.116.11 against 18.104.22.168 at this point of time
Also within 11gR1 which would you prefer 11.1.16 or 11.1.15
One more thing, our application (22.214.171.124) is using web services (WSDLs) out of a seperate 126.96.36.199 SOA suite. They are running on different web logic instances.
Appreciate your feedback, this would really help us.
|Re: [ADF EMG] Re: Performance and stability of JDeveloper 11gR2 vs. 11gR1||vikceo||7/30/12 9:08 PM|
|Re: [ADF EMG] Re: Performance and stability of JDeveloper 11gR2 vs. 11gR1||Chad Thompson||7/31/12 6:12 AM|
This will depend on your immediate needs: 188.8.131.52 does have a few enhancements and is the 'bridge' to the next major releases of ADF and Fusion technologies that will use the JEE6 standards (Facelets for view layers, etc.)
With the 11.1.1.x versions you should be able to simply 'upgrade' your JDeveloper (and the ADF libraries on your deployment environments!) without too much trouble - the 11.1.2.x versions are a little different in terms of patching, use of Enterprise Manager/Fusion Middleware Control, etc.
I'd jump to the 'highest version you can support' because the newer versions will have bug fixes, minor enhancements, etc. that will make things easier (hopefully) for you. Which brings me to the last point:
The other thing to consider here is your developer/development environment - if you are supporting both the SOA Suite plus the ADF application, you might find it easier to match ADF and SOA versions for your deployment and development, if anything to keep "one version of JDeveloper" and minimize any issues with incompatibility.
If most of your development is Fusion Middleware focused, you might have an easier time sticking with the 11.1.1.x versions until you do a larger migration to the 11.1.2.x / 12c versions of ADF and Fusion Middleware.