NPrinting Leaves Open Sessions In QlikView

[lgtsotrsdh]

Hi,

NPrinting is currently leaving a lots of open sessions in QlikView even after it hasn't used the document for hours. These sessions can be viewed in the QVS Statistics view in the QMC. A restart of the service on the Document Server clears all these sessions. Can this be done without restarting the service and kicking out all users?

I'm using QlikView May 2023 and NPrinting May 2023 SR1.

Thanks,

Scott

[Frank_S]

Hi @lgtsotrsdh 

Please see this article at your convenience.

https://community.qlik.com/t5/Official-Support-Articles/How-does-Nprinting-Handle-Multiple-Concurren...

You may notice QlikView processes remain in memory. This is done by design to enable NPrinting to reuse open sessions in case the QVWs are used again for additional reporting. Thus speedier results on subsequent tasks. If new tasks are started that utilize different QVWs, then the NP scheduler service will close the open sessions and start new sessions.

Kind regards...

[lgtsotrsdh]

Interesting. This is a process that sends publish requests using the same document over and over using different filters and the executions overlap so it sounds like this could be helpful. Any recommendations on what to do about it?

Thanks for the response.

Scott

[Lech_Miszkiewicz]

you can read this: https://community.qlik.com/t5/Official-Support-Articles/How-to-remove-the-Idle-Connections-from-Npri...

cheers

[lgtsotrsdh]

Thanks but I already applied that last week. It successfully removed all the idle connections that I can see using the NPrinting admin/plan link.

These are connections to the document server that I can view through the QMC. I don't know if there's anywhere else they can be viewed. Appreciate the response though. It took some serious searching to find that article last week.

For the record, I also applied this solution last week:

https://community.qlik.com/t5/Official-Support-Articles/Force-Qlik-NPrinting-to-automatically-close-...

It successfully killed the sessions on the NPrinting servers where the engines are running. Still the connections to the document server persist.

[David_Friend]

@lgtsotrsdh are you seeing any adverse behavior as a result