[akka-user] Question about kaka-http websocket client

Hello all, Hoping someone can shed some light on the following! I am using the example provided with the documentation: object WebSocketClient extends App { implicit val system = ActorSystem("test") implicit val fm = ActorMaterializer() import system.dispatcher val incoming: Sink[Mess

Re: [akka-user] multi actor or just one?

Hi Martynas : Thanks for your answer. for design a low latency application, we don't want to having a lot of thread because it will cause context switching issue. I don't know how the akka/scale to avoid this problem if we create lot of actors in the system. really appreciate your help Reg

[akka-user] Is there a way to get the supervisor actorref of an actor?

Just playing around a bit and was wondering what the replacement was (if there is any) of the following method on ActorRef in version 1.x defsupervisor : Option[ActorRef ] Returns the supervisor, if there is one. http://doc.akka.io/api/

[akka-user] Async console output

This whole area of async boundaries in akka streams is still very confusing to me. I don't know what to suggest in terms of documentation, other than numerous examples of code, with corresponding diagrams showing the resultant boundaries and actor instances after materialization. As an example, I

Re: [akka-user] flexible path router

I have written a mini server that forwards messages through the root container, and that can serve up resources, using akka.http. It's pretty neat and short: SoLiD (Social Linked Data) Server.

[akka-user] Re: A simple question?

Hi, Thank for your quickly responses. I have developed a framework for active learning, named JCLAL (Java Class Library for Active Learning). In the area of active learning is commonly to find problems that involve huge amount of data. Therefore, the scalability of this type of class library is

[akka-user] How to create a good persistence actor test in java

Hi, I'm working on figuring out how to create a good persistence actor test in java but am struggling with the example . This is my unit-test code

Re: [akka-user] Managing blocking (outside of an Actor or Stream stage)

Thanks. Is there a good way within my stream code to look up the blocking dispatcher? Or do I need to do something like this at the top level val blockingExecutionContext = system.dispatchers.lookup( "blocking-dispatcher") and pass it through intervening layers as a non-implicit parameter, in add

Re: [akka-user] Re: A simple question?

Hi Oscar, Akka definitely makes a lot of sense even just locally – Actors are also a concurrency abstraction (much nicer to work with than threads). One would need to know more about your project to say more however. For example, while we have Actors, some things are better modeled as Akka Strea

[akka-user] Re: A simple question?

Yes. But without knowing more there's no way we can know if it's an appropriate choice or not. On Wednesday, March 2, 2016 at 9:15:50 AM UTC-7, Oscar Gabriel Reyes Pupo wrote: > > Hello, > > I'm new in Akka. After reading some examples, I have a simple question, It > is suitable to use Akka fo

[akka-user] Camel Producer acknowledge on success

Hi, class JmsCamelProducer(override val endpointUri: String) extends Actor with Producer How do I know the the message published by the Actor was success ? I can't seem to find any response coming back. Any pointers ? Akhil PS: I am publishing it to an ibm MQ -- >> Read the d

[akka-user] A simple question?

Hello, I'm new in Akka. After reading some examples, I have a simple question, It is suitable to use Akka for developing a concurrent application that only runs on a single machine? Best Oscar Reyes -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >>

[akka-user] akka default dispatcher : parallelism-min & parallelism-max

I am a newbie to akka, so please excuse me if this sounds like a dumb question. I am trying to understand akka's default dispatcher configuration with fork-join-pool executor. I have 8 core cpu and this is my dispatcher configuration, akka.actor.default-dispatcher { fork-join-executor {

[akka-user] Re: Connecting RabbitMQ with Java Actors

Thank you. On Friday, February 26, 2016 at 7:13:18 AM UTC-6, Guido Medina wrote: > > *Correction of previous response:* As far as my experience with RabbitMQ > goes they provide *a client* which will start a loop thread and a handler > function should be specified. > -- >> Read th

Re: [akka-user] Am I misunderstanding throttle?

Hi Endre, many thanks for wanting to help me!! If you run the code you will see that only "success : Pipeline 2" gets outputted to System.out. If I remove the Throttle everything works as expected. //Source pipeline = source.via(throttle).mapConcat(t -> t); Source pipeline = source.mapConcat

Re: [akka-user] Am I misunderstanding throttle?

Hi John, Can you prepare a small reproducer? It might be a bug, but we can only be sure if we see some code that exhibits the behavior. -Endre On Wed, Mar 2, 2016 at 1:40 PM, wrote: > I am running up several instances of the an akka streams pipeline. > > In the pipeline there is a throttle sta

[akka-user] Am I misunderstanding throttle?

I am running up several instances of the an akka streams pipeline. In the pipeline there is a throttle stage (Flow.create.throttle(..)) Now what is happing is that only the first pipeline works. The other pipelines all stall. Any Ideas? Many Greetings John -- >> Read the docs: ht

Re: [akka-user] multi actor or just one?

Hi Steven, per-request actors are usually created when you have some state to keep up for every request while handling it. If you go with a fixed number of actors, make sure to have at least as much actors as you have threads in your thread pool, as otherwise you will not be utilizing all availab

Re: [akka-user] Re: Does each ActorMaterializer need its own ActorSystem?

ActorMaterializer needs ActorContext and a Materializer can be used for many materializations. -- Cheers, √ On Mar 2, 2016 10:22, wrote: > sorry I hitted the send button too early. its just meant as pesudo code. > I was wondering if each > > ActorMaterializer needs its own ActorSystem ? Or can

[akka-user] ANNOUNCE: akka-persistence-dynamodb and akka-persistence-cassandra

Dear hakkers, we proudly present two additions to the Akka github family: akka-persistence-cassandra and akka-persistence-dynamodb . Both projects have their roots in the Eventsourced

Re: [akka-user] Re: Does each ActorMaterializer need its own ActorSystem?

On Wed, Mar 2, 2016 at 10:26 AM, Tal Pressman wrote: > In our application we create a new ActorMaterializer for each stream, but > only 1 ActorSystem and there are no problems with it. > Hm, why do you need that? For being able to shut down streams? -Endre > In another part of the application

[akka-user] multi actor or just one?

Hi I am very new to akka framework. but now I have one design question, hope someone could help me on this in my user case, we have a message queue, client sends message to the queue (1M to 2M message per day), our application process it.. there are two way to use the actor here. one is in ou

Re: [akka-user] Re: Does each ActorMaterializer need its own ActorSystem?

In our application we create a new ActorMaterializer for each stream, but only 1 ActorSystem and there are no problems with it. In another part of the application we also have a single a single ActorMaterializer that is used to create many streams. Tal On Wednesday, March 2, 2016 at 11:22:49 A

Re: [akka-user] Re: Does each ActorMaterializer need its own ActorSystem?

On Wed, Mar 2, 2016 at 10:22 AM, wrote: > sorry I hitted the send button too early. its just meant as pesudo code. > I was wondering if each > > ActorMaterializer needs its own ActorSystem ? > > No, it does not, you can just share one. > Or can one ActorSystem be used for many Materializers?

Re: [akka-user] Re: Does each ActorMaterializer need its own ActorSystem?

If the question is whether you need a *new* system for each materializer, then the answer is no. In fact, 99% of the cases you want to have one system and reuse it everywhere. Also, there is no need to create a new materializer in your foreach block. You can create one upfront and just use it (it i

Re: [akka-user] Re: Does each ActorMaterializer need its own ActorSystem?

sorry I hitted the send button too early. its just meant as pesudo code. I was wondering if each ActorMaterializer needs its own ActorSystem ? Or can one ActorSystem be used for many Materializers? Am Mittwoch, 2. März 2016 10:17:32 UTC+1 schrieb √: > > I don't understand the question. And l

Re: [akka-user] Re: Does each ActorMaterializer need its own ActorSystem?

I don't understand the question. And looking at the code I don't think it would compile. On Wed, Mar 2, 2016 at 10:15 AM, wrote: > system = ActorSystem.create(); > > new Array[]{"a","b"}.stream() > .forEach { > final Materializer m = > ActorMaterializer.create(ActorMaterialize

[akka-user] Re: Does each ActorMaterializer need its own ActorSystem?

system = ActorSystem.create(); new Array[]{"a","b"}.stream() .forEach { final Materializer m = ActorMaterializer.create(ActorMaterializerSettings.create(system).withSupervisionStrategy(decider), system); pipeLine.to(Sink.foreach(..).run(m); } } Now only the

[akka-user] Does each ActorMaterializer need its own ActorSystem?

I have the following code new Array[]{"a","b"}.stream() .forEach { } } -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >> http://doc.akka.io/docs/akka/current/additional/faq.html >> Search the archives: https://groups.google.co