Description of NPrinting Resolver behavior:
Description of Property "force-unused-resolvers-closure-policy"
- On the NP Server add a setting to a scheduler.config file that will force closure of the internal connections (qv.exe processes) once they have become idle.
- Forcing resolver closures may be useful if engine machines have low RAM capability and/or in case of NP connections to Large* Qlik Applications.
- "0" is Default Value/Default NPrinting Behavior: a resolver will be closed only if it is the best option based on current load and what the internal algorithm determines
- "1" force closure of all open resolvers: when the system does not have open execution requests upon them
- "2" force closure of idle connections: if the connection is used occasionally - weekly, monthly, yearly etc. vs connections that a used with reports that run on a schedule trigger daily or hourly.
- This policy may only be applied to NPrinting June 2018 or higher. Attempt to add this key/policy in earlier versions of NPrinting may cause system instability.
*NOTE: The term 'Large' is relative to the amount of RAM on your NP server. If low Ram like 64 or 128 GB RAM, then 1 GB QVW is 'large' since it may grow as large as 10 GB in memory. Then if you have 8 cores, it will open 16 processes each potentially with 10 GB each since NPrinting will use every core process by default to generate a single report. (https://help.qlik.com/en-US/nprinting/February2019/Content/NPrinting/DeployingQVNprinting/Performance.htm)
NOTE: Please ensure to back up the scheduler.config file before proceeding
- Stop the NPrinting services on the NPrinting Server. Please stop all NP engines if installed on different server computers.
- Make a copy of "C:\Program Files\NPrintingServer\NPrinting\Scheduler\scheduler.config"
- Launch Notepad as an admin and edit "C:\Program Files\NPrintingServer\NPrinting\Scheduler\scheduler.config"
- Add the following key:
<add key="force-unused-resolvers-closure-policy" value="1" />
right before the final </appSettings> line
- Save the file and restart all the NP services.
- Please restart all NP engines if installed on different server computers.
: Config file changes are overwritten upon upgrading NPrinting. Please apply these changes again after upgrading if the issues persist.