Error after upgrade to 7.3.3

Questions
1

After upgrade to 7.3.3 we see this error in log every 5th second:

2020-03-21 21:14:24.5637 [App:02] [c355ad01-1cb4-433e-b1cd-a62833fa97da] [ERROR] [] Litium.Application.Scheduler.BackgroundJobEngine - Execution of background processor Litium.Application.Scheduler.BackgroundJobWorker, Litium.Application failed, executing again in 5 seconds. System.NullReferenceException: Object reference not set to an instance of an object.
   at Litium.Application.Scheduler.BackgroundJobQueue.<ReceiveAsync>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Litium.Application.Scheduler.BackgroundJobWorker.<ExecuteAsync>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Litium.Application.Scheduler.BackgroundJobEngine.InfiniteRetryBackgroundProcess.<ExecuteAsync>d__3.MoveNext()

Any idea why we are getting this error?

Litium version: 7.3.3-patch-2003180843

2

Please, see https://docs.litium.com/support/bugs/bug_details?id=49525

3

Ok, thanks. Will the error affect the “new” application?

4

The error will not affect the new application, only the old one. In this case when we talk about app domain starts in the application pool.

If we check the log we have rows that starts in this way

2020-03-24 10:06:15.9354 [App:04] [b6581d4c-7c72-48b3-b751-fa5ef939dada] [INFO ]

where the [App:04] tells that is the 3 times the app domain have started (first add domain always get App:02 as name) and then the number is increment for each start and all log-rows that have the same app-number will be in the same context, if they are in different app they are executed independent of each other and is not related.

I have publish a new version of the pre-release that will (finger crossed) handle this in a graceful way without logging the error.

5

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.