Performance Degradation When Expanding A Report Folder Tree In P6 To Display Reports (Doc ID 1937777.1)

Last updated on MARCH 10, 2016

Applies to:

Primavera P6 Enterprise Project Portfolio Management - Version 8.2.0.0 and later
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
When loading the Reports applet, performance degradation is experienced in one of two places:

EXPECTED BEHAVIOR
When loading the Reports applet or expanding a catalog folder in the reports applet to display the reports, for initialization of the applet to load much quicker.

STEPS
The issue can be reproduced at will with the following steps:

  1. Login to P6
  2. Select the Reports link
  3. Note the amount of time it takes for initialization of the applet to complete and load the associated report list or the amount of time it takes after expanding a catalog folder and before the reports display.

OR

  1. Login to P6
  2. Select the Reports link
  3. Expand the catalog folder list, and note the amount of time it takes to display the reports configured under one of the catalog folders. During this time, a "Loading..." box is displayed.

ADDITIONAL INFORMATION

EXAMPLE 1:
Example catalog folder list displayed once initialized is:
Custom (folder)
   --> Testing (folder)
          --> Reports underneath

Under the above example, if P6 is configured for the "folder path" to "/Custom", the reports applet will load quickly but expanding the "Testing" folder can take a long time before the reports display.

EXAMPLE 2:
Custom (folder)
   --> Reports underneath

Under the above example, if P6 is configured for the "folder path" to "/Custom", the reports applet itself can take a long time to load before the applet initializes and provides ability to display the reports.

During this time, if the loading exceeds WebLogic's "Stuck Thread Max Time", you may experience Stuck Threads from the POST request of /xmlpserver/services/PublicReportService.

Example:
<[STUCK] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "612" seconds working on the request "weblogic.servlet.internal.ServletRequestImpl@44e2f637[
POST /xmlpserver/services/PublicReportService HTTP/1.1
Content-type: multipart/related;start="<rootpart*c4a3090f-3858-4a00-b0d5-7814517a0306@example.jaxws.sun.com>";type="application/xop+xml";boundary="uuid:c4a3090f-3858-4a00-b0d5-7814517a0306";start-info="text/xml"
Soapaction: ""
Accept: text/xml, multipart/related, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
User-Agent: Oracle JAX-WS 2.1.5
Connection: Keep-Alive
Content-Length: 696

To see the WebLogic "Stuck Thread Max Time":

  1. Log into the WebLogic Admin Console for BI deployment
  2. Navigate to base_domain > Environment > Servers > $ServerName > Configuration/Tuning
  3. Note the value for Stuck Thread Max Time.

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms