Re: [akka-user] Permanently stopping a persisted single entity in a cluster shard

2017-06-06 Thread Yee-Ning Cheng
I see, that makes sense. After thinking about the design, the passivation might actually work for my use case. Thanks! On Tuesday, June 6, 2017 at 11:21:33 AM UTC-4, Justin du coeur wrote: > > Well, yeah -- that's how Sharding works, and how it is *supposed* to > work. If you send a message t

Re: [akka-user] Permanently stopping a persisted single entity in a cluster shard

2017-06-06 Thread Justin du coeur
Well, yeah -- that's how Sharding works, and how it is *supposed* to work. If you send a message to a sharded ID, it will start an entity with that ID. Passivate and the like are intended, as the name implies, to *passivate* the Actor -- to turn it off temporarily while it's not doing anything use

[akka-user] Permanently stopping a persisted single entity in a cluster shard

2017-06-06 Thread Yee-Ning Cheng
I currently have an actor that extends PersistentActor and is created using cluster sharding as a single entity part of a shard. After a certain amount of time, I want to be able to explicity kill/stop a single entity actor permanently. I have tried using Passivate, explicitly sending a Poiso

[akka-user] Re: ActorSystem Uncaught fatal error shutting down ActorSystem !

2017-06-06 Thread johannes . rudolph
Hi, my colleague Arnout just found out that the error will only be logged to stderr if you enable the `akka.jvm-exit-on-fatal-error` setting. Can you try enabling this setting and then run again? I also filed an issue to improve the logging of fatal errors: https://github.com/akka/akka/issue

[akka-user] Re: Akka cluster http management

2017-06-06 Thread johannes . rudolph
Hi, the hostname setting is a bit misnamed. It defines the interface the server binds to. So, you can put "0.0.0.0" in there to make sure the management interface is bound on all interfaces (but make sure not to expose it publicly) or put some other interface address in there. I filed https:/

[akka-user] Re: ActorSystem Uncaught fatal error shutting down ActorSystem !

2017-06-06 Thread johannes . rudolph
Hi, in cases of fatal errors, the error and stack trace is logged to stderr (not using the logging framework). Note that in some cases, the logging itself may fail (that's why the error is fatal: after it happens, the state of the JVM might be corrupted and operations like logging may fail for

[akka-user] Message [akka.stream.impl.fusing.ActorGraphInterpreter$Resume$] was not delivered in 'completeStage()' of BidiStage

2017-06-06 Thread Alexey Shuksto
Hello hAkkers, I've got some filter-like bidi-stage that filters elements of second flow based on elements from first one. Like this: final class IOFilter[O] extends GraphStage[BidiShape[O, O, O, O]] { val inO1: Inlet[O] = Inlet("IOFilter.inO1") val inO2: Inlet[O] = Inlet("IOFilter.inO2