1. Community
  2. Errores
+2
No es un bug

Hangfire DB Issue or Suspend and Resume Tools Issue.

Hemant Chauhan hace 3 años • actualizado por Yogesh Rajpurohit hace 3 años • 3

Hello WareWolf Team, 

Warewolf Version : 2.6.3.28


Issue 1 ==> Timeout expired. The timeout elapsed prior to obtaining a distributed lock on the 'HangFire:HangfireScheduler.ResumeWorkflow' resource.

Please check attachment, workflow & below recording for Issue 1

https://theunlimited-my.sharepoint.com/personal/wynand_vermaak_theunlimited_co_za/_layouts/15/onedrive.aspx?id=%2Fpersonal%2Fwynand%5Fvermaak%5Ftheunlimited%5Fco%5Fza%2FDocuments%2FRecordings%2FCall%20with%20Hemant%20and%201%20other%2D20211006%5F115411%2DMeeting%20Recording%2Emp4&parent=%2Fpersonal%2Fwynand%5Fvermaak%5Ftheunlimited%5Fco%5Fza%2FDocum...

Issue1.PNG


SimUsageJourney.bite


Issue 2 ==> We are getting multiple "Processing" for [HangFire].[State]. Please check attachment with name "Issue2" for more detail.


Issue2.PNG


En revisión
Siphamandla Dube hace 3 años
No es un bug
Yogesh Rajpurohit hace 3 años
Yogesh Rajpurohit hace 3 años

We were not able to get data that could support the claim on multiple executions. The screen shared db during the meeting has information that support this not being a Bug as though the state my be recorded to be "Processing" a number of times this is to be expected given the bottleneck with the production setup. The timeout error is caused by the Sql Server lock.

Do also notice the job(s) shared with this meeting's recording that their states are Processing, Processing and Then Success the other is Processing multiple times and Then Failing which is indeed to be expected with tools of this kind. Below are images for your references.

Note : Keep monitor this issue if found anything to be handle from our side then reopen the issue again.

Servicio de atención al cliente por UserEcho