0 Replies Latest reply: Feb 13, 2015 3:49 PM by Pooja Chadha RSS

    Modified the setting to allocate 4 QlikView Engines but the some of the logs still show 2 engines.

      Summary of the Issue

      --------------------------------------

      We  recently Increased the "Max Concurrent Reloads" setting for the server within QMC from 2 to 4 (in order to allow 4 parallel tasks to run together) and noticed logging anomalies during the qlikview refreshes. This change is not being reflected correctly in task logs in QMC. We are concerned, since If 4 qlikview engines are not being used for all tasks it would cause production failures.

       

      Explanation of the Issue

      --------------------------------------

      The production Log from QMC for our tasks shows "Current usage count=0 of 4 " for some tasks, but "Current usage count=0 of 2" for other tasks. Since this is a server setting change, we expected all task logs to show "...of 4" in its logs. 

       

      We do not think this is application specific, or even related to the caching/memory (which are factors we thought of, initially), because, the same task shows "...of 4" in the log for yesterday's run, which shows "...of 2" in today's log - Example below:


      "2015-02-11 20:18:31) Information: Document is marked to be Reloaded with fresh data. Initializing Reload for Distribution.

      (2015-02-11 20:18:31) Information: Opening "E:\qlikview_storage\xxxx.qvw"

      (2015-02-11 20:18:31) Information: Allocating new QlikView Engine. Current usage count=1 of 4 (of type non-reader).

      (2015-02-11 20:18:31) Information: Max retries:5"

       

      "2015-02-12 20:20:35) Information: Document is marked to be Reloaded with fresh data. Initializing Reload for Distribution.

      (2015-02-12 20:20:35) Information: Opening "E:\qlikview_storage\xxxx.qvw"

      (2015-02-12 20:20:35) Information: Allocating new QlikView Engine. Current usage count=1 of 2 (of type non-reader).

      (2015-02-12 20:20:35) Information: Max retries:5"

       

      If it were a Qlik logging bug, I would imagine other environments to have had this issue as well. However I have only observed this in one environment of ours and not the other.

       

      Are there things to check for, in QVPR, or other logs/data to find differences between environments or reasons for this strange logging?

       

      Has anyone else experienced this before?

       

      Your help is much appreciated! Thank you!