EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB440291: Timeout settings from application.properties file in the PDFExportService folder is not being applied in MicroStrategy 10.9


Community Admin

• Strategy


This issue has been classified as a defect by MicroStrategy. The impact is limited to timeout settings change in application.properties file in MicroStrategy 10.9. A workaround and code fix for this issue is available in current releases.

Starting with the release of Strategy ONE (March 2024), dossiers are also known as dashboards.
SYMPTOM:
 
In Strategy 10.9, make changes to the timeout settings from application.properties file in the PDFExportService folder is not being applied.
 
REPRODUCING STEPS IN TUTORIAL:

  1. Open the application.properties file in the PDFExportService folder (located in <MSTR_HOME_PATH>/IntelligenceServer/PDFExportService)
  2. Set the following timeout settings to something different than the default 60 seconds:

exporter.phantoms.rendering.timeout=... 
exporter.phantoms.resource.timeout=...
       3.  Restart the PDFExportService
       4.  Try to export a very large document or Dossier so the timeout is hit
       5.  Notice theNewExportEngine.log still shows Request timeout: 60 seconds
 
Refer to Technical Document below on how to restart PDFExporterService:
How to Change port number of New Export Engine and restart New Export Engine in Strategy 10.6
  
CAUSE:
 
This is a known issue with Strategy 10.9.
 
A typo in the application.properties file in the PDFExportService folder prevents the timeout settings to be applied.
 
The typo is in the following lines:
exporter.phantoms.rendering.timeout=... 
exporter.phantoms.resource.timeout=... 
This is wrong and should be renamed to: 
exporter.phantomjs.rendering.timeout=... 
exporter.phantomjs.resource.timeout=...
 
ACTION:
 
The issue has been fixed in 10.11. Upgrade to this version to take advantage of the fix.
 
WORKAROUND:
renamed the problematic lines to:
exporter.phantomjs.rendering.timeout=...
exporter.phantomjs.resource.timeout=...
 
 
Article Reference Number: KB440291 KB440291


Comment

0 comments

Details

Knowledge Article

Published:

March 24, 2018

Last Updated:

March 21, 2024