[akka-user] design question - modeling a multi step data aggregation with actors

Hi, I’m wondering what would be the best way to model services which continually collect data from various sources until it finally has enough to create an answer. In synchronous pseudo code this would look like: def myservice = { val field1 = getData1().map(_.getField1) val field2 = getDat

[akka-user] Re: design question - modeling a multi step data aggregation with actors

ing with? I'm just trying to get a > sense of how much elegance you might need to trade to squeeze out perf. > > On Wednesday, July 16, 2014 6:56:00 AM UTC-7, Adam wrote: >> >> Hi, >> >> I’m wondering what would be the best way to model services which >>

[akka-user] Changing socket options from the Java API of Akka IO

Hi, Is there a way to change socket options such as send & receive buffers from the Java API? All I can find is the set of Scala case classes (e.g. http://doc.akka.io/api/akka/snapshot/index.html#akka.io.Inet$$SO$$SendBufferSize), but to the best of my knowledge there is no way to use case cla

Re: [akka-user] Changing socket options from the Java API of Akka IO

, rkuhn wrote: > > Hi Adam, > > Scala’s case classes are normal classes, they just come with a few > auto-generated methods (like productIterator() and static apply()). > Nothing stands in the way of using them just like any other Java class. > > Regards, > > Ro

Re: [akka-user] Changing socket options from the Java API of Akka IO

factory methods are there in the class. On Wednesday, July 23, 2014 1:39:48 PM UTC+3, Adam wrote: > > Hi, > > Thanks, this indeed works. > However, just for the record, the way to reference these classes is not > exactly as the average Java programmer would expect. > I had to

Re: [akka-user] Changing socket options from the Java API of Akka IO

OK. Thanks a lot. On Wednesday, July 23, 2014 1:52:57 PM UTC+3, rkuhn wrote: > > Ah, right, that is the more direct route. This is in the JavaDoc by way of > “implemented super-interfaces”. > > Regards, > > Roland > > 23 jul 2014 kl. 12:49 skrev Adam >: > >

Re: [akka-user] Futures vs actors

I suspect any kind of long running operation running on the same dispatcher as other actors (or futures) that are supposed to work at a high throughput is problematic - future or actor. On Wednesday, July 30, 2014 9:09:00 PM UTC+3, Saurabh Rawat wrote: > > Hi Bartłomiej, > > One more thing, acto

[akka-user] Re: Tackling the ask pattern and `timeout hell`

I was facing a similar decision a few weeks ago. For now, I've went with the actor per request approach that Martynas mentions. The actor basically looks like a series of receive methods and I use become to switch between them. Each switch is done whenever I need to wait for an asynchronous call

[akka-user] modifying log level at run-time

Hi, I know Akka's configuration does not get reloaded at run-time (see here ). It is however quite a common use case for logger settings to be re-loadable at run-time. Is there any way to achieve this? -- >>

Re: [akka-user] modifying log level at run-time

Hi, One more follow up question. When using the setting advised by the documentation for this scenario (http://doc.akka.io/docs/akka/snapshot/java/logging.html#SLF4J) the only real gap from what I need is that with akka.logLevel set to DEBUG and with the SLF4J binding configured to INFO, writin

[akka-user] Re: Handle legacy blocking IO (InputStream/OutputStream)

Hi, I'm not sure how using protobuf forces you to communicate in a blocking manner. I'm also using it but over akka.io, which is modeled as actors, so it's completely non blocking and works in exactly the same way as the rest of my application does. On Tuesday, September 2, 2014 11:44:27 AM

[akka-user] Re: Handle legacy blocking IO (InputStream/OutputStream)

(by akka.io, I meant the IO package of akka <http://doc.akka.io/docs/akka/2.3.5/scala/io.html>, of course...) On Tuesday, September 2, 2014 4:06:56 PM UTC+3, Adam wrote: > > Hi, > > I'm not sure how using protobuf forces you to communicate in a blocking > manner. &g

[akka-user] Re: combining receive pfs - am I being stupid here?

Interesting. Which Scala version are you using? I've copied your code into a Scala project I have that uses Scala 2.11.2 (with akka 2.3.6) and I get no warnings. Also the IDE (Intellij) correctly shows that receive is of type PartialFunction[Any,Unit]. Have you tried modifying it to: def recei

Re: [akka-user] Re: combining receive pfs - am I being stupid here?

: >> >> sorry meant to add - yes with or without { } it has the same and just >> changing now to 2.3.6 it makes no different >> >> On 23 September 2014 23:15, Tim Pigden >> > wrote: >> >>> 2.11.2 (akka 2.3.4) >>> >>> scalacOptio

[akka-user] Akka Cluster Metrics- Node Wise

You cannot have separate cpu and heap metrics for nodes within the same JVM. OSGI won't help either - it mostly achieves containment through complex class loaders. You could sort of have an approximiation of CPU consumption per node by summing up the thread cpu consumption for the related dispat

[akka-user] Realtime (as in Electronics) processing in Akka and Garbage Collection's Effect to It

There is also an option of trying the Zing JVM from Azul. It's not free, but depending on your case, it might end up being cheaper in the overall, assuming it does what they claim - I've never used it myself, only talked to other people who were using it. Also it's possible for some application

[akka-user] Re: [Java 2.3.x] Default message behaviors?

One easy way is to extend UntypedActor, override whatever methods you need with final methods and provide your own callback methods for overriding by sub classes. The slightly messy part of this is that you’ll be forced to provide callback method names with different names (e.g. onResolverReceiv

[akka-user] How to Monitor akka, improving performance

I suspect a thread dump in this state and the akka version you're using would be invaluable to understanding this. -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >> http://doc.akka.io/docs/akka/current/additional/faq.html >> Search the

Re: [akka-user] Testing per-request child creation

It's a matter if opinion and I risk stating the obvious, but my (unoriginal) rules of thumb are: Updates to internal state are out of scope for tests. Sometimes when something is not testable, it's for a good reason - you're code should simply be modified. This is one of those cases. Adding i

[akka-user] Maven, scala, akka - version mismatch

Try running "mvn dependency:tree" (before and after commenting out). It will show you exactly how you get each library. Most probably you're getting akka 2.3.X for scala 2.11 as a transitive dependency. -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >

[akka-user] Re: Sharing behavior among Actors in Java

Object msg){ //use the shared logic of db and auth whereever needed } @Override public UntypedActor getActor() { return this; } } Finally, for asynchronous paths we simply use more actors, but I assume that was already obvious to you and you were asking about

[akka-user] Re: One-Actor-Per-Request pattern with Akka-Http

So why not always return OK in such cases? -- >> 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.com/group/akka-user --- You received th

[akka-user] Re: Using different names for application.conf

See here: http://doc.akka.io/docs/akka/snapshot/general/configuration.html You can add the system property -Dconfig.resource= And load whatever file you wish as your configuration file. On Monday, February 2, 2015 at 8:55:13 PM UTC+2, Mark Kaberman wrote: > > My application consists out of multip

Re: [akka-user] Re: Why AKKA Microkernel

dows servers :( ~Adam~ On Wed, Jan 22, 2014 at 12:58 PM, Peter Wolf wrote: > Thanks Victor, I had read that doc, but it left me puzzled. That's why I > asked here. > > Here is the important paragraph: > > "The purpose of the Akka Microkernel is to offer a bundling mechan

Re: [akka-user] How can I reconcile untyped actors with typeful programming?

While far from perfect, one thing that I do is strictly following the convention that the only objects a specific actor will process are defined within that actor's companion object. I also refrain from directly importing those objects/classes anywhere so I always have to write out actor.message w

[akka-user] Is it possible to use Akka logging while only referencing SLF4J API?

Hi, I've read thorough the instructions under the logging chapter of the Akka manual(Java API in this case) and it seems like what it requires is directly using the akka.event.Logging and akka.event.LoggingAdapter classes. (BTW Suspecting I might have missed something in the documentation, I lo

Re: [akka-user] Is it possible to use Akka logging while only referencing SLF4J API?

n't one for now. Thanks. On Monday, June 23, 2014 6:55:19 PM UTC+3, Björn Antonsson wrote: > > Hi Adam, > > I'm not sure that I understand your question completely. > > Akka can use slf4j as a backend for akka logging. Akka does not provide a > generic slf4 backe

Re: [akka-user] Re: Performance Of Akka IO

I think the OS you're using matters a lot for this sort of test. Hopefully it's not windows... What was the maximum concurrency level that you've tested? Did you make sure (in the performance test code) that this concurrency level is actually met in all cases? Did you try tweaking with the socke

Re: [akka-user] Performance Of Akka IO

I believe 50M messages per second on a single machine was mainly an example for scaling up. See the kind of machine that was used for it . Anyway, have you tried doing the same analysis on the "legacy" driver? It

[akka-user] Many concurrent network connections

I'll refer you to here: http://doc.akka.io/docs/akka/2.3.9/dev/io-layer.html It says Akka IO is designed with the requirement of "scalability to millions of concurrent connections". Of course, this typically requires tuning (including at the OS level), but sounds like 50k should be supported. I

[akka-user] Re: Best practices for selecting or creating actor

First of all, you shouldn't ever block like this, as you do with Await. As for your question - this sounds like something the parent actor should be responsible for. I'm not even sure the code above works (it at least never occurred to me to try to create an actor using a full path as I always u

[akka-user] Overriding default configuration

First of all, regardless of inclusion, you need your build to exclude this application.conf file from jars. There's not much point for a configuration file that can't be easily modified. It should instead be in a folder (e.g. ./conf) that is added to your classpath. Then, you can either add you

[akka-user] Number of actors

Hi, First of all, actors are very lightweight and you can have many of them, while an ActorSystem is heavyweight and you should not have many of that (typically you'd have one). As for the pattern you describe - it all depends on the fine details, but if I had to implement a service that needs

[akka-user] Re: High variance in response times when using Akka

As far as high variance - Have you tried looking into GC performance? I don't know what "around 2ms" means, but if that's the expected max ET you're looking for, GC could make this very difficult to achieve. I would try to use JMH in order to isolate the CPU intensive work and optimize whatever

[akka-user] What happens to unhandled(message)?

Unhandled is mainly useful for troubleshooting. Akka won't check if you actually did something with the message or not. It also doesn't force you to call unhandled and probably (never tried this) does't prevent you from calling unhandled multiple times. The documentation goes into detail regardi

[akka-user] Re: Reasons why Logback is recommended for Akka logging

Hi, Where I work, we're using Akka with log4j2 (through slf4j binding) in production. We're handling billions of daily requests and so far it works flawlessly :-) On Thursday, May 21, 2015 at 10:55:22 AM UTC+3, monika singhal wrote: > > Anyone tried log4j2 with Akka ? > > Thanks, > Monika > > >

[akka-user] Instrumenting Akka

You can take 2 heap dumps a day or more apart and then use Eclipse MAT to compare them (there's a compare basket feature that is very useful in such cases). Actually there's a good chance that even a single heap dump will suffice if the JVM has been running for long enough. Try to use the leak

Re: [akka-user] DynamoDB snapshot plugin?

There’s actually one thing you need to take into account when using DynamoDB for persistence. I've been bitten by this a few times when using other Amazon services. The Java SDK provided by Amazon includes two interfaces: synchronous and asynchronous. I imagine you’d prefer to use the asyn

[akka-user] Re: how do I use the scala repl to inspect a "in java written" actor system.

scala -cp On Monday, June 29, 2015 at 11:58:14 AM UTC+3, john@gmail.com wrote: > > Sorry that I know so little about scala. > I have written a java akka system which uses maven for dependeny > management. > > I would now like to inspect my configuration (Typesafe Config Library >

[akka-user] akka-http/spray REST API documentation?

Looks like there's something for spray: http://github.com/gettyimages/spray-swagger I imagine there's nothing for Akka HTTP, seeing as it's not even officially released yet. -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >> http://doc.akka.io/doc

[akka-user] Performance question

The general answer similar questions usually get here is that you'll have to measure, but here are a few comments: 1. I'd check what's causing these spikes. The usual suspect is GC. 2. You didn't mention what handling such a request means. Optimally with 2 cores you have 2000ms per second worth

[akka-user] Akka dispatcher threads get deadlock on log4j classloading

It can be due to a variety of reasons, but there's an implicit lock when loading classes and tools that instrument byte codes can sometimes hit this. Can you post the entire thread dump? Usually it's very easy to pin point the deadlock from thrrad dump. -- >> Read the docs: http://

[akka-user] Setting akka log level from log4j

I've worked around this by starting an actor that polls a regular slf4j logger and then changes the akka log level at run time through the event bus. It works well enough, although it means selective log levels still incur a high overhead, regardless of logging frequency and it also means that e

[akka-user] Re: Setting akka log level from log4j

https://gist.github.com/adamhonen/8863088641df095cce96 Here, I hope that helps. On Tuesday, August 25, 2015 at 11:52:18 AM UTC+3, Dennis Jönsson wrote: > > > > Den måndag 24 augusti 2015 kl. 18:58:26 UTC+2 skrev Adam: >> >> I've worked around this by starting an act

Re: [akka-user] Can Akka actors deadlock?

What kind of web container (if any are you using)? I'd say using ask and blocking on it is still an improvement with pre 3.0 servlets. With asynchronous servlets you can push the AsyncContext down in a message or use as in the ask future's onComplete callback. With other frameworks (Netty, Jet

[akka-user] Re: system.scheduler.scheduleOnce consumes Heap over time

You can easily check what Roland suggested. 1. Setup the frequency of the scheduling to be very fast so memory will grow quickly. 2. connect with visualvm\jconsole to the jvm and initiate gc manually. 3. Compare the trend of memory of the moments right *after the GC* and see if it

[akka-user] Creating a reconnecting TCP client

Hi, I've been looking for a way to create a client that upon disconnection will try to reconnect. I've done this in the past with RxJava observables, but I'm not sure how to do this using Akka Streams. I saw some code examples where PushStage is being used to implement this, but the code sampl

[akka-user] Re: Proposed major simplification of the Akka Streams FlowGraph APIs

, which is already not trivial (at least in my eyes as compare it to RxJava\RxScala). Usually having less options can make things simpler, but in this case I know I’ve used the addEdge method in order to try and make sense of how to use the Akka streams DSL. Adam On Saturday, October 17, 2015 at

Re: [akka-user] Re: Behavior of Akka when you sleep in an actor

I don't understand the purpose of "keeping the actor busy". Why not use the actor system's scheduler in order to implement the delay? Do you actually want to use CPU or other resources? The only thing to pay attention to is that the scheduler, has a certain precision, so the delay may turn out t

Re: [akka-user] Modeling synchronous startup behavior

Hi, In my system I have an initialization sequence that must take place at a certain order. Basically I don't want to open my system for incoming requests, before all services are properly started. So what I needed is sort of similar to what you describe here. I've implemented it without ask. W

Re: [akka-user] ActorSelection vs ActorRef

But that is not really accurate, isn't it? When restarted the ActorRef is still perfectly valid and you only need to watch actors in case you have reason to believe that they will be terminated. Also, messages don't get lost during the restart, because the mailbox isn't restarted (well messages

[akka-user] OutOfMemoryError due to too much logging

Hi, I sometimes see this issue where I want to switch logs to DEBUG, but due to the large number of messages the JVM will crash on OutOfMemory which turns out to be due to the accumulation of logging events. Most logging frameworks have the ability to drop messages beyond a certain number and s

[akka-user] Re: OutOfMemoryError due to too much logging

C on my own. Probably not that much work anyway. Thanks! On Monday, December 14, 2015 at 10:53:13 AM UTC+2, Johan Andrén wrote: > > Hi Adam, > > I think what you are describing is covered in the logging docs: > http://doc.akka.io/docs/akka/2.4.1/scala/logging.html#Loggers and &

[akka-user] Rejections in Akka HTTP Java API

Hi, I see Rejections are only described in the Scala version of the docs. Is that on purpose? What are my options using the Java API in order to customize rejections? -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >> http://doc.akka.io/docs/akka/cu

[akka-user] Akka HTTP performance for short lived connections

Hi, I'm wondering if there's an expected (even rough) date for when Akka HTTP will have similar (or hopefully better :-) ) performance as other HTTP libraries\frameworks like Spray or Play. Specifically, I'm more interested in the scenario of short lived connections, which I remember was said t

Re: [akka-user] Akka HTTP performance for short lived connections

OK, thanks. So just to be certain - in the meantime, is it expected that I'll see Akka HTTP perform ~100 times worse (or let's just say "much worse") than Play framework for such cases? I was hoping it's actually something that I'm doing wrong because I was expecting it to be worse per the REA

[akka-user] Re: Akka HTTP performance for short lived connections

Sure. I first did one round of 100k requests and then another. These are the results of the second round: ab -c 400 -n 10 -m GET http://localhost:3000/hello?name=Bob This is ApacheBench, Version 2.3 <$Revision: 1706008 $> Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeuste

Re: [akka-user] Re: Akka HTTP performance for short lived connections

> the current akka-http version is to disable autoFusing (which is pretty >>> costly). That can be done when you create the materializer like this: >>> >>> >>> ActorMaterializer(ActorMaterializerSettings(system).withAutoFusing(false)) >>> >>&g

Re: [akka-user] Re: Akka HTTP performance for short lived connections

t 1 second for the fastest requests. On Tuesday, April 19, 2016 at 12:25:24 AM UTC+3, Adam wrote: > > Yeah, no code is rather silly really... > > I've created this repository: > > https://github.com/adamhonen/Akka-Http-performance-test > > I didn't get a chance to

[akka-user] Akka HTTP documentation about asynchronous completion of routes

e hard to easily find what to do. Adam. -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >&

[akka-user] Re: Akka HTTP documentation about asynchronous completion of routes

int times) { ... On Monday, September 5, 2016 at 5:28:19 PM UTC+3, Adam wrote: > > Hi, > > I'm looking at the docs trying to find an example of how to create a route > that does not complete the result synchronously from the route tree, but > rather relies on some oth

[akka-user] Akka HTTP performance in 2.4.9

ab -c 400 -n 10 -m GET http://127.0.0.1:3000/ This is ApacheBench, Version 2.3 <$Revision: 1706008 $> Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/ Licensed to The Apache Software Foundation, http://www.apache.org/ Benchmarking 127.0.0.1 (be patient) Completed 100

Re: [akka-user] Akka HTTP performance in 2.4.9

Thanks! Adding -k indeed fixes this right away: ab -k -c 400 -n 10 -m GET http://127.0.0.1:3000/ This is ApacheBench, Version 2.3 <$Revision: 1706008 $> Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/ Licensed to The Apache Software Foundation, http://www.apac

[akka-user] Enjoying Akka HTTP performance

Hi, I'd just like to share my satisfaction from Akka HTTP performance in 2.4.10. I'm diagnosing some low level Node.js performance issues and while running various tests that only require the most basic "Hello World" style code, I decided to take a few minutes to check how would Akka HTTP handle

[akka-user] foreach in akka-streams 0.7

ch is a Sink type now", which I don't really understand :). Is there some different way to implement foreach? (the foreach usage I have is to handle connections from stream-tcp) Thanks, Adam -- >>>>>>>>>> Read the docs: http://akka.io/docs/ &g

Re: [akka-user] foreach in akka-streams 0.7

Got it, thanks! Updated the code :) Adam On Wednesday, September 17, 2014 2:50:23 PM UTC-7, Konrad Malawski wrote: > > Hello Adam, > yes, there is: .withSink(ForeachSink(el => ).run() > ​ > The sink also holds a future which you can watch for completion, see: > http:/

Re: [akka-user] Realtime (as in Electronics) processing in Akka and Garbage Collection's Effect to It

st) > > I have checked out my application with jHiccup (which Adam suggested) > running for a day and it seems that the highest hiccup duration is 65 > milliseconds. It is acceptable for my application ( but it will not be, if I > try to implement the realtime part I was asking for ) A frie

[akka-user] Stopping a reactive stream

supervisor hierarchy" for the stream. -- Thanks, Adam -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/f

Re: [akka-user] Stopping a reactive stream

On Thursday, October 30, 2014 11:15:50 AM UTC+1, Akka Team wrote: > > Hi Adam, > > This might or might not be associated with the components of the stream >> itself; in my current scenario I have a sink which is a reactive tcp >> connection. >> > >

Re: [akka-user] Stopping a reactive stream

Sure :) I'm using streams 0.9, scaladsl2 and I want to add failure detection to that: https://github.com/adamw/reactmq/blob/master/src/main/scala/com/reactmq/Sender.scala Adam On Thursday, October 30, 2014 12:04:23 PM UTC+1, Akka Team wrote: > > Hi Adam, > > >> I'

Re: [akka-user] Stopping a reactive stream

sink1 (output stream) source --> trans1 --> broadcast --< \---> sink2 (on complete drain) Will the failure of sink1 propagate to a completion of the whole stream? In theory it could continue in a "crippled" way (with only on

Re: [akka-user] Stopping a reactive stream

> On Thu, Oct 30, 2014 at 1:43 PM, Adam Warski > wrote: > >> There's an OnCompleteDrain :) (btw. - sink, drain, subscriber - a lot of >> names ;) ) >> > > Drain is no longer there (as a name at least) and you should usually not > see a Subscriber ;)

Re: [akka-user] Stopping a reactive stream

ant to return) of their own > that is completely library dependent -- for example a file writer Sink can > give a Future that represents the event while the file has been completely > closed. > So each sink should provide a sink-dependent way of letting the user know when things are

Re: [akka-user] Stopping a reactive stream

gt; Sure, this makes sense. Having as little of an additional protocol as possible is certainly nice. Though the fact that a socket died doesn't always require protocol support (I mean, often you will know that a socket isn't working without sending special pings or such). So this coul

[akka-user] Reactive actor-actor communication

he A-actors. Or maybe the direction I'm heading with this is somehow wrong? :) Adam -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io

Re: [akka-user] Reactive actor-actor communication

each consumer to a number of partitions, so it would be as you describe, kind of point-to-point streams, which get re-balanced when a node goes down. Going this route, there could be a cluster-singleton service which assigns B-actors to A-actors, and creates streams between those two. These

Re: [akka-user] Reactive actor-actor communication

I opened GH issues and I see Konrad beat me to it: https://github.com/akka/akka/issues/16348 :) Adam On Wednesday, November 19, 2014 8:36:41 AM UTC+2, rkuhn wrote: > > Hi Adam, > > your initial point of creating a growing (and maybe thundering) herd of > retries is a good one

Re: [akka-user] Reactive actor-actor communication

"reactive message streams" from above. And to solve the >>> demand-splitting problem (when a B has two As assigned), there could be >>> simply more consumer-actors then producer-actors. >>> >> This sounds like a very interesting use case. > Would be awesome if

Re: [akka-user] Reactive actor-actor communication

g tokens over the network. > So as I understand back-pressure is implemented as described here: http://doc.akka.io/docs/akka/2.3.7/scala/io-tcp.html (with propagation to the writer side by using TCP buffers), right? If the subscriber doesn't generate demand, this

[akka-user] [streams 1.0-M1]

r.scala#L34 Any thoughts? :) Adam -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>&

[akka-user] Re: [streams 1.0-M1]

Seems I forgot to actually write the title, sorry ;) It should be sth like "No-element never-completed source" Adam On Thursday, December 11, 2014 11:33:42 AM UTC+1, Adam Warski wrote: > > Hello, > > I'm migrating to the latest streams, the new client-server stream tc

Re: [akka-user] Re: [streams 1.0-M1]

Done, issue added: https://github.com/akka/akka/issues/16547 Adam On Monday, December 15, 2014 12:16:17 PM UTC+1, Björn Antonsson wrote: > > Hi Adam, > > Yes, that seems to bit awkward. And yes that part of the TCP API also > feels a bit backwards. I think that we need to revis

[akka-user] [akka-streams] Duplicator example from the docs

I would expect it to have a default buffer of awaiting elements? Adam -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/curre

[akka-user] [cluster] minimum number of members and cluster-singleton

ller number than the setting alive), the singleton starts up anyway). Adam -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/curr

Re: [akka-user] [cluster] minimum number of members and cluster-singleton

scenario If I get some free time I'd be happy to work on the issue, I assume master is a good starting point? Adam On Friday, January 2, 2015 3:58:37 PM UTC+1, Patrik Nordwall wrote: > > Hi Adam, > > We have been thinking that this should be handled with a "smarter" dow

Re: [akka-user] [akka-streams] Duplicator example from the docs

Ok, if there's only one ball, that answers the question. Thanks! :) Adam On Thursday, January 1, 2015 10:00:27 AM UTC+1, Akka Team wrote: > > Hi Adam, > > PushPull stage callbacks are never concurrent. Also, if a stage calls > ctx.Push then it will receive eventually an onP

[akka-user] akka-http underlying threading

ually gets down to that same point. Is this the plan going forward, or perhaps is there some other strategy that will be used? [0]: https://groups.google.com/forum/#!topic/spray-user/avYhEFYsvcg -- Adam Shannon | Software Engineer | Banno | Jack Henry 206 6th Ave Suite 1020 | Des Moines, IA 50

Re: [akka-user] akka-http underlying threading

feb 2015 kl. 20:50 skrev Adam Shannon : > > This thread in spray-user [0] got me curious about akka-http's current and > future usage of the low level mechanisms. I'm not very familiar with > akka-io underpinnings, but does it use a similar single thread for even > notifica

[akka-user] Re: What are some suggestions for building a GUI for an Akka app?

Swing by Arnost Valicek<http://stackoverflow.com/users/458832/arnost-valicek> . http://stackoverflow.com/questions/15203758/asynchronous-ui-update-with-swing#15218597 -- Adam Mackler -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>&g

[akka-user] Documentation suggestion regarding Swing

tion in a trail of documentation that begins in what might be the most commonly-used introductory text on the Scala language. Thanks, -- Adam Mackler -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ:

Re: [akka-user] Documentation suggestion regarding Swing

Actor*. What is that? -- Adam Mackler -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: http://akka.io/faq/ >>>>>>>>>> Search the archives: https://groups.google.com/

Re: [akka-user] New Android app that uses Akka

tions your app can expect while operating on the road with the drivers. -- Adam Mackler -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: http://akka.io/faq/ >>>>>>>>>>

[akka-user] StackOverflow with long actor path name.

names? https://gist.github.com/adamdecaf/8790506 -- Adam Shannon Software Engineer University of Northern Iowa Senior -- Computer Science & Mathematics http://ashannon.us -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>&g

Re: [akka-user] StackOverflow with long actor path name.

The name should be short and to the point, it's not a place to put a > base64-encoded payload (or worse ;)) > > > On Mon, Feb 3, 2014 at 8:24 PM, Adam Shannon wrote: > >> Hello all, >> >> I've found out that I can get a StackOverflow exception when creating a

Re: [akka-user] StackOverflow with long actor path name.

e to not only fix the regex if possible, but > also put a reasonable cap on the name length to make sure that the paths > are representable as strings? > > > On Mon, Feb 3, 2014 at 8:34 PM, Adam Shannon wrote: > >> That's the route we're going to use now. W

[akka-user] Props Factory

I've been trying to use the recommended factory method for defining props as indicated here: http://doc.akka.io/docs/akka/2.2.3/scala/actors.html I tried it on my own class and it failed with the same type mismatch as seen below, so I went straight to the demo code using two definitions for pr

[akka-user] [akka-streams]: actor producers, load balancers

e naturally, maybe even more than in locally), but do you plan to develop this somehow? E.g. when there would be multiple consumers for a single producer, a useful component would be a load-balancer which takes into account the backpressure information. Thanks! -- Adam -- >>>

Re: [akka-user] [akka-streams]: actor producers, load balancers

On Friday, May 23, 2014 4:57:32 PM UTC+2, Konrad Malawski wrote: > > Cześć Adam :-) > > > - is it reasonable (thinking about reactive streams in general) to have an > actor which produces elements on-demand (instead of providing a > collection/iterator/() => as is curr

Re: [akka-user] [akka-streams]: actor producers, load balancers

> Stay tuned. > Right, I was thinking about a Future-based producer initially as well (I could then use ? to get the data from the actor), but then I thought it would be actually more efficient if I knew how many elements I can produce in the actor. Adam -- >>>>>>>>&g

Re: [akka-user] [akka-streams]: actor producers, load balancers

h make implementing these > easier, but I'm not aware of plans of exposing them any time soon - for > starters we need to update akka-streams to the updated reactive-streams > interfaces. > I see, but then I have to implement the subscription management etc myself - which I gu

  1   2   >