Re: [akka-user] java.lang.VerifyError after shading with sbt-assembly

Hm, what version of the JVM has this been tested on? -Endre On Mon, Feb 6, 2017 at 2:40 AM, Manu Zhang wrote: > Hi, > > We(Gearpump) are recently seeing *java.lang.VerifyError* after shading > with sbt-assembly as in https://github.com/akka/akka/issues/21596 > >

Re: [akka-user] Re: [Akka-streams] Cannot push port twice

On Mon, Jan 9, 2017 at 3:03 PM, Sergey Sopin wrote: > Hi again, > > In my case I have 1 inlet and 2 outlets. It seems that inlet port can be > pulled only once. > Yes, this is clearly documented here:

Re: [akka-user] Strange behavior with unzip when fusing is on

is effectively a buffer, so you'll need a buffer > in front of zip.in0 as well to enable parallelism. > > Regards, Roland > > Sent from my iPhone > > On 21 Dec 2016, at 09:34, Endre Varga <endre.va...@lightbend.com> wrote: > > > > On Tue, Dec 20, 2016 a

Re: [akka-user] Strange behavior with unzip when fusing is on

On Tue, Dec 20, 2016 at 11:34 PM, Anil Gursel wrote: > I see that unzip does not pull the next element when fusing is on. I > understand that when fusing is on, a message goes through the entire stream > and then the next message goes through. > This is not true, messages

Re: [akka-user] Re: Initial message when attached to a BroadcastHub

On Sat, Dec 17, 2016 at 3:55 AM, oleksiys wrote: > Hmm, I dynamically create a sub-stream as a reaction to a certain stream > event, so not sure how exactly alsoTo can help here. > Ok, so that is a different problem. You are basically trying to reimplement splitWhen (or maybe

Re: [akka-user] Re: Initial message when attached to a BroadcastHub

Why use Hub for this? There is a race when the actual side-channel is attached, hence it can miss some of the initial elements. You can either just use normal broadcast or the combinator alsoTo. On Fri, Dec 16, 2016 at 12:22 AM, oleksiys wrote: > I'll try to give more context,

Re: [akka-user] What's wrong with value classes as parameters?

stand these nooks and crannies -- thanks for clearing it up! > No problem :) -Endre > > On Thu, Dec 15, 2016 at 9:11 AM, Endre Varga <endre.va...@lightbend.com> > wrote: > >> I also recommend this section in the doc: http://doc.akka.io/docs/a >> kka/2.4/scala/actors.html

Re: [akka-user] What's wrong with value classes as parameters?

I also recommend this section in the doc: http://doc.akka.io/docs/akka/2.4/scala/actors.html#Edge_cases On Thu, Dec 15, 2016 at 3:08 PM, Justin du coeur wrote: > Huh -- actually, this one surprises me, so I'd like to poke at it. I > understand why your response works, but

Re: [akka-user] Aeron errors when network temporarily disconnected.

Have you tried 2.4.14? Please always try the latest bugfix release before reporting bugs. The issue might have been fixed before and it is a waste of time to try to find non-existing bugs. -Endre On Wed, Dec 14, 2016 at 1:44 AM, Allan Brighton wrote: > Using akka-2.4.11 on

Re: [akka-user] How to deal with Futures in Sources/Flows

On Fri, Dec 9, 2016 at 7:31 PM, wrote: > I thought I needed to use a GraphStageLogic because I need to do the > following: > > request url for page of data and push > if response has next token, grab another page and push > continue until no next token > complete the stream >

Re: [akka-user] min-nr-of-members not getting applied

.. and, please always use the latest version, which is 2.4.14 in this case. On Fri, Dec 9, 2016 at 3:19 PM, Konrad Malawski < konrad.malaw...@typesafe.com> wrote: > Hi Richard, > no, nothing special other than setting this. > > Some questions to help debugging this: > - are you joining the nodes

Re: [akka-user] How to deal with Futures in Sources/Flows

On Thu, Dec 8, 2016 at 9:21 PM, wrote: > Hi, > > I'm creating a Source via GraphStageLogic which makes calls to another > api, which happens to return a Source. However I'm unsure how to deal with > Source/Futures in a GraphStageLogic. It seems that I want my shape to look >

Re: [akka-user] invalid materialized value

Yes, this is a bug. I filed a ticket: https://github.com/akka/akka/issues/21955 On Tue, Dec 6, 2016 at 10:39 AM, Endre Varga <endre.va...@lightbend.com> wrote: > Hi Stefan, > > What version are you using? This might be a bug. > > -Endre > > On Tue, Dec 6, 2016 at

Re: [akka-user] invalid materialized value

Hi Stefan, What version are you using? This might be a bug. -Endre On Tue, Dec 6, 2016 at 10:13 AM, EXTERNAL Wachter Stefan (Keybird IT Consulting und Vetriebs GmbH, INST-ICM/BSV-BS) < external.stefan.wach...@bosch-si.com> wrote: > Hi all, > > > > the following line of code > > > > > > *val

Re: [akka-user] [Streams 2.4.14] Custom Stream Processing - Elasticsearch Sink

Hi Isaias, Such callbacks can be handled by the AsyncCallback support in stages: http://doc.akka.io/docs/akka/2.4/scala/stream/stream-customize.html#Using_asynchronous_side-channels In general, I recommend looking at our blog which has a series about custom GraphStage building, in particular I

Re: [akka-user] Akka-remoting with Artery using load balancing/round robbing dns

Actor remote messaging is a P2P protocol and as such any kind of name-remapping is harmful. Trying to load balance Akka Remote connections I think is a mistake and makes not much sense. You *can* load balance Akka provided services of course, but you need to expose them as a different protocol

Re: [akka-user] Why default-plugin-dispatcher is PinnedDispatcher thread-pool-executor ?

Because there is no reason for a FJP executor. PinnedDispatcher dedicates a thread to an actor, there is no sharing and hence no work stealing. FJP is overkill in that case and makes no sense. -Endre On Thu, Nov 10, 2016 at 12:41 PM, Yaroslav Klymko wrote: > Hi guys, > > Just

Re: [akka-user] Re: New to Akka, newbie to high scale server programming

There are new introductory docs in the works. I hope we can get some of them online before Christmas (even if in a beta shape). Until then, the old docs are great as a reference, but admittedly not as friendly to newbies as they could be. Nevertheless, you will find everything in there. -Endre

Re: [akka-user] How to Use BroadCastHub as a GraphState in Akka standard graph stage

Hi, You have not added your Source to the Graph, so it will not work. You need b.add() to import things into the graph to wire them up. -endre On Fri, Oct 28, 2016 at 12:39 PM, auxdx wrote: > Hi, > > I am wondering why this code does not work as intended: > > def

Re: [akka-user] Memory Bounding Akka Streams

On Thu, Sep 29, 2016 at 1:41 AM, Dagny Taggart wrote: > > > LATEST updated understanding I have then is the following; and if someone > could PLEASE correct my (Newbie) understanding with a link to a clear Blog > Post or GitHub repo illustrating the concept! > > 1) The

Re: [akka-user] Scala Akka Alignment

Also, why not the latest version 2.4.10? On Wed, Sep 21, 2016 at 1:19 AM, Konrad Malawski < konrad.malaw...@lightbend.com> wrote: > You can see which version of Scala an Akka artifact is released for by > looking at the artifact names: >

Re: [akka-user] Source from Sink

Isn't that just simply: requests.via(outgoingHttpConnection).flatMapConcat { resp => resp.dataBytes } ? On Tue, Sep 20, 2016 at 4:42 PM, Victor wrote: > Sorry for the spam. To make it simple, what I really want to achieve is to > have a continuous flow of

Re: [akka-user] Akka Streams - Source.map vs Source.via(flow)

Hi Ori, The reason is if you have longer, reusable chains of computations then you can factor them out into a Flow. For example if you have a more complex chain handling some deserialization and domain object mapping then you can express it once and then just include it multiple times into other

Re: [akka-user] Embed a Flow in a GraphStage?

Even simpler newFlow = flow join bidiFlow or newFlow = bidiFlow join flow On Thu, Sep 1, 2016 at 10:23 AM, Victor wrote: > Ah I see :) Something like this: > > ... -> BidiFlow.port1 -> EmbededFlow -> BidiFlow.port2 -> ... > > Thanks, > Victor > > Le jeudi 1 septembre

Re: [akka-user] Embed a Flow in a GraphStage?

Hi Victor, Embedding is not the way to think about this. What you really want is a BidiStage which then can be composed by any Flow to get a new Flow. -Endre On Thu, Sep 1, 2016 at 10:12 AM, Victor wrote: > Hi, > > Is it possible to embed a Flow in a GraphStage? > >

Re: [akka-user] Re: How can I convert a listener pattern into a stream with akka streams?

I am not sure a simple listener pattern warrants a full Akka Stream to be involved. Streams starts to shine when you need backpressure, but if you don't need any (because events are rare, or there is no way to meaningfully backpressure) then it might be just too heavyweight and lead to

Re: [akka-user] Delay within GraphStageLogic

On Sat, Aug 27, 2016 at 12:44 AM, Gary Struthers wrote: > Sorry, my onTimer() doesn't fire. > That would be surprising given that all of the built-in time based operators are implemented in terms of this. > It looks like all I need to do is 1. use TimerGraphStageLogic

Re: [akka-user] Delay within GraphStageLogic

Hi Gary, On Fri, Aug 26, 2016 at 6:17 PM, Gary Struthers wrote: > Thanks Konrad, but I posted because I tried scheduleOnce and got no delay > > scheduleOnce(logger.debug("1 currentTimeMillis {}", System. > currentTimeMillis()), FiniteDuration(100, MICROSECONDS)) > >

Re: [akka-user] How to join three streams but output only when one emits an object?

Hi Mark, On Thu, Aug 25, 2016 at 2:48 PM, Mark Hammons wrote: > I want to zip three streams together and form a class which will be output > to a sink. > That is so far a ZipWith > however, this class should only be emitted when the first stream emits an > item,

Re: [akka-user] Binding Actors to CPU or to a core

> It's using native code. > > /Patrik > > On Tue, Aug 23, 2016 at 9:15 AM, Endre Varga <endre.va...@lightbend.com> > wrote: > >> Hi Mahesh, >> >> Unfortunately there is no way to set CPU affinity for a Java thread from >> the JVM. You can probably build a

Re: [akka-user] Binding Actors to CPU or to a core

Hi Mahesh, Unfortunately there is no way to set CPU affinity for a Java thread from the JVM. You can probably build a native library that you can call into via JNA. -Endre On Tue, Aug 23, 2016 at 5:13 AM, Mahesh Govind wrote: > Dear Experts, > > Is it possible to bind a

Re: [akka-user] Cluster Metrics on Windows

Hi Chris, Thank you for all this, very valuable information! Can you please file a ticket on the repo for further discussions to not have this accidentally lost? -Endre On Sun, Aug 21, 2016 at 1:06 AM, Chris Van Vranken < cessationoft...@gmail.com> wrote: > Someone responded to me in the

Re: [akka-user] Cluster Metrics on Windows

Hi, Which metric collector are you using, the JMX or the SIGAR collector? -Endre On Sat, Aug 20, 2016 at 1:31 AM, cessationoftime wrote: > Using Akka 2.4.9 and Windows 10 I am unable to get CPU cluster metrics, I > can only get HeapMemory metrics. Running the same

Re: [akka-user] Reactive kafka getStageActor exception

This looks like a typical classpath issue. I think you have incompatible versions of some libraries in your classpath. -Endre On Sat, Aug 20, 2016 at 9:30 AM, Lap Ming Lee wrote: > I keep on getting this error when I restart my IntelliJ to run unit test > on my reactive

Re: [akka-user] Router path in Akka config

This looks like where Akka Streams might be a better fit? See this chapter in the streams docs: http://doc.akka.io/docs/akka/2.4/scala/stream/stream-parallelism.html -Endre On Fri, Aug 19, 2016 at 5:27 PM, Mark Kaberman wrote: > In my case single actor may not be fast

Re: [akka-user] [akka-streams] Accessing the dispatcher used for a mapAsync stage

Hi, There is no way to get the execution context inside such a simple operator, unfortunately. Inside a GraphStage you can access the materializer from the logic: http://doc.akka.io/api/akka/2.4/index.html#akka.stream.stage.GraphStageLogic@materializer:akka.stream.Materializer Unfortunately

Re: [akka-user] How to create listener which is placed outside actor system?

Isn't what you want is a simple actor that calls the callback? I.e.: class CallbackActor(callback: Callback) extends Actor { ... def receive = { case msg: MessageA => callback.invoke(msg) } ... } ... callbackInvoker = system.actorOf(callbackActorProps, ...) callbackInvoker ! new

Re: [akka-user] Streams - custom HTTP POST Sink?

On Thu, Aug 11, 2016 at 12:32 AM, Mike Bryant wrote: > Thanks Endre - that's perfect. The prefixAndTail with zero prefix was the > missing ingredient I needed to transform the whole source within a separate > flow (maybe there's a case for adding that as another specific >

Re: [akka-user] Re: How to read XML inputstream (with SAX parser) received by akka-http?

Btw, I am also interested in how it fares on a 5G input, so please tell us how it went. On Wed, Aug 10, 2016 at 9:02 PM, Endre Varga <endre.va...@lightbend.com> wrote: > Hi, > > Christmas is early for you then, since this is exactly what I am working > on: https://github.c

Re: [akka-user] Streams - custom HTTP POST Sink?

> Using Akka HTTP and streams I can take a Source[ByteString, _] and using > it as the body entity for a POST request to some HTTP endpoint, yielding > some response. I'd like to abstract this into an Akka streams *Sink* I > can run with said Source and materialise to, for example, the HTTP status

Re: [akka-user] Akka Stream Getting Stuck (2.4.9-RC2)

Hi, On Wed, Aug 10, 2016 at 10:26 PM, tigerfoot wrote: > For whoever finds this thread and struggles with the same problem... I've > found a solution that fixed it for me. > > implicit val materializer = ActorMaterializer( > ActorMaterializerSettings(system) >

Re: [akka-user] Re: How to read XML inputstream (with SAX parser) received by akka-http?

Hi, Christmas is early for you then, since this is exactly what I am working on: https://github.com/drewhk/akka-xml-stream/pull/1 As you see, it is currently on my private repo, but it will be migrated and donated soon to the akka-stream-contrib project (and will gain an Apache Lincense of

Re: [akka-user] Released Requester 2.4

Nice one! On Tue, Aug 9, 2016 at 4:24 PM, Patrik Nordwall wrote: > Awesome! Thanks for sharing. > > On Tue, Aug 9, 2016 at 3:19 PM, Justin du coeur > wrote: > >> A quick note for those who care: I've just cut a new release of Requester >>

Re: [akka-user] Question about Akka Scaling: Memory

On Tue, Aug 9, 2016 at 5:07 PM, Rob Crawford wrote: > The project home page says "~2.5 million actors per GB of heap" -- > That is sadly outdated, actors now take up more memory. Still, not a drastic difference, the million in magnitude likely holds. > that works out to

Re: [akka-user] Akka Stream Getting Stuck (2.4.9-RC2)

Hi Greg, On Sat, Aug 6, 2016 at 1:11 AM, tigerfoot wrote: > I'm having a nasty issue I hope someone can help me with. > > I have some stream code like this: > > val contentAssembly = Flow[CRec].map { crec => > println("HERE!") > val x =

Re: [akka-user] Akka Cluster (with Sharding) not working without auto-down-unreachable-after

On Fri, Aug 5, 2016 at 12:04 AM, Justin du coeur wrote: > It does do reassignment -- but it has to know to do that. Keep in mind > that "down" is the master switch here: until the node is downed, the rest > of the system doesn't *know* that NodeA should be avoided. I

Re: [akka-user] Unable to receive UDP packets after restarting network interface

Hi, I am not sure what Akka can do about this. We just use the NIO interfaces from the JDK. If we didn't report an error then likely we didn't get one from Java in the first place. I might be wrong of course but I don't really know what we could do here. -Endre On Wed, Aug 3, 2016 at 2:46 PM,

Re: [akka-user] Can't get backpressure to work...

Hi, Your actor code is faulty, you are closing over the actor's state in Future callbacks, namely future.foreach and future.onFailure. This is not thread safe and will fail in various interesting ways. There is not much reason to use an ActorPublisher for this to be honest. There are built-in

Re: [akka-user] Re: Akka Tcp peer to peer architecture instead of client server

On Wed, Jun 29, 2016 at 2:25 AM, Chris Stewart wrote: > It looks like akka is missing messages that are sent microseconds apart. I > Can you please post a test reproducing this issue? Akka TCP exists for more than 3 years now, and Akka Stream and Akka HTTP are built

Re: [akka-user] Re: ANNOUNCE: New Remoting Milestone 2

On Sat, Jun 11, 2016 at 4:01 PM, Guido Medina wrote: > My first try failed, I thought Netty-3 wasn't being used so I excluded it > as it is being pulled by akka-remote artery version, and I got the > following exception: > That is because the old remoting is still included

Re: [akka-user] Re: ANNOUNCE: New Remoting Milestone 2

On Mon, Jun 13, 2016 at 8:53 AM, Guido Medina wrote: > Hi Patrik, > > About performance, it seems to perform worse than the old akka remote, I > usually get averages of 1ms and peaks between 10-20ms: > That is *very* surprising and contradicts our test results on different

Re: [akka-user] HttpServerBluePrint: Cannot push port (requestPrepOut) twice

Yes, this looks like a bug. Can you please file a ticket? On Fri, May 27, 2016 at 10:38 AM, Kyrylo Stokoz wrote: > Hi All, > > > During run of my application which is using akka-streams & akka-http of > v.2.4.6 sometimes i see following error in the logs: > > Error in stage

Re: [akka-user] How do I get connected Inlet and Outlet ? Akka 2.4.6

I would add though, that it is generally not recommended to set the maximumBurst to zero as it is highly inefficient (needs to contact the Scheduler for basically all messages) and for higher rates it has not enough precision. So maximumBurst is also used to be able to compensate for the scheduler

Re: [akka-user] how do i correctly use the Flow.batch?

By putting there an .async you put there a buffer, too. See http://doc.akka.io/docs/akka/2.4.5/scala/stream/stream-rate.html for details. On Thu, May 19, 2016 at 4:05 AM, Yang Yang wrote: > hi ,i changed to async > > implicit lazy val system = ActorSystem("example") >

Re: [akka-user] Call a function on overflow

ah, there is a buffer.isEmpty check before. On Wed, May 4, 2016 at 4:27 PM, Endre Varga <endre.va...@lightbend.com> wrote: > ... and buffer.poll() might return null. > > On Wed, May 4, 2016 at 4:22 PM, Viktor Klang <viktor.kl...@gmail.com> > wrote: > >> And, t

Re: [akka-user] Call a function on overflow

... and buffer.poll() might return null. On Wed, May 4, 2016 at 4:22 PM, Viktor Klang wrote: > And, the Async Callback is not executed concurrently with the graphstage > so no need for the AtomicBoolean, no? > > On Wed, May 4, 2016 at 4:14 PM, Johan Andrén

Re: [akka-user] What are the correlation between ByteString in Akka Streams TCP packet payloads?

Yes, this is a simple approach and works without having to do a custom stage (exactly why statefulMapConcat was introduced). -Endre On Wed, Apr 20, 2016 at 4:03 PM, Derek Williams wrote: > If it helps, a simple custom framing stage could look like this: > >

Re: [akka-user] Re: Connect two TCP sockets

You can use Sink.queue to get a future based queue API that is backpressured. Then you can just combine with mapAsync on the sockets side to get backpressured merges. Not exactly the same as Hub would work, but already works for this simple case. -Endre On Wed, Apr 20, 2016 at 10:05 AM, Johan

Re: [akka-user] Re: ActorSystem.terminate() couldn't fully terminate the system

Threads from the pool are released after a timeout. You can make them daemonic if you want via configuration. -Endre On Mon, Apr 18, 2016 at 10:02 PM, Yan Pei wrote: > John, > > After I upgrade AKKA to 2.4.4 and AKKA persistence cassandra to 0.12, > the system.terminate()

Re: [akka-user] Akka streams: stage that combines consecutive elements

True, I missed that option. On Tue, Apr 12, 2016 at 11:37 AM, Roland Kuhn <goo...@rkuhn.info> wrote: > Well, you could also concat an EOF marker and use that to flush … > > 12 apr 2016 kl. 11:33 skrev Endre Varga <endre.va...@lightbend.com>: > > No, for that you n

Re: [akka-user] Akka streams: stage that combines consecutive elements

> > - Arno > > Am 12.04.2016 um 09:27 schrieb Endre Varga: > > Hi Arno, > > > > statefulMapConcat is likely what you need. If that does not work, then > > build a custom stage. > > > > -Endre > > > > On Mon, Apr 11, 2016 at 8:09 PM

Re: [akka-user] Akka streams: stage that combines consecutive elements

Hi Arno, statefulMapConcat is likely what you need. If that does not work, then build a custom stage. -Endre On Mon, Apr 11, 2016 at 8:09 PM, Arno Haase wrote: > I have a Source of element type A, and I am looking for a way to build a > stage combining

Re: [akka-user] What are the correlation between ByteString in Akka Streams TCP packet payloads?

Hi Magnus, On Sat, Apr 9, 2016 at 11:00 PM, Magnus Andersson wrote: > Hi > > I'm implementing a TCP protocol (Lumberjack2/Beats) in Akka Streams. It is > a streaming application level protocol where each messages varies data > length. In Akka streams I get ByteStrings

Re: [akka-user] Akka HTTP bind exception on Windows

But first, please file a ticket! On Fri, Apr 8, 2016 at 11:24 AM, Viktor Klang <viktor.kl...@gmail.com> wrote: > And to clarify, by "we", anyone reading this or the Issue is eligible for > fixing it :) > > On Fri, Apr 8, 2016 at 10:11 AM, Endre Varga <endre.va...@

Re: [akka-user] Akka HTTP bind exception on Windows

, please file a ticket. Strange that it >>>>> works on non-Windows though :( (we have test for the behavior) >>>>> >>>>> >>>>>> >>>>>> My problem is that I am running out of time. Our customer is getting >>&

Re: [akka-user] Akka HTTP bind exception on Windows

gt;> >>> >>> Thanks, >>> Michael >>> >>> On Tuesday, April 5, 2016 at 6:34:26 PM UTC+2, drewhk wrote: >>>> >>>> Have you tried to add a configuration (ServerSettings) when you bind >>>> the TCP which enables the Reus

Re: [akka-user] Akka HTTP bind exception on Windows

ed to add a configuration (ServerSettings) when you bind the >> TCP which enables the ReuseAddress ( >> http://doc.akka.io/api/akka/2.4.3/#akka.io.Inet$$SO$$ReuseAddress) >> option? >> >> -Endre >> >> On Tue, Apr 5, 2016 at 6:29 PM, Endre Varga <endre...@lightben

Re: [akka-user] Akka HTTP bind exception on Windows

Have you tried to add a configuration (ServerSettings) when you bind the TCP which enables the ReuseAddress ( http://doc.akka.io/api/akka/2.4.3/#akka.io.Inet$$SO$$ReuseAddress) option? -Endre On Tue, Apr 5, 2016 at 6:29 PM, Endre Varga <endre.va...@lightbend.com> wrote: > But that

Re: [akka-user] Akka HTTP bind exception on Windows

But that code uses SO_REUSEADDR. -Endre On Tue, Apr 5, 2016 at 5:50 PM, Michi wrote: > Hi Endre, > > I wrote a small test program that creates a socket channel, closes it and > creates another one using the same port: > > import java.io.IOException; >

Re: [akka-user] Akka HTTP bind exception on Windows

On Tue, Apr 5, 2016 at 5:04 PM, Michi wrote: > Hi Endre, > > even after 10 Minutes TCPView shows that the socket is still bound by > jawaw.exe. If I close the application, the socket gets unbound immediately. > That's why I am wondering if I do something

Re: [akka-user] Akka HTTP bind exception on Windows

Hi, As far as I know event though NIO reports the unbind, unbinding on Windows is not immediate and you are not guaranteed to be able to bind again immediately. I don't know if this comes from Windows or the NIO windows drivers though. -Endre On Tue, Apr 5, 2016 at 2:05 PM, Michi

Re: [akka-user] Scheduler onReceive method called twice in a row but registered once

Hi, Akka 2.2 is an ancient version, almost 3 years old and it is not supported at all. 2.2.5 is the last version of that line. If you want support for these versions you need commercial support subscription. -Endre On Tue, Apr 5, 2016 at 12:35 PM, Aurélien Panhaleux wrote:

Re: [akka-user] ANNOUNCE: Akka Stream and Http 2.0.4 released!

(This release is for Akka 2.3.x series, for those on Akka 2.4 check out the latest Akka 2.4.3 release) On Fri, Apr 1, 2016 at 6:44 PM, Martynas Mickevičius < martynas.mickevic...@lightbend.com> wrote: > Dear Hakkers, > > we—the Akka committers—are happy to announce the fourth maintenance >

Re: [akka-user] ANNOUNCE: Akka 2.4.3 released!

Yay! On Fri, Apr 1, 2016 at 6:37 PM, Konrad Malawski wrote: > ANNOUNCE: Akka 2.4.3 Released > > Dear hakkers, > > we—the Akka committers—are proud to announce the third patch release of > Akka 2.4. > > This release focused mostly on hardening and polishing of existing >

Re: [akka-user] [reactive-kafka 0.9.0.1] Why is my use of reactive-kafka so slow on commit?

Also, what version of streams is this? There is no reason why the stream version could not produce 6 figure numbers, so something else is going on. Have you profiled it? -Endre On Fri, Apr 1, 2016 at 1:12 PM, Viktor Klang wrote: > Hi Greg, > > I don't know why the

Re: [akka-user] Akka on Android: akka.actor.ActorInitializationException

>From the failed resolution I would guess that one Flink actor tries to instantiate something JMX related which is not available on Android. -Endre On Fri, Apr 1, 2016 at 11:04 AM, Viktor Klang wrote: > Hi Luca, > > check the stack trace of the

Re: [akka-user] postStop doesn't get invoked after actor initialization failure

t; >> Interestingly, I have never pondered these semantics in this light >> before, thanks for the discussion! >> >> Regards, >> >> Roland >> >> PS: changing this behavior is indeed not trivial since nulling out the >> actor field is required for prope

Re: [akka-user] akka 2.4.2 [java] stopping http-server and flow handling IncomingConnection

Or wait until 2.4.3 and use the KillSwitch feature, as it was mentioned before: 1. unbind server 2. wait until grace period, then trigger KillSwitch.shutdown or abort 3. shut down ActorSystem -Endre On Fri, Apr 1, 2016 at 11:33 AM, Viktor Klang wrote: > Call 'shutdown'

Re: [akka-user] Re: Akka HTTP Websockets Java with Actor

On Thu, Mar 31, 2016 at 4:08 PM, Alan Klikic wrote: > Hi all, > > Sink sink = Flow.create() > .map((msg) -> new Incoming(msg.asTextMessage().getStrictText())) >* .to(Sink.actorRef(actor, PoisonPill.getInstance()));* > > Can you please explain

Re: [akka-user] postStop doesn't get invoked after actor initialization failure

nit fails >>>> - init; preStart (fails)?; postStop (fails)? >>>> >>>> The above contract is basically: "If initialization succeeds, preStart >>>> and postStop are attempted to be called eventually, independently of thrown >>>> exceptions&q

Re: [akka-user] postStop doesn't get invoked after actor initialization failure

tStop >> even if preStart throws. >> >> -Endre >> >> >> >> On Thu, Mar 31, 2016 at 2:41 PM, Viktor Klang <viktor...@gmail.com> >> wrote: >> >>> PostStop would never be called if the constructor fails. Which could be >>> s

Re: [akka-user] postStop doesn't get invoked after actor initialization failure

> > -- > Cheers, > √ > On Mar 31, 2016 2:39 PM, "Endre Varga" <endre.va...@lightbend.com> wrote: > >> >> >> On Thu, Mar 31, 2016 at 2:36 PM, Guido Medina <oxyg...@gmail.com> wrote: >> >>> it gets worse if I failed starting "

Re: [akka-user] postStop doesn't get invoked after actor initialization failure

code from Akka calling postStop...see my point? >>>> >>> >>> Nope, Akka should just swallow the double-fault at that point. I still >>> think it should at least attempt to call postStop() to mitigate resource >>> leaks. >>> >>> -Endre >>

Re: [akka-user] postStop doesn't get invoked after actor initialization failure

t attempt to call postStop() to mitigate resource >> leaks. >> >> -Endre >> >> >>> >>> Guido. >>> >>> On Thursday, March 31, 2016 at 9:19:15 AM UTC+1, drewhk wrote: >>>> >>>> That description suits me ;) >>>> &g

Re: [akka-user] postStop doesn't get invoked after actor initialization failure

<patrik@gmail.com> >> wrote: >> >>> From the source: "Only change this if you're very confident and lucky" >>> :-) >>> >>> On Thu, Mar 31, 2016 at 9:30 AM, Endre Varga <endre...@lightbend.com> >>> wrote: >>> >

Re: [akka-user] Akka Streams and Async buffering

On Thu, Mar 31, 2016 at 12:35 PM, wrote: > Thanks Endre, > > Without using the async though the stream locked up, which i had thought > was due to running it in one stream. > You should investigate that deadlock there. Maybe blocking calls? > Using a feedback loop

Re: [akka-user] Akka Streams and Async buffering

Hi Robin, As a very first step I would recommend reading this section: http://doc.akka.io/docs/akka/2.4.2/scala/stream/stream-rate.html#Internal_buffers_and_their_effect The reason why an async boundary adds a buffer is because an async boundary makes no sense otherwise as without buffer both

Re: [akka-user] postStop doesn't get invoked after actor initialization failure

That description suits me ;) On Thu, Mar 31, 2016 at 10:18 AM, Patrik Nordwall <patrik.nordw...@gmail.com > wrote: > From the source: "Only change this if you're very confident and lucky" :-) > > On Thu, Mar 31, 2016 at 9:30 AM, Endre Varga <endre.va...@lightbend.com

Re: [akka-user] postStop doesn't get invoked after actor initialization failure

lt in stop, but postStop is not called > because the actor field was cleared: > https://github.com/akka/akka/blob/master/akka-actor/src/main/scala/akka/actor/dungeon/FaultHandling.scala#L210 > > On Wed, Mar 30, 2016 at 10:59 AM, Endre Varga <endre.va...@lightbend.com> > wrote: > >

Re: [akka-user] postStop doesn't get invoked after actor initialization failure

On Sun, Mar 27, 2016 at 5:52 PM, Stanislav Savulchik wrote: > Hi, everyone! > > I've discovered that Actor's postStop method doesn't get invoked if > exception occurs during actor initialization via preStart method. Does > anyone know if it is the correct behavior? I

Re: [akka-user] Source with feedback?

Also, familiarize yourself with the BidiFlow API: `BidiFlow.atop` `BidiFlow.join` `Flow.atop` `Flow.join` On Wed, Mar 30, 2016 at 2:00 AM, Konrad Malawski wrote: > Source + 1 input = Flow :-) > > Read up on custom stages >

Re: [akka-user] [2.4.2] - http-client - lots of: Error in stage [One2OneBidi]: Inner stream finished before inputs completed. Outputs might have been truncated

This is a "bug" as in it does not cause any issues but warns against truncation possibilities too conservatively. Being fixed already. -Endre On Thu, Mar 24, 2016 at 8:43 AM, Marek Żebrowski wrote: > I experience lots of Errors of such kind: > >

Re: [akka-user] Re: Can this be done with the build in stages?

I like the throttle version more ;) On Sun, Mar 20, 2016 at 4:24 PM, Roland Kuhn wrote: > Yes, and for the immediate case you can use Future.successful. > > Regards, Roland > > Sent from my iPhone > > On 20 Mar 2016, at 15:41, john.vie...@gmail.com wrote: > > Something very

Re: [akka-user] How-to restart a RunnableGraph on failure?

in stopping all of the actors materialized by that materializer. -Endre > > (i.e. I don't think that's a solution) > > On Mon, Mar 21, 2016 at 7:22 PM, Endre Varga <endre.va...@lightbend.com> > wrote: > >> The issue is that there might be 3rd party RS stages, or stages from a >&

Re: [akka-user] How-to restart a RunnableGraph on failure?

d we have a termination Future, similar to the ActorSystem? > > mån 21 mars 2016 kl. 16:59 skrev Endre Varga <endre.va...@lightbend.com>: > >> Ah, OK that will work. The only issue is that shutdown() is asynchronous >> so you cannot be fully sure when it has stopped everything. >

Re: [akka-user] How-to restart a RunnableGraph on failure?

Ah, OK that will work. The only issue is that shutdown() is asynchronous so you cannot be fully sure when it has stopped everything. -Endre On Mon, Mar 21, 2016 at 4:58 PM, wrote: > Hi Endre, > forgive my wording. I meant calling shutdown() on the materializer of the >

Re: [akka-user] Akka Cluster without Remoting?

Hi Curt, On Fri, Mar 18, 2016 at 5:35 AM, Curt Siffert wrote: > Hi, I'm supporting a pre-existing Akka project that is currently set up to > run 1 Master instance and N Worker instances. > > It does not use routing/remoting. > What do you mean by not using routing? How does

Re: [akka-user] Akka remote communication roadmap?

Nope. We just drop out-of-order messages. There will be no reliable delivery (except system messages). But even if we need to add it, it is not hard to implement. -Endre On Fri, Mar 18, 2016 at 11:21 AM, Guido Medina wrote: > Message ordering would be challenging to

Re: [akka-user] Akka remote small/many messages throughput discussion?

On Fri, Mar 18, 2016 at 12:31 PM, Guido Medina wrote: > Thanks for the quick response: > > Nodes pair or actors pair? > Sorry I meant actors pair. But honestly, in the case of UDP there will be no performance increase by having these subchannels at all, at least in terms of

Re: [akka-user] Akka remote small/many messages throughput discussion?

On Fri, Mar 18, 2016 at 12:13 PM, Guido Medina wrote: > Given the following scenario, which design would fit best: > > Assume I have 2 receivers@node-1, for simplicity lets call them (I know > I'm using the wrong convention): > >- receiver-1@node-1 >- receiver-2@node-1

  1   2   3   4   >