[akka-user] Is there a standard way of referencing external objects inside of custom serializers?

Consider a serializer that delegates to some JSON library. The delegate is instantiated outside of the serializer, before the ActorSystem is even created (when, for example, relying on a dependency injection framework). Is it possible to "share" this delegate with the serializer(s) that depend

Re: [akka-user] Class cast exceptions in actors that return Future[Unit]

Ahah! I think you may of nailed it... Thanks! Indeed you did nail it - "thanks" doesn't come close as I'd looked at this for so long that I'd gone completely snow-blind ;-) Is there a convenient shorthand way of mapping between a scala.util.Success and an akka.actor.Status.Success, or

Re: [akka-user] Class cast exceptions in actors that return Future[Unit]

On 31/01/17 23:34, Viktor Klang wrote: I think the problem is that your responding with a scala.util.Success rather than a akka.actor.Status.Success. Ahah! I think you may of nailed it... Thanks! -- Alan Burlison -- -- Read the docs: http://akka.io/docs/ Check the FAQ:

Re: [akka-user] Class cast exceptions in actors that return Future[Unit]

I think the problem is that your responding with a scala.util.Success rather than a akka.actor.Status.Success. On Wed, Feb 1, 2017 at 12:20 AM, Alan Burlison wrote: > On 31/01/17 22:18, Viktor Klang wrote: > > The answer will be in the stack traces. >> > > What I got

Re: [akka-user] Class cast exceptions in actors that return Future[Unit]

On 31/01/17 22:18, Viktor Klang wrote: The answer will be in the stack traces. What I got was: java.lang.ClassCastException: Cannot cast scala.util.Success to scala.runtime.BoxedUnit which didn't give me much of a clue, however it was clear that asInstanceOf wasn't the right approach and

Re: [akka-user] Class cast exceptions in actors that return Future[Unit]

The answer will be in the stack traces. -- Cheers, √ On Jan 31, 2017 10:55 PM, "Akka Team" wrote: > If it in fact was a Unit you got back from the actor then neither of the > things you tried should throw a class cast exception though. If the actor > for example sends

Re: [akka-user] Class cast exceptions in actors that return Future[Unit]

If it in fact was a Unit you got back from the actor then neither of the things you tried should throw a class cast exception though. If the actor for example sends a Future[Unit] back, then you will have a Future[Future[Unit]] returned from ask. -- Johan Akka Team On Tue, Jan 31, 2017 at 2:41

Re: [akka-user] Class cast exceptions in actors that return Future[Unit]

On 31/01/2017 20:32, Akka Team wrote: You have a Future[Something], and a Something is an Any (everything is) but it is not Unit (only Unit is), so you can not just cast it, you must replace it with an actual Unit, which is what .map(_ => ()) does. OK, thanks for confirming that I haven't

Re: [akka-user] Class cast exceptions in actors that return Future[Unit]

You have a Future[Something], and a Something is an Any (everything is) but it is not Unit (only Unit is), so you can not just cast it, you must replace it with an actual Unit, which is what .map(_ => ()) does. -- Johan Akka Team On Tue, Jan 31, 2017 at 11:35 AM, Alan Burlison

Re: [akka-user] CRDT gossip implementation - replication flow

On Tue, Jan 31, 2017 at 7:26 AM, Vadim Punski wrote: > > > On Tuesday, January 31, 2017 at 4:02:51 PM UTC+2, Patrik Nordwall wrote: >> >> >> >> On Tue, Jan 31, 2017 at 6:42 AM, Vadim Punski wrote: >> >>> >>> >>> On Monday, January 30, 2017 at 4:29:13 PM

[akka-user] Class cast exceptions in actors that return Future[Unit]

I'm writing an Akka persistence journal that saves data in JSON format. I've done that as normal, by subclassing AsyncWriteJournal and implementing the necessary methods. The actual file IO is done by sub-Actors, one per output file where each persistent actor has its own JSON file. The

Re: [akka-user] Akka persistence: can you use it as the main storage system for you application's data?

On Mon, Jan 30, 2017 at 1:00 PM, José González Gómez < jose.gonza...@openinput.com> wrote: > First of all, Akka persistence stores data using a journal. Data in that > journal (both events and snapshots) are stored after being serialized. This > seems to pose several problems: > >- You can't

Re: [akka-user] Akka persistence: can you use it as the main storage system for you application's data?

On 30/01/17 18:00, José González Gómez wrote: - You can't have access to data as you may have in a SQL or NoSQL database, so it seems to be hard to diagnose corrupt data or relationships among that data. Am I missing anything here? Not that I know of, which is why I'm hacking

Re: [akka-user] How to stop unstoppable actor?

Hi Sergey, It's hard to guess with the information you provided, so here are a few questions: are you sure the killSwitch is placed in the correct place in the flow? are flow stages executing in a timely fashion, or do they occupy CPU for long periods of time? how and when are you triggering

Re: [akka-user] transactors and STM are gone. What conception to use instead?

I think you need to look into saga pattern which is actor model analogue of (distributed) transactions. It has the advantage that the parties involved in the transaction do not need to be present on the same VM (cluster node etc.) which is a prerequisite for STM / Agents. Cheers, Rafał W dniu

[akka-user] Re: Make Source from remote actor

Hi, Ad 1. you could create your own Actor that would take Source.actorRef in through it's Props. You can give this actor a name as necessary and it would forward the messages from remote system to be published locally by the Source. Ad 2. I don't see why wouldn't it be visible. ActorRef are

[akka-user] Akka persistence: can you use it as the main storage system for you application's data?

Hi! I've been reading about Akka persistence, and it seems the way to go to persist data in a reactive application, using event sourcing and immutable data models. I have no experience doing this, so I'd love to hear about your experience. Any way, after reading the docs, I have the following

[akka-user] Delaying akka.remote.netty.tcp.{hostname, port} resolution?

Greetings -- I'm moving here a thread started on twitter. Here's my scenario: I am spinning up a cluster on a compute fabric that's managed by an external component. One consequence of this configuration is that the nodes' IP addresses and their ports aren't known a priori: they are

Re: [akka-user] how to stop waiting for association failed remote??

Basically, you need to implement one of the strategies describes in the Split Brain Resolver document yourself. This isn't rocket science, but it does require a bunch of tricky work. (Which is why Lightbend can charge money for it.) You need to pay attention to the Cluster, and particularly to

Re: [akka-user] CRDT gossip implementation - replication flow

On Tue, Jan 31, 2017 at 6:42 AM, Vadim Punski wrote: > > > On Monday, January 30, 2017 at 4:29:13 PM UTC+2, Patrik Nordwall wrote: >> >> >> It's sent to one random node per tick, not all nodes. >> > > Node per tick, you're right ... > > >> The reason for sending all digests is

Re: [akka-user] CRDT gossip implementation - replication flow

On Monday, January 30, 2017 at 4:29:13 PM UTC+2, Patrik Nordwall wrote: > > > It's sent to one random node per tick, not all nodes. > Node per tick, you're right ... > The reason for sending all digests is to be able to find entries that are > not the same. Remember that message delivery

Re: [akka-user] Streaming as HTTP response on spray-can 1.3.1 withAck

In Addition, We are sending the content-type with the response. On Tue, Jan 31, 2017 at 12:27 PM, aarti wrote: > Hi Team, > > I need to send the chunk messages as streams as an http-response withACK > from spray-can 1.3.1. and getting the below error: > >