My Oracle Support Banner

Timesheet Approval Performance Issues when Approvals Are Set to 'Two Approval Levels - Project and Resource Managers' Approval Required' and Timesheet Audting Is Enabled (Doc ID 2645611.1)

Last updated on MARCH 24, 2020

Applies to:

Primavera P6 Enterprise Project Portfolio Management - Version 17.12.7.0 to 17.12.15.0 [Release 17.12]
Primavera P6 Enterprise Project Portfolio Management - Version 19.12 to 19.12.2.0 [Release 19.12]
Primavera P6 Enterprise Project Portfolio Management - Version 18.8 to 18.8.17.0 [Release 18.8]
Primavera P6 Enterprise Project Portfolio Management Cloud Service - Version 17.12.0.0 to 17.12.15.0 [Release 17.12]
Primavera P6 Enterprise Project Portfolio Management Cloud Service - Version 18.8 to 18.8.17.0 [Release 18.8]
Information in this document applies to any platform.

Symptoms

Users experience performance issues approving timesheets when approvals are set to Two approval levels - Project and Resource managers' approval required and Timesheet Auditing is enabled. 

The following errors can potentially be found in the P6WebAccess.html log file, although they are not produced for all occurrences of the issue:

<DATE> <$TIMESTAMP> [ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)' ERROR com.primavera.guisupport.timeapproval.TimesheetApprovalDataSaver ?:? @#$%/rest/timesheet/save (User Id: ###### DB Id: 1)
com.primavera.PhoenixException: DBEngine.executeStatement for {call ts_audit(?, ?, ?, ?, ?)}failed:Socket closed
  at com.primavera.bo.base.DBEngineImpl.executeStatement(DBEngineImpl.java:1969)
  at com.primavera.guisupport.timeapproval.TimesheetApprovalDataSaver.f(TimesheetApprovalDataSaver.java:457)
  at com.primavera.guisupport.timeapproval.TimesheetApprovalDataSaver.d(TimesheetApprovalDataSaver.java:165)
  at com.primavera.guisupport.timeapproval.TimesheetApprovalDataSaver.updateStore(TimesheetApprovalDataSaver.java:52)
  at com.primavera.rest.service.timesheetapproval.TimesheetApprovalDataHandler.saveData(TimesheetApprovalDataHandler.java:184)
  at com.primavera.rest.resources.timesheetapproval.TimesheetApprovalResource.saveData(TimesheetApprovalResource.java:107)
  at sun.reflect.GeneratedMethodAccessor833.invoke(Unknown Source)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
  at java.lang.reflect.Method.invoke(Method.java:498)
...
  at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:348)
  at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:333)
  at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:54)
  at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
  at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:640)
  at weblogic.work.ExecuteThread.execute(ExecuteThread.java:406)
  at weblogic.work.ExecuteThread.run(ExecuteThread.java:346)
  Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Socket closed

 

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

  1. Login to P6 Web as an admin-superuser.
  2. Navigate to Administration > Applications Settings > Timesheets.
  3. Select the Two approval levels - Project and Resource managers' approval required' and Enable timesheet auditing options, then click Save.
  4. Navigate to the Approvals tab.
  5. Upon approving a timesheet as either a Project Manager or Resource Manager, the page will take a long time to respond, requiring the user to refresh the page to see any updates.

Cause

To view full details, 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 a vibrant support community of peers and Oracle experts.