Errors and Cache Expires for Content Presenter During Load Testing of a WebCenter Portal Application (Doc ID 1619201.1)
Last updated on FEBRUARY 03, 2017
Oracle WebCenter Portal - Version 184.108.40.206.1 to 220.127.116.11.2 [Release 11g] Information in this document applies to any platform.
This issue could be seen on a custom WebCenter Portal application which is being load tested or being heavily used on an environment with a large number of active users. The Webcenter Portal application contains the Content Presenter taskflow.
This error is seen multiple times in the managed server log for the managed server where the application is deployed:
<Error> <oracle.webcenter.doclib.internal.view.presenter.ContentPresenterBackingBean> <WCS-07080> <Error retrieving node(s). oracle.webcenter.doclib.internal.model.presenter.PresenterRetrievalException: oracle.webcenter.doclib.internal.model.presenter.conf.PresenterConfigurationException: <date> oracle.webcenter.doclib.internal.model.presenter.conf.PresenterConfigurationException asError ALL: Query expression must be a valid, non-empty expression.
at oracle.webcenter.doclib.internal.view.presenter.PresenterRetrievalService.getNodes(PresenterRetrievalService.java:86) at oracle.webcenter.doclib.internal.view.presenter.ContentPresenterBackingBean.getDatasourceResults(ContentPresenterBackingBean.java:254) at oracle.webcenter.doclib.internal.view.presenter.ContentPresenterBackingBean.getNodes(ContentPresenterBackingBean.java:169) ......
Nevertheless the WebCenter Portal Content Presenter Task Flow Coherence cache expires about every hour and it is observed that the coherence cache is not caching all the expected data for WebCenter Portal applications. The periodic performance delays resulted by this are caused by WebCenter Portal calling the VCR_GET_CONTENT_TYPES Service. This service is called about every hour from Webcenter Portal and takes about 3.3 seconds to complete. Therefore the page construction time is slow. The rest of the content is coming from the coherence cache as expected.
So, the coherence cache does not cache all content types that are configured. The following caches are not listed in the list of caches shown via EM, even though these are configured in content-coherence-cache-config.xml file.: