Interrupt from The Generator by "Slow down logging."

[#1]

Have you a answer to this problem. I have the trouble by the interfaces by the Reloadings from the Generator. Anaytime the Generator break up. Why can QlickView not start with Slow down logging. Log every <1200> seconds.

n: Reloading......

(2015-09-08 09:47:22) Information: Reloading.......

(2015-09-08 09:47:24) Information: Reloading........

(2015-09-08 09:47:26) Information: Reloading.........

(2015-09-08 09:47:28) Information: Reloading..........

(2015-09-08 09:47:30) Information: Slow down logging. Log every <10> seconds.

(2015-09-08 09:47:30) Information: Reloading

(2015-09-08 09:47:41) Information: Reloading.

(2015-09-08 09:47:51) Information: Reloading..

(2015-09-08 09:48:01) Information: Reloading...

(2015-09-08 09:48:12) Information: Reloading....

(2015-09-08 09:48:22) Information: Reloading.....

(2015-09-08 09:48:33) Information: Reloading......

(2015-09-08 09:48:43) Information: Reloading.......

(2015-09-08 09:48:53) Information: Reloading........

(2015-09-08 09:49:04) Information: Reloading.........

(2015-09-08 09:49:14) Information: Reloading..........

(2015-09-08 09:49:25) Information: Slow down logging. Log every <60> seconds.

(2015-09-08 09:49:25) Information: Reloading

(2015-09-08 09:50:27) Information: Reloading.

(2015-09-08 09:51:30) Information: Reloading..

(2015-09-08 09:52:32) Information: Reloading...

(2015-09-08 09:53:33) Information: Reloading....

(2015-09-08 09:54:34) Information: Reloading.....

(2015-09-08 09:55:34) Information: Reloading......

(2015-09-08 09:56:36) Information: Reloading.......

(2015-09-08 09:57:37) Information: Reloading........

(2015-09-08 09:58:38) Information: Reloading.........

(2015-09-08 09:59:38) Information: Reloading..........

(2015-09-08 10:00:38) Information: Slow down logging. Log every <300> seconds.

[marcus_sommer]

The server only tried to minimize the overhead with the extension from the logging-interval. I don't think that here is the problem for your long loadings and/or failures of loadings. I suggest that you looked at first to the log from the qvw to see what happens by the reload.

- Marcus

[#3]

The QlickView break it up, after one reload with 1200 seconds. The program could in my thinking not clear the storage after the reloads.

"

(2015-09-08 15:34:31) Information: Slow down logging. Log every <1200> seconds.

(2015-09-08 15:34:31) Information: Reloading

(2015-09-08 15:47:02) Warning: The QlikView Engine is Reloading, it will be killed (Please ignore logged warnings/errors about the kill).

(2015-09-08 15:47:02) Information: Killing the QlikView Engine. ProcessID=5340

(2015-09-08 15:47:02) Information: Reload was aborted.

(2015-09-08 15:47:04) Information: Killing a child process of the QlikView Engine. ProcessID=5620. ProcessName=qvconnect64

(2015-09-08 15:47:04) Information: Successfully killed a child process of the QlikView Engine. ProcessID=5340. ProcessName=qvb

(2015-09-08 15:47:05) Information: Closed the QlikView Engine successfully. ProcessID=5340

(2015-09-08 15:47:06) Error: The task "StsBi/eigene_generatoren_zum ändern/QVD_Generator_sales_6.qvw" failed. Exception: || QDSMain.Exceptions.TaskFailedException: Task execution failed with errors to follow. ---> QDSMain.Exceptions.ReloadFailedException: Reload failed ---> System.Threading.ThreadAbortException: Der Thread wurde abgebrochen. || bei System.Threading.WaitHandle.WaitOneNative(SafeHandle waitableSafeHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext) || bei System.Threading.WaitHandle.InternalWaitOne(SafeHandle waitableSafeHandle, Int64 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext) || bei SolutionGlobal.ThreadPool.ThreadPoolJob.SafeWaitEvent(WaitHandle eventWaitHandle) || bei QDSMain.ReloadTask.Reload(String fileName, TaskResult taskResult, String sectionAccessUserName, String sectionAccessPassword, eReloadOptions reloadOption, String variableName, String variableValue, Boolean moniterCpuUsage) || --- Ende der internen Ausnahmestapelüberwachung --- || bei QDSMain.ReloadTask.Reload(String fileName, TaskResult taskResult, String sectionAccessUserName, String sectionAccessPassword, eReloadOptions reloadOption, String variableName, String variableValue, Boolean moniterCpuUsage) || bei QDSMain.DistributeTask.Execute(TaskResult currentTaskResult) || --- Ende der internen Ausnahmestapelüberwachung --- || bei QDSMain.DistributeTask.Execute(TaskResult currentTaskResult) || bei QDSMain.Task.AbstractTask.TaskExecution(ILogBucket logBucket, TaskResult taskResult)

(2015-09-08 15:47:06) Error: Task failed with exception

(2015-09-08 15:47:06) Error: Exception=The currently executing operation was aborted.

(2015-09-08 15:47:06) Information: TaskResult.status=Finished

(2015-09-08 15:47:06) Information: Notifying all triggers of new state:FinishedWithErrors

(2015-09-08 15:47:06) Information: Notifying all triggers of new state:FinishedWithErrors - completed

(2015-09-08 15:47:06) Information: Saving Task Result"

[marcus_sommer]

I'm not a specialist in server-messages but I would interpret it that the task is run into a timeout maybe by waiting for a responce from a database-connection then qlikview and the child-process of qvconnect64 were killed (maybe the database is too slow or the network is bad).

What happens if you run this application with the fat-client?

- Marcus

[#5]

Hello everyone,

I got the same problem. QVW can reload without any problem. But publish goes forever.

The task keep running and cannot stop even restart the server machine.

Does anybody have suggestion?

Thank you very much in advance

[#6]

Hello!!

I got the same problem. And i need you'r help!!!!

3/2/2016 21:49:42.9090689 Information Reloading......

3/2/2016 22:04:43.6110171 Information Reloading.......

3/2/2016 22:19:44.3089315 Information Reloading........

3/2/2016 22:34:44.7340573 Information Reloading.........

3/2/2016 22:49:45.4980321 Information Reloading..........

3/2/2016 23:04:46.2342357 Information Slow down logging. Log every <1200> seconds.

3/2/2016 23:04:46.2342357 Information Reloading

3/2/2016 23:21:14.9076947 Warning The QlikView Engine is Reloading, it will be killed (Please ignore logged warnings/errors about the kill).

3/2/2016 23:21:14.9236955 Information Killing the QlikView Engine. ProcessID=7844

3/2/2016 23:21:14.9316799 Information Reload was aborted.

3/2/2016 23:21:15.5906776 Information Killing a child process of the QlikView Engine. ProcessID=7952. ProcessName=qvconnect64

3/2/2016 23:21:15.6926779 Information Successfully killed a child process of the QlikView Engine. ProcessID=7844. ProcessName=qvb

3/2/2016 23:21:15.7266857 Information Closed the QlikView Engine successfully. ProcessID=7844

3/2/2016 23:21:15.7376761 Error The task "Скоринг.qvw" failed. Exception: || QDSMain.Exceptions.TaskFailedException: Task execution failed with errors to follow. ---> QDSMain.Exceptions.ReloadFailedException: Reload failed ---> System.Threading.ThreadAbortException: Thread was being aborted. ||    at System.Threading.WaitHandle.WaitOneNative(SafeHandle waitableSafeHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext) ||    at System.Threading.WaitHandle.InternalWaitOne(SafeHandle waitableSafeHandle, Int64 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext) ||    at SolutionGlobal.ThreadPool.ThreadPoolJob.SafeWaitEvent(WaitHandle eventWaitHandle) ||    at QDSMain.ReloadTask.Reload(String fileName, TaskResult taskResult, String sectionAccessUserName, String sectionAccessPassword, eReloadOptions reloadOption, String variableName, String variableValue, Boolean moniterCpuUsage) ||    --- End of inner exception stack trace --- ||    at QDSMain.ReloadTask.Reload(String fileName, TaskResult taskResult, String sectionAccessUserName, String sectionAccessPassword, eReloadOptions reloadOption, String variableName, String variableValue, Boolean moniterCpuUsage) ||    at QDSMain.DistributeTask.Execute(TaskResult currentTaskResult) ||    --- End of inner exception stack trace --- ||    at QDSMain.DistributeTask.Execute(TaskResult currentTaskResult) ||    at QDSMain.Task.AbstractTask.TaskExecution(ILogBucket logBucket, TaskResult taskResult)

3/2/2016 23:21:15.7426895 Error Task failed with exception

3/2/2016 23:21:15.7426895 Error Exception=The currently executing operation was aborted.

3/2/2016 23:21:15.7466776 Information TaskResult.status=Finished

3/2/2016 23:21:15.7616893 Information Notifying all triggers of new state:FinishedWithErrors

3/2/2016 23:21:15.7616893 Information Notifying all triggers of new state:FinishedWithErrors - completed

3/2/2016 23:21:15.7666892 Information Saving Task Result

Thank you!

[rwunderlich]

This generally means that the task has exceeded the timeout limit for the task. If it should run longer, increase the timeout value in the Reload definition (or the trigger if using Publisher).

-Rob

[#8]

I increased the timeout,It did not help (((

[#9]

I had to solve the Problem with a better left outer join code(very short) in SQL. You could also try to make a view with your SQL join,.. This view could you also use for your Script in QlickView.

For example:

Items:
LOAD (pk_tenant & '_' & pk_id) AS item_row_id, 1 AS si_count, pk_id AS 'itemnumber',
pk_id as l_item_id,
text(code) AS si_code, (text(code) & ' ' & if(isNull(desc), si_searchname, desc)) AS si_bkey,
if(isNull(desc), si_searchname, desc) AS si_name,
si_searchname, si_trade_unit,
si_mixed_price, si_last_purchase_price, si_plan_price1, si_plan_price2,
si_production_costs, si_ig_desc, si_ig_searchname, si_rg_desc, si_rg_searchname,
i_procurement_type,
text(eclass) as eClass,
if(i_procurement_type = 'Fremdbeschaffung', si_last_purchase_price, si_production_costs) AS Kostenbasis_DB_Kalkulation_Hauswährung, // zieht EK oder HK an, je nach Artikel (fremdbeschafft/Eigenerzeugnis)
sseg as si_sseg;
SQL SELECT
i.pk_tenant  AS pk_tenant,
i.pk_id AS pk_id,
i.code AS code,
i.description AS desc,
i.eclass AS eclass,
i.searchname AS si_searchname,
i.trade_unit AS si_trade_unit,
i.mixed_price_domestic AS si_mixed_price,
i.last_purchase_price_domestic AS si_last_purchase_price,
i.plan_price1 AS si_plan_price1,
i.plan_price2  AS si_plan_price2,
i.production_costs AS si_production_costs,
i.procurement_type  AS i_procurement_type, // Fremdbeschaffung / Eigenerzeugnis zur Unterscheidung ob EK oder HK angezogen werden
i.sseg AS sseg,
ig.description AS si_ig_desc,
ig.searchname AS si_ig_searchname,
rg.description AS si_rg_desc,
rg.searchname AS si_rg_searchname


FROM dim_item i
LEFT JOIN dim_itemgroup ig ON i.item_group_id = ig.pk_id
LEFT JOIN dim_revenuegroup rg ON i.revenue_group_id = rg.pk_id 

For the table "dim_itemgroup ig" could you use a view.

I hope it help you.

[Nasar]

I am seeing seeing a similar issue for a task that was running fine for years. Suddenly since a week it is failing. The task logs continues as below, Doc log is not updated at all.

(2/13/2019 11:54:20 PM) Information: Slow down logging. Log every <60> seconds.

(2/13/2019 11:54:20 PM) Information: Reloading

(2/13/2019 11:55:20 PM) Information: Reloading.

(2/13/2019 11:56:20 PM) Information: Reloading..

(2/13/2019 11:57:20 PM) Information: Reloading...

(2/13/2019 11:58:20 PM) Information: Reloading....

(2/13/2019 11:59:20 PM) Information: Reloading.....

(2/14/2019 12:00:20 AM) Information: Reloading......

(2/14/2019 12:01:20 AM) Information: Reloading.......

(2/14/2019 12:02:20 AM) Information: Reloading........

(2/14/2019 12:03:20 AM) Information: Reloading.........

(2/14/2019 12:04:20 AM) Information: Reloading..........

(2/14/2019 12:05:20 AM) Information: Slow down logging. Log every <300> seconds.

(2/14/2019 12:05:20 AM) Information: Reloading

(2/14/2019 12:10:20 AM) Information: Reloading.

(2/14/2019 12:15:20 AM) Information: Reloading..

(2/14/2019 12:20:20 AM) Information: Reloading...

(2/14/2019 12:25:20 AM) Information: Reloading....

(2/14/2019 12:30:20 AM) Information: Reloading.....

(2/14/2019 12:35:20 AM) Information: Reloading......

(2/14/2019 12:40:20 AM) Information: Reloading.......

(2/14/2019 12:45:20 AM) Information: Reloading........

(2/14/2019 12:50:20 AM) Information: Reloading.........

(2/14/2019 12:55:20 AM) Information: Reloading..........