This question was also from an Expert Panel session at Oracle Open World (10/11-15/2009). The experts were beating the brushes and I answered the question.
The cloned instance does not copy the Web Application Server cache at $COMMON_TOP/_pages. Thus, for the first access to a JSP pages, the system needs to compile it into HTML and put in _oa__html (HTML pages) and _oa__java (JAVA class). The future access to this page will be faster. In the production environment, the cache is never refreshed. After a few rounds of patching or apply consolidated updates, there are a lot of junks in the cache. Thus, production instance delivers the HTML pages slower than cloned instances even if the cloned instance on the same set of machines as the production instance.
Here is the way to refresh EBS web server cache:
1. rename _oa__html and _oa__java.
cd $COMMON_TOP/_pages
mv _oa__html _oa__html.old
mv _oa__java _oa_java.old
mkdir _oa__html _oa__java
2. recreate the cache
perl -x $JTF_TOP/admin/scripts/ojspCompile.pl --compile –quiet
3. If during the clone procedure, the cache got copied over, you might get login problem due to missing java class etc. You also need to refresh the cache. See Note 466739.1 AppsLocalLogin.jsp Fails With java.lang.NoSuchMethodError oracle.apps.fnd.sso.HttpLanguageMap.getOracleFromHttp
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment