Cloned Services are always using 'App' webserverinstance Entry URL for Performing Playwright PDF export
search cancel

Cloned Services are always using 'App' webserverinstance Entry URL for Performing Playwright PDF export

book

Article ID: 242807

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

The customer has cloned the App Server to have the ability to generate status reports in mixed environments where they have SSO on one app service and use another app service for admin work. Errors in the log file indicate the action is not retrieving the correct entryURL. 

Steps to Reproduce: 

  1. Install Clarity 16.0.1 or 16.0.2
  2. Configure that app service is running on Port 80 and then Entry URL for App service is "http://hostname"
  3. Clone the app service which creates and app2 service on port 81. Modify the entry URL of app2 service to "http://hostname:81"
  4. Modify the Entry URL of APP service to http://<not-working-hostname> which the server can't resolve
  5. Login to App2 service on port 81 
  6. Navigate to New UX -> Projects -> Status and click on Preview 

Expected Results: The Export to PDF Preview is successful. 

Actual Results: The Export to PDF Preview failed with the error: EXP - 01000: Error exporting PDF with below error stack 

Caused by: com.microsoft.playwright.impl.DriverException: Error {
  message='net::ERR_CONNECTION_TIMED_OUT at http://<not-working-hostname>/pm/#/project/6642570/status/5652001?print=true
=========================== logs ===========================
navigating to "http://<not-working-hostname>/pm/#/project/6642570/status/5652001?print=true", waiting until "load"
============================================================
  name='Error
  stack='Error: net::ERR_CONNECTION_TIMED_OUT at http://<not-working-hostname>/pm/#/project/6642570/status/5652001?print=true
=========================== logs ===========================
navigating to "http://<not-working-hostname>/pm/#/project/6642570/status/5652001?print=true", waiting until "load"
============================================================
    at FrameSession._navigate (E:\App\Clarity\tomcat-app2-deploy\temp\playwright-java-13666345770721772647\package\lib\server\chromium\crPage.js:599:35)
    at async E:\App\Clarity\tomcat-app2-deploy\temp\playwright-java-13666345770721772647\package\lib\server\frames.js:622:30
    at async ProgressController.run (E:\App\Clarity\tomcat-app2-deploy\temp\playwright-java-13666345770721772647\package\lib\server\progress.js:89:22)
    at async FrameDispatcher.goto (E:\App\Clarity\tomcat-app2-deploy\temp\playwright-java-13666345770721772647\package\lib\dispatchers\frameDispatcher.js:79:59)
    at async DispatcherConnection.dispatch (E:\App\Clarity\tomcat-app2-deploy\temp\playwright-java-13666345770721772647\package\lib\dispatchers\dispatcher.js:330:22)

Environment

Release: 16.0.1, 16.0.2 

Cause

DE65005 

Resolution

Fixed in Release 16.0.3