Zheng Tech Blog

Thanks Martin Deh from A-Team for identifying it is a recently reported bug. To summarize the problem: during a load testing (>1000 users attempt) on a WebCenter framework application developed with content presenter task flows, the performance (page response time) was greatly impacted by a series of parked threads. The issue was not produced in the 1000 users test. The parked threads took from >30 seconds to minutes to resume. By investigating the stack trace, the culprit is pointed to java.util.concurrent.locks.ReentrantLock.lock() which is called by UCMBridge.getAccessLevel(IdcContext, DataObject, ITrace). This issue has been filed as a bug ( Bug 17330713 ) and the patch/fix is to be provided soon (Update: the patch is available as of date 11/4/2013 for 11.1.1.7.1) The following shows a graphic indication of the parked threads (gray) through the tests. As you can see, the gray areas took the majority of the timeline. Here is the stack track of one particular parked ...

Update : The Oracle Patch on the bug has been released: Patch 17328920 : CONTENT PRESENTER THROWS STUCK THREAD AND OOM WHEN UCM RETURNS MANY PROFILES.  In this fix, a system parameter "contentTypeLazyCaching=true" is requested to be added on the JVM startup. Custom code has been added into the ContentTypeFactory.class in the two places: %ORACLE_HOME%/webcenter/modules/oracle.webcenter.content.integration_11.1.1/ucm_spi.jar/oracle/webcenter/content/integration/spi/ucm/factory/ContentTypeFactory.class %ORACLE_HOME%/webcenter/modules/oracle.webcenter.content.integration_11.1.1/content-app-lib.ear/APP-INF/lib/ucm_spi.jar/oracle/webcenter/content/integration/spi/ucm/factory/ContentTypeFactory.class The directory could be either on your local Jdev folder or on the remote WebCenter portal server. The added custom code is a new method getMinimalContentTypes():   public synchronized List<ContentType> getMinimalContentTypes()     throws RepositoryExc...

According to the Oracle document , WebCenter Spaces provides out-of-the-box translations for 27 languages and 100 different locales. These 27 languages are available after the WebCenter installation and no additional developments/configurations are needed. There are two ways to see the translated WebCenter Space. One is via the provided language changer UI on the Space page header. The other is via the browser locale setting. For the WebCenter framework application, the 27 languages are also available for those build-in services and features.Since the framework application doesn't have the out-of-the-box language changer UI but you can always set your preferred locale in your client browser. For example, here is a snapshot of the admin page of a WebCenter framework application displaying in English language. Now I change my preferred browser display language to Spanish (ES). Refresh the portal page and I can get it displaying in Spanish. Again I chang...