Activities of "cellero"

All Question Answer
Newest Oldest
CRITICAL: Blazor Server Circuit ObjectDisposedException causing application crashes with LeptonX Theme #10283
Answer

Thank you. I will give that a try.

CRITICAL: Blazor Server Circuit ObjectDisposedException causing application crashes with LeptonX Theme #10283
Answer

AI assessment of the full log file is:

Root Cause Analysis Primary Issue: ObjectDisposedException - Autofac LifetimeScope has been disposed while components are still trying to resolve dependencies. Trigger Point: The exceptions originate from ABP Framework's LeptonX Theme components (Breadcrumbs and ContentToolbar) during their initialization phase, specifically in property change event handlers that trigger StateHasChanged(). Key Problem Pattern The crash follows this sequence:

  1. PropertyChanged event fires in Breadcrumbs.<OnInitializedAsync>b__8_1 and ContentToolbar.<OnInitializedAsync>b__7_1
  2. StateHasChanged() is called, triggering a re-render
  3. Syncfusion components try to instantiate via SfComponentActivator.CreateInstance()
  4. Autofac attempts resolution from a disposed LifetimeScope
  5. Fatal exception - Application terminates (IsTerminating: true) Likely Causes
  6. Component lifecycle mismatch: Layout components are subscribing to events but not properly unsubscribing, causing events to fire after their scope is disposed
  7. Asynchronous rendering race condition: Navigation or circuit disposal happening while async initialization is still in progress
  8. Syncfusion + Autofac integration issue: Custom activator attempting to resolve from incorrect scope
CRITICAL: Blazor Server Circuit ObjectDisposedException causing application crashes with LeptonX Theme #10283
Answer

Here is a snippet of the log file when the crash occurs. See the actvitiy before the [FTL] FATAL event. But I think it would be better to email the full log file for a better picture. I've pasted the max allowed.

  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.InitializeNewSubtree(DiffContext& diffContext, Int32 frameIndex)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.InsertNewFrame(DiffContext& diffContext, Int32 newFrameIndex)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForRange(DiffContext& diffContext, Int32 oldStartIndex, Int32 oldEndIndexExcl, Int32 newStartIndex, Int32 newEndIndexExcl)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForFramesWithSameSequence(DiffContext& diffContext, Int32 oldFrameIndex, Int32 newFrameIndex)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForRange(DiffContext& diffContext, Int32 oldStartIndex, Int32 oldEndIndexExcl, Int32 newStartIndex, Int32 newEndIndexExcl)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForFramesWithSameSequence(DiffContext& diffContext, Int32 oldFrameIndex, Int32 newFrameIndex)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForRange(DiffContext& diffContext, Int32 oldStartIndex, Int32 oldEndIndexExcl, Int32 newStartIndex, Int32 newEndIndexExcl)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForFramesWithSameSequence(DiffContext& diffContext, Int32 oldFrameIndex, Int32 newFrameIndex)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForRange(DiffContext& diffContext, Int32 oldStartIndex, Int32 oldEndIndexExcl, Int32 newStartIndex, Int32 newEndIndexExcl)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.ComputeDiff(Renderer renderer, RenderBatchBuilder batchBuilder, Int32 componentId, ArrayRange`1 oldTree, ArrayRange`1 newTree)
  at Microsoft.AspNetCore.Components.Rendering.ComponentState.RenderIntoBatch(RenderBatchBuilder batchBuilder, RenderFragment renderFragment, Exception& renderFragmentException)
  at Microsoft.AspNetCore.Components.RenderTree.Renderer.ProcessRenderQueue()
--- End of stack trace from previous location ---
  at Microsoft.AspNetCore.Components.RenderTree.Renderer.ProcessRenderQueue()
  at Microsoft.AspNetCore.Components.RenderTree.Renderer.AddToRenderQueue(Int32 componentId, RenderFragment renderFragment)
  at Microsoft.AspNetCore.Components.ComponentBase.StateHasChanged()
  at Microsoft.AspNetCore.Components.Rendering.RendererSynchronizationContext.<InvokeAsync>g__Execute|8_0(ValueTuple`3 state)
--- End of stack trace from previous location ---
  at Volo.Abp.AspNetCore.Components.Web.LeptonXTheme.Components.ApplicationLayout.Common.ContentToolbar.&lt;OnInitializedAsync&gt;b__7_1(Object s, PropertyChangedEventArgs e)
  at System.Threading.Tasks.Task.&lt;&gt;c.&lt;ThrowAsync&gt;b__128_1(Object state)
  at System.Threading.QueueUserWorkItemCallback.Execute()
  at System.Threading.ThreadPoolWorkQueue.Dispatch()
  at System.Threading.PortableThreadPool.WorkerThread.WorkerThreadStart()
2026-01-13 10:08:43.379 +11:00 [FTL] FATAL: Unhandled exception in AppDomain. IsTerminating: true
System.ObjectDisposedException: Instances cannot be resolved and nested lifetimes cannot be created from this LifetimeScope as it (or one of its parent scopes) has already been disposed.
  at Autofac.Core.Lifetime.LifetimeScope.ThrowDisposedException()
  at Autofac.Core.Lifetime.LifetimeScope.ResolveComponent(ResolveRequest& request)
  at Autofac.ResolutionExtensions.TryResolveService(IComponentContext context, Service service, IEnumerable`1 parameters, Object& instance)
  at Autofac.ResolutionExtensions.ResolveOptionalService(IComponentContext context, Service service, IEnumerable`1 parameters)
  at Syncfusion.Blazor.SfComponentActivator.CreateInstance(Type componentType)
  at Microsoft.AspNetCore.Components.ComponentFactory.InstantiateComponent(IServiceProvider serviceProvider, Type componentType, IComponentRenderMode callerSpecifiedRenderMode, Nullable`1 parentComponentId)
  at Microsoft.AspNetCore.Components.RenderTree.Renderer.InstantiateChildComponentOnFrame(RenderTreeFrame[] frames, Int32 frameIndex, Int32 parentComponentId)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.InitializeNewComponentFrame(DiffContext& diffContext, Int32 frameIndex)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.InitializeNewSubtree(DiffContext& diffContext, Int32 frameIndex)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.InsertNewFrame(DiffContext& diffContext, Int32 newFrameIndex)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForRange(DiffContext& diffContext, Int32 oldStartIndex, Int32 oldEndIndexExcl, Int32 newStartIndex, Int32 newEndIndexExcl)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForFramesWithSameSequence(DiffContext& diffContext, Int32 oldFrameIndex, Int32 newFrameIndex)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForRange(DiffContext& diffContext, Int32 oldStartIndex, Int32 oldEndIndexExcl, Int32 newStartIndex, Int32 newEndIndexExcl)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForFramesWithSameSequence(DiffContext& diffContext, Int32 oldFrameIndex, Int32 newFrameIndex)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForRange(DiffContext& diffContext, Int32 oldStartIndex, Int32 oldEndIndexExcl, Int32 newStartIndex, Int32 newEndIndexExcl)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForFramesWithSameSequence(DiffContext& diffContext, Int32 oldFrameIndex, Int32 newFrameIndex)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForRange(DiffContext& diffContext, Int32 oldStartIndex, Int32 oldEndIndexExcl, Int32 newStartIndex, Int32 newEndIndexExcl)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.ComputeDiff(Renderer renderer, RenderBatchBuilder batchBuilder, Int32 componentId, ArrayRange`1 oldTree, ArrayRange`1 newTree)
  at Microsoft.AspNetCore.Components.Rendering.ComponentState.RenderIntoBatch(RenderBatchBuilder batchBuilder, RenderFragment renderFragment, Exception& renderFragmentException)
  at Microsoft.AspNetCore.Components.RenderTree.Renderer.ProcessRenderQueue()
--- End of stack trace from previous location ---
  at Microsoft.AspNetCore.Components.RenderTree.Renderer.ProcessRenderQueue()
  at Microsoft.AspNetCore.Components.RenderTree.Renderer.AddToRenderQueue(Int32 componentId, RenderFragment renderFragment)
  at Microsoft.AspNetCore.Components.ComponentBase.StateHasChanged()
  at Microsoft.AspNetCore.Components.Rendering.RendererSynchronizationContext.<InvokeAsync>g__Execute|8_0(ValueTuple`3 state)
--- End of stack trace from previous location ---
  at Volo.Abp.AspNetCore.Components.Web.LeptonXTheme.Components.ApplicationLayout.Common.Breadcrumbs.&lt;OnInitializedAsync&gt;b__8_1(Object s, PropertyChangedEventArgs e)
  at System.Threading.Tasks.Task.&lt;&gt;c.&lt;ThrowAsync&gt;b__128_1(Object state)
  at System.Threading.QueueUserWorkItemCallback.Execute()
  at System.Threading.ThreadPoolWorkQueue.Dispatch()
  at System.Threading.PortableThreadPool.WorkerThread.WorkerThreadStart()
2026-01-13 10:08:43.379 +11:00 [FTL] FATAL: Unhandled exception in AppDomain. IsTerminating: true
System.ObjectDisposedException: Instances cannot be resolved and nested lifetimes cannot be created from this LifetimeScope as it (or one of its parent scopes) has already been disposed.
  at Autofac.Core.Lifetime.LifetimeScope.ThrowDisposedException()
  at Autofac.Core.Lifetime.LifetimeScope.ResolveComponent(ResolveRequest& request)
  at Autofac.ResolutionExtensions.TryResolveService(IComponentContext context, Service service, IEnumerable`1 parameters, Object& instance)
  at Autofac.ResolutionExtensions.ResolveOptionalService(IComponentContext context, Service service, IEnumerable`1 parameters)
  at Syncfusion.Blazor.SfComponentActivator.CreateInstance(Type componentType)
  at Microsoft.AspNetCore.Components.ComponentFactory.InstantiateComponent(IServiceProvider serviceProvider, Type componentType, IComponentRenderMode callerSpecifiedRenderMode, Nullable`1 parentComponentId)
  at Microsoft.AspNetCore.Components.RenderTree.Renderer.InstantiateChildComponentOnFrame(RenderTreeFrame[] frames, Int32 frameIndex, Int32 parentComponentId)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.InitializeNewComponentFrame(DiffContext& diffContext, Int32 frameIndex)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.InitializeNewSubtree(DiffContext& diffContext, Int32 frameIndex)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.InsertNewFrame(DiffContext& diffContext, Int32 newFrameIndex)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForRange(DiffContext& diffContext, Int32 oldStartIndex, Int32 oldEndIndexExcl, Int32 newStartIndex, Int32 newEndIndexExcl)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForFramesWithSameSequence(DiffContext& diffContext, Int32 oldFrameIndex, Int32 newFrameIndex)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForRange(DiffContext& diffContext, Int32 oldStartIndex, Int32 oldEndIndexExcl, Int32 newStartIndex, Int32 newEndIndexExcl)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForFramesWithSameSequence(DiffContext& diffContext, Int32 oldFrameIndex, Int32 newFrameIndex)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForRange(DiffContext& diffContext, Int32 oldStartIndex, Int32 oldEndIndexExcl, Int32 newStartIndex, Int32 newEndIndexExcl)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForFramesWithSameSequence(DiffContext& diffContext, Int32 oldFrameIndex, Int32 newFrameIndex)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForRange(DiffContext& diffContext, Int32 oldStartIndex, Int32 oldEndIndexExcl, Int32 newStartIndex, Int32 newEndIndexExcl)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.ComputeDiff(Renderer renderer, RenderBatchBuilder batchBuilder, Int32 componentId, ArrayRange`1 oldTree, ArrayRange`1 newTree)
  at Microsoft.AspNetCore.Components.Rendering.ComponentState.RenderIntoBatch(RenderBatchBuilder batchBuilder, RenderFragment renderFragment, Exception& renderFragmentException)
  at Microsoft.AspNetCore.Components.RenderTree.Renderer.ProcessRenderQueue()
--- End of stack trace from previous location ---
  at Microsoft.AspNetCore.Components.RenderTree.Renderer.ProcessRenderQueue()
  at Microsoft.AspNetCore.Components.RenderTree.Renderer.AddToRenderQueue(Int32 componentId, RenderFragment renderFragment)
  at Microsoft.AspNetCore.Components.ComponentBase.StateHasChanged()
  at Microsoft.AspNetCore.Components.Rendering.RendererSynchronizationContext.<InvokeAsync>g__Execute|8_0(ValueTuple`3 state)
--- End of stack trace from previous location ---
  at Volo.Abp.AspNetCore.Components.Web.LeptonXTheme.Components.ApplicationLayout.Common.ContentToolbar.&lt;OnInitializedAsync&gt;b__7_1(Object s, PropertyChangedEventArgs e)
  at System.Threading.Tasks.Task.&lt;&gt;c.&lt;ThrowAsync&gt;b__128_1(Object state)
  at System.Threading.QueueUserWorkItemCallback.Execute()
  at System.Threading.ThreadPoolWorkQueue.Dispatch()
  at System.Threading.PortableThreadPool.WorkerThread.WorkerThreadStart()
2026-01-13 10:08:43.379 +11:00 [FTL] FATAL: Unhandled exception in AppDomain. IsTerminating: true
System.ObjectDisposedException: Instances cannot be resolved and nested lifetimes cannot be created from this LifetimeScope as it (or one of its parent scopes) has already been disposed.
  at Autofac.Core.Lifetime.LifetimeScope.ThrowDisposedException()
  at Autofac.Core.Lifetime.LifetimeScope.ResolveComponent(ResolveRequest& request)
  at Autofac.ResolutionExtensions.TryResolveService(IComponentContext context, Service service, IEnumerable`1 parameters, Object& instance)
  at Autofac.ResolutionExtensions.ResolveOptionalService(IComponentContext context, Service service, IEnumerable`1 parameters)
  at Syncfusion.Blazor.SfComponentActivator.CreateInstance(Type componentType)
  at Microsoft.AspNetCore.Components.ComponentFactory.InstantiateComponent(IServiceProvider serviceProvider, Type componentType, IComponentRenderMode callerSpecifiedRenderMode, Nullable`1 parentComponentId)
  at Microsoft.AspNetCore.Components.RenderTree.Renderer.InstantiateChildComponentOnFrame(RenderTreeFrame[] frames, Int32 frameIndex, Int32 parentComponentId)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.InitializeNewComponentFrame(DiffContext& diffContext, Int32 frameIndex)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.InitializeNewSubtree(DiffContext& diffContext, Int32 frameIndex)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.InsertNewFrame(DiffContext& diffContext, Int32 newFrameIndex)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForRange(DiffContext& diffContext, Int32 oldStartIndex, Int32 oldEndIndexExcl, Int32 newStartIndex, Int32 newEndIndexExcl)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForFramesWithSameSequence(DiffContext& diffContext, Int32 oldFrameIndex, Int32 newFrameIndex)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForRange(DiffContext& diffContext, Int32 oldStartIndex, Int32 oldEndIndexExcl, Int32 newStartIndex, Int32 newEndIndexExcl)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForFramesWithSameSequence(DiffContext& diffContext, Int32 oldFrameIndex, Int32 newFrameIndex)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForRange(DiffContext& diffContext, Int32 oldStartIndex, Int32 oldEndIndexExcl, Int32 newStartIndex, Int32 newEndIndexExcl)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForFramesWithSameSequence(DiffContext& diffContext, Int32 oldFrameIndex, Int32 newFrameIndex)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.AppendDiffEntriesForRange(DiffContext& diffContext, Int32 oldStartIndex, Int32 oldEndIndexExcl, Int32 newStartIndex, Int32 newEndIndexExcl)
  at Microsoft.AspNetCore.Components.RenderTree.RenderTreeDiffBuilder.ComputeDiff(Renderer renderer, RenderBatchBuilder batchBuilder, Int32 componentId, ArrayRange`1 oldTree, ArrayRange`1 newTree)
  at Microsoft.AspNetCore.Components.Rendering.ComponentState.RenderIntoBatch(RenderBatchBuilder batchBuilder, RenderFragment renderFragment, Exception& renderFragmentException)
  at Microsoft.AspNetCore.Components.RenderTree.Renderer.ProcessRenderQueue()
--- End of stack trace from previous location ---
  at Microsoft.AspNetCore.Components.RenderTree.Renderer.ProcessRenderQueue()
  at Microsoft.AspNetCore.Components.RenderTree.Renderer.AddToRenderQueue(Int32 componentId, RenderFragment renderFragment)
  at Microsoft.AspNetCore.Components.ComponentBase.StateHasChanged()
  at Microsoft.AspNetCore.Components.Rendering.RendererSynchronizationContext.<InvokeAsync>g__Execute|8_0(ValueTuple`3 state)
--- End of stack trace from previous location ---
  at Volo.Abp.AspNetCore.Components.Web.LeptonXTheme.Components.ApplicationLayout.Common.ContentToolbar.&lt;OnInitializedAsync&gt;b__7_1(Object s, PropertyChangedEventArgs e)
  at System.Threading.Tasks.Task.&lt;&gt;c.&lt;ThrowAsync&gt;b__128_1(Object state)
  at System.Threading.QueueUserWorkItemCallback.Execute()
  at System.Threading.ThreadPoolWorkQueue.Dispatch()
  at System.Threading.PortableThreadPool.WorkerThread.WorkerThreadStart()
CRITICAL: Blazor Server Circuit ObjectDisposedException causing application crashes with LeptonX Theme #10283
Answer

On further investigation it seems it may be related to the Syncfusion Blazor Grid and Kanban components we are using. I will log a ticket with Syncfusion to see if it is a known issue for them.

CRITICAL: Blazor Server Circuit ObjectDisposedException causing application crashes with LeptonX Theme #10283
Answer

We have reviewed support cases #6280 and #5289 which describe identical issues. We've implemented the recommended workarounds: • Increased DisconnectedCircuitRetentionPeriod to 30 minutes • Increased DisconnectedCircuitMaxRetained to 1000 • Added circuit handler with ObjectDisposedException catching • Increased Hub timeout intervals However, our application is still experiencing fatal crashes (application process termination with IsTerminating: true). The exceptions are occurring on background threads from LeptonX theme component event handlers, NOT in the circuit inbound activity pipeline. Specific question: Are there any updates or patches since cases #6280 and #5289 were closed? Our crash pattern suggests the issue extends beyond what the circuit handler can catch.

Returning User 403 - Forbidden: Access is denied. #9753
Answer

Ok, the database size issue has been sorted.
Can you log in then log out to experience the 403 - Forbidden: Access is denied.

Thanks!

Returning User 403 - Forbidden: Access is denied. #9753
Answer

Can you expand on the suggested Ensure Claims/Permissions Are Refreshed: Where should this code go?

I can replicate this each time I choose logout from the top right menu:

unregistered version of Eziriz's ".NET Reactor"! #8990
Answer

Hi everyone,

We sincerely apologize for the issue caused by the recent release with a 3rd party component. The affected versions are 9.0.7 and 9.1.0, other versions don't have any issue. We understand how frustrating it is, especially when it affects live systems. The ABP project, like other software solutions, includes many 3rd party components, and sometimes there may be problems with them. We contacted our 3rd party vendor and completely fixed the case.

The issue is now resolved, and here's the quick fix:

  1. Run this command on your development computer to clear your local NuGet cache:
    dotnet nuget locals all --clear

  2. Uninstall and install ABP Suite again:
    abp suite remove
    abp suite install

  3. Rebuild your ABP solution and publish it again to your live environment

Thank you for your patience, and we truly appreciate the feedback. We're taking extra measures to prevent this in future releases.

– ABP Team

I'm sorry, that is not an explanation of what went wrong, and gives us no reassurance that it won't happen again.

We have customers that cannot tolerate an outage like this, and saying "someone else will fix it in the next day" is NOT an acceptable answer. Being may time zones away that means we are effectively shutting down their business for at least a day.

We put a LOT of effort into creating an offline build so that we are not affected by a temporary outage of any NuGet servers, but this problem stopped logins in code that was already functional and deployed. That means that 1 of 2 things happened, both of which are unacceptable:

  1. A component in our compiled code is reaching out to a server live to determine if it is allowed to run
  2. A license code embedded in our dependencies has an expiration date that we do not know about

We need to answer our organizations with a specific cause for this outage, or we will be forced to abandon ABP entirely (which we do not want to do).

Well said. I 100% agree. I am watching this space for ABP to acknowledge this is an architectural flaw and needs to be rectified.

unregistered version of Eziriz's ".NET Reactor"! #8990
Answer

How did it suddenly stop working? We had a functional 9.1.0 build that was working without errors.

This is a serious / important question. I had a fully deployed system that stopped working due to this issue.
The system has a requirement to have high availability.

My customer will not accept this type of architecture whereby the site availability is dependent on a third party.

@ABP - Do you agree? Do you think a chance is required here?

unregistered version of Eziriz's ".NET Reactor"! #8990
Answer

hi karl.ettinger

Can you rebuild and publish the website?

Sorry for your production website. Please get in touch with us(info@abp.io). We will do something.

Hi Maliming, I would like to understand this as well. I also had a site go down.
I am concern that a fully deployed system has dependencies on ABP.

Can you please advise what is being done to prevent this.

Thank you.

Showing 11 to 20 of 96 entries
Boost Your Development
ABP Live Training
Packages
See Trainings
Mastering ABP Framework Book
The Official Guide
Mastering
ABP Framework
Learn More
Mastering ABP Framework Book
Made with ❤️ on ABP v10.8.0-preview. Updated on September 28, 2026, 11:44
1
ABP Assistant
🔐 You need to be logged in to use the chatbot. Please log in first.