You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Saga Timeout manager does not have a SagaId property and thats why its not unique.
To Reproduce
Steps to reproduce the behavior:
Create a new Saga
Add a handler for ISagaHandlesTimeout
Instantiate a new saga. The first one works perfectly fine.
Instantiate another saga - You will get this error message:
ERR akka://your-app-system/user/yoursaga-saga] Actor name “BulkActionTimeout-timeoutmanager” is not unique!
[akka://your-app-system/user/bulkaction-saga/bulkaction-a8ac291a-e157-4ba9-ac99-618d2831dee5#1018278655]: Akka.Actor.ActorInitializationException: Exception during creation
---> Akka.Actor.InvalidActorNameException: Actor name “BulkActionTimeout-timeoutmanager” is not unique!
at Akka.Actor.Internal.NormalChildrenContainer.Reserve(String name)
at Akka.Actor.ActorCell.ReserveChild(String name)
at Akka.Actor.ActorCell.MakeChild(Props props, String name, Boolean async, Boolean systemService)
at Akka.Actor.ActorCell.ActorOf(Props props, String name, Boolean isAsync, Boolean isSystemService)
at Akka.Actor.ActorCell.ActorOf(Props props, String name)
at Akkatecture.Sagas.AggregateSaga.AggregateSaga`3.PreStart()
at Akka.Actor.ActorBase.AroundPreStart()
at Akka.Persistence.Eventsourced.AroundPreStart()
at Akka.Actor.ActorCell.<>c__DisplayClass176_0.b__0()
at Akka.Actor.ActorCell.UseThreadContext(Action action)
at Akka.Actor.ActorCell.Create(Exception failure)
--- End of inner exception stack trace ---
at Akka.Actor.ActorCell.Create(Exception failure)
at Akka.Actor.ActorCell.FinishCreate()
Expected behavior
Multiple saga should. be able to handle timeouts uniquely
Actual behavior
Run time error
Screenshots
Environment
Linux
Additional context
The text was updated successfully, but these errors were encountered:
Version Information
0.6,1
Describe the bug
Saga Timeout manager does not have a SagaId property and thats why its not unique.
To Reproduce
Steps to reproduce the behavior:
ERR akka://your-app-system/user/yoursaga-saga] Actor name “BulkActionTimeout-timeoutmanager” is not unique!
[akka://your-app-system/user/bulkaction-saga/bulkaction-a8ac291a-e157-4ba9-ac99-618d2831dee5#1018278655]: Akka.Actor.ActorInitializationException: Exception during creation
---> Akka.Actor.InvalidActorNameException: Actor name “BulkActionTimeout-timeoutmanager” is not unique!
at Akka.Actor.Internal.NormalChildrenContainer.Reserve(String name)
at Akka.Actor.ActorCell.ReserveChild(String name)
at Akka.Actor.ActorCell.MakeChild(Props props, String name, Boolean async, Boolean systemService)
at Akka.Actor.ActorCell.ActorOf(Props props, String name, Boolean isAsync, Boolean isSystemService)
at Akka.Actor.ActorCell.ActorOf(Props props, String name)
at Akkatecture.Sagas.AggregateSaga.AggregateSaga`3.PreStart()
at Akka.Actor.ActorBase.AroundPreStart()
at Akka.Persistence.Eventsourced.AroundPreStart()
at Akka.Actor.ActorCell.<>c__DisplayClass176_0.b__0()
at Akka.Actor.ActorCell.UseThreadContext(Action action)
at Akka.Actor.ActorCell.Create(Exception failure)
--- End of inner exception stack trace ---
at Akka.Actor.ActorCell.Create(Exception failure)
at Akka.Actor.ActorCell.FinishCreate()
Expected behavior
Multiple saga should. be able to handle timeouts uniquely
Actual behavior
Run time error
Screenshots
Environment
Linux
Additional context
The text was updated successfully, but these errors were encountered: