SQLMainDomLock throws exception on boot, causing boot to fail

[nzdev]

A brief description of the issue goes here.

SQLMainDomLock throws exception on boot, causing boot to fail

Can not get Current.Config during composition. Use composition.Config.

System.InvalidOperationException:
at Umbraco.Core.Composing.Current.get_Configs (Umbraco.Core, Version=8.0.0.0, Culture=neutral, PublicKeyToken=nullUmbraco.Core, Version=8.0.0.0, Culture=neutral, PublicKeyToken=null: D:\a\1\s\src\Umbraco.Core\Composing\Current.csUmbraco.Core, Version=8.0.0.0, Culture=neutral, PublicKeyToken=null: 138)
at Umbraco.Core.Persistence.SqlSyntax.SqlServerSyntaxProvider.WriteLock (Umbraco.Core, Version=8.0.0.0, Culture=neutral, PublicKeyToken=nullUmbraco.Core, Version=8.0.0.0, Culture=neutral, PublicKeyToken=null: D:\a\1\s\src\Umbraco.Core\Persistence\SqlSyntax\SqlServerSyntaxProvider.csUmbraco.Core, Version=8.0.0.0, Culture=neutral, PublicKeyToken=null: 271)
at Umbraco.Core.Runtime.SqlMainDomLock.AcquireWhenMaxWaitTimeElapsed (Umbraco.Core, Version=8.0.0.0, Culture=neutral, PublicKeyToken=nullUmbraco.Core, Version=8.0.0.0, Culture=neutral, PublicKeyToken=null: D:\a\1\s\src\Umbraco.Core\Runtime\SqlMainDomLock.csUmbraco.Core, Version=8.0.0.0, Culture=neutral, PublicKeyToken=null: 358)

Umbraco version

I am seeing this issue on Umbraco version: 8.12.1

Reproduction

If you're filing a bug, please describe how to reproduce it. Include as much
relevant information as possible, such as:

Bug summary

SQLMainDomLock throws exception on boot, causing boot to fail

Specifics

Steps to reproduce

Configure SQLMainDomLock to be used

Expected result

umbraco boots

Actual result

Umbraco does not boot, throws invalidoperationexception then timeoutexception

Umbraco.Core.Exceptions.BootFailedException:
System.TimeoutException:
at Umbraco.Core.Runtime.MainDom.Acquire (Umbraco.Core, Version=8.0.0.0, Culture=neutral, PublicKeyToken=nullUmbraco.Core, Version=8.0.0.0, Culture=neutral, PublicKeyToken=null: D:\a\1\s\src\Umbraco.Core\Runtime\MainDom.csUmbraco.Core, Version=8.0.0.0, Culture=neutral, PublicKeyToken=null: 172)
at System.Threading.LazyInitializer.EnsureInitializedCore (mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089)
at Umbraco.Core.Runtime.MainDom.get_IsMainDom (Umbraco.Core, Version=8.0.0.0, Culture=neutral, PublicKeyToken=nullUmbraco.Core, Version=8.0.0.0, Culture=neutral, PublicKeyToken=null: D:\a\1\s\src\Umbraco.Core\Runtime\MainDom.csUmbraco.Core, Version=8.0.0.0, Culture=neutral, PublicKeyToken=null: 204)
at Umbraco.Core.Runtime.CoreRuntime.AcquireMainDom (Umbraco.Core, Version=8.0.0.0, Culture=neutral, PublicKeyToken=nullUmbraco.Core, Version=8.0.0.0, Culture=neutral, PublicKeyToken=null: D:\a\1\s\src\Umbraco.Core\Runtime\CoreRuntime.csUmbraco.Core, Version=8.0.0.0, Culture=neutral, PublicKeyToken=null: 348)
at Umbraco.Core.Runtime.CoreRuntime.Boot (Umbraco.Core, Version=8.0.0.0, Culture=neutral, PublicKeyToken=nullUmbraco.Core, Version=8.0.0.0, Culture=neutral, PublicKeyToken=null: D:\a\1\s\src\Umbraco.Core\Runtime\CoreRuntime.csUmbraco.Core, Version=8.0.0.0, Culture=neutral, PublicKeyToken=null: 176)

[Shazwazza]

This should have been fixed here: #9973

you are definitely on 8.12.1?

@bergmania + @nul800sebastiaan was that change definitely merged and released in 8.12.1 ?

[nzdev]

I may be on 12.0. I'll double check

[nzdev]

Yes. 8.12.0. I'll upgrade and try again. Thanks

[nzdev]

Looks to have fixed this. Thanks @Shazwazza