Re: [akka-user] Re: Akka interoperability with Akka.net ?

Hi, No, remoting is not possible to use with Kafka. Roland wanted to say that you can use Kafka (or Http, or any other technology) *instead* of remoting if you want interoperability. Nothing forces you to use Akka Remoting. -Endre On Thu, Dec 17, 2015 at 12:40 AM, marin aglic

Re: [akka-user] Re: Feedback on BackoffSupervisor

There is an alternative to not doing the context.stop(self) on persist failures, that I didn't follow up on in the discussion in the pull request; you can throw a special exception that inherits from Throwable (let's call this `PersistFailureException`) So, the motivation behind

[akka-user] Deserialize ActorRef, again

Hey hAkkers, I've been trying to implement Serializer for akka so that it uses https://github.com/RuedigerMoeller/fast-serialization instead of the default Java one. The code is as follows class FST4Akka(system: ExtendedActorSystem) extends Serializer { val address =

[akka-user] Re: Deserialize ActorRef, again

As a related question: is it possible to use my customed serializer for anything but ActorRefs, so that I don't have to handle any akka-specific stuff? What would the correct configuration be? -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >>

Re: [akka-user] Re: Feedback on BackoffSupervisor

I will try one more comment though, Why not put the two back-off supervisors in the akka.pattern package instead of one of them in contrib, and have the BackoffSupervisor props methods create one or the other (and give the props methods some good names)? The actual back-off supervisor actors

Re: Re: Re: [akka-user] How to pipe reactive mongo results into a WebSocket stream

Hi Endre, finally I had the time to come back to that issue. Thanks for your advice. It works like expected now that I use Merge node. However, one final question. Why doesn't the whole stream terminate when the browser closes the connection? When the outgoing side is closed then the whole

Re: [akka-user] Re: Feedback on BackoffSupervisor

On Thu, Dec 17, 2015 at 6:14 PM, Henry Mai wrote: > There is an alternative to not doing the context.stop(self) on persist > failures, that I didn't follow up on in the discussion in the pull request; > you can throw a special exception that inherits from Throwable (let's

[akka-user] Deadlock in a flow with a cycle?

Hey everybody, I'm trying to convince myself that a flow I'm building with Akka Streams is deadlock-free. Here's what I'm trying to do: - I have an infinite source *s* of some kind of requests *r1, r2, ... *that I need "execute". - In case such an execution fails, I'd like to

Re: [akka-user] Re: Feedback on BackoffSupervisor

That is not true. The default behavior to restart does not apply to custom exceptions that extend from Throwable. It will escalate custom exceptions that extend from Throwable. You can test this out yourself by creating a parent actor and a child actor within the parent actor and have it throw

[akka-user] Streaming http call gives EntityStreamSizeException (2.0-M2)

Hi all, I'm running into an EntityStreamSizeException when streaming data from a streaming response I got by calling another endpoint.. It is a little bit like presented in the talk by Mathias & Johannes at scalaworld: https://www.youtube.com/watch?v=6VBn9V3S2aQ I'm using with akka-http

[akka-user] akka-typed question about behavior vs actors?

How does behavior correlate with the actor instance? If I create a behavior with an "And" combinator, does it create two actors? I've posted a more detailed question on SO: http://stackoverflow.com/questions/34340262/does-akka-typed-create-actors-when-i-use-behavior-combinator-like-and I think

Re: [akka-user] Re: Feedback on BackoffSupervisor

> User can install supervision that catch and for example resume, which can result in that the in-memory state is different from what is actually stored. Sure, the user can catch all Throwables, but my statement was that it doesn't happen by default. > We have a solution that works. Why

Re: [akka-user] Re: Feedback on BackoffSupervisor

Ah, I missed that you extended Throwable. That will anyway not enforce that the actor is always stopped when there are storage exceptions. User can install supervision that catch and for example resume, which can result in that the in-memory state is different from what is actually stored. We

Re: [akka-user] Re: Feedback on BackoffSupervisor

Hi Patrik, Henry Mai looped me in on the existence of the TransparentExponentialBackoffSupervisor in akka-contrib and PR https://github.com/akka/akka/pull/18776 (thanks Henry!). I find it confusing that there are two. As a user I would like one BackoffSupervisor, in akka.pattern, not two, one

Re: [akka-user] Re: Feedback on BackoffSupervisor

On Thu, Dec 17, 2015 at 11:58 AM, Raymond Roestenburg < raymond.roestenb...@gmail.com> wrote: > Hi Patrik, > > Henry Mai looped me in on the existence of > the TransparentExponentialBackoffSupervisor in akka-contrib and PR > https://github.com/akka/akka/pull/18776 (thanks Henry!). > I find it

Re: [akka-user] Re: Feedback on BackoffSupervisor

On Thursday, December 17, 2015 at 1:18:47 PM UTC+2, Patrik Nordwall wrote: > > > > On Thu, Dec 17, 2015 at 11:58 AM, Raymond Roestenburg < > raymond.r...@gmail.com > wrote: > >> Hi Patrik, >> >> Henry Mai looped me in on the existence of >> the TransparentExponentialBackoffSupervisor in

Re: [akka-user] Re: Feedback on BackoffSupervisor

> > Why? We had flawed failure handling in Akka Persistence 2.3. We must > enforce stopping of the persistent actor when there are journal failures, > becuase the state must not diverge from what has actually been stored. > http://doc.akka.io/docs/akka/2.4.1/scala/persistence.html#Failures > >