Re: [akka-user][deprecated] [Akka 2.5.x][Remoting] - Recovering from guaranteed nodes

Could I ask you to move the question to discuss.akka.io? Thanks! -- Cheers, Konrad 'ktoso ' Malawski Akka @ Lightbend On May 17, 2018 at 18:26:11, gutzeit (gutz...@gmail.com) wrote: Dear list members, My company runs a large scale

Re: [akka-user][deprecated] Caused by: com.typesafe.config.ConfigException$Missing: No configuration setting found for key 'enabled'

It is likely related to your build or code, please share that. Can we continue this on discuss.akka.io please though? You have a better chance to get answers quickly there. As noted in the header of this mailing list: We announced

Re: [akka-user][deprecated] Akka Streams Resuming Materializer does not log exceptions

Use the .log() operator. Same as exceptions thrown in a Future do not automatically get logged. There has been discussion about enabling this always, however you’d then be swamped with errors which are recovered and actually “fine and nothing to worry about”. If you want logging, put a log()

Re: [akka-user][deprecated] How to generate the javadoc for offline use?

Hi there, It’s `sbt Dakka.genjavadoc.enabled=true doc` if I remember correctly. I suggest you ask questions on the https://discuss.akka.io forum as that one we monitor more actively nowadays (as mentioned in the footer and header of the mailing list) -- Cheers, Konrad 'ktoso '

Re: [akka-user][deprecated] Akka streams doesnt run when integer range is large

This was already answered on stackoverflow; https://stackoverflow.com/questions/50264569/akka-streams-doesnt-run-when-integer-range-is-large You likely terminate the app before the stream has time to print all things — you have to wait for that to happen as mentioned on SO, this is done by using

Re: [akka-user][deprecated] Cluster state shows node status up even though node is down & unreachable

No idea, I’d guess you have more insights into your envs than we here so you should be able to dig into it more. I also don’t quite get what “not works” means in this context. PS: Consider moving to discuss.akka.io -- Cheers, Konrad 'ktoso ' Malawski Akka @

Re: [akka-user][deprecated] Akka HTTP for microservice orchestration?

Just to confirm > Thanks for your confirmation. I thought that I read somewhere that Akka Http was only intended for internal communication within actor-systems and it should not be used directly...but obviously I was mistaken. Perhaps it was talking about Akka *actor* messaging — which yes

Re: [akka-user][deprecated] Re: Supervision: optimal use for retry logic and understanding logged error

Thanks, let’s follow up there then :) -- Cheers, Konrad 'ktoso ' Malawski Akka @ Lightbend On April 4, 2018 at 21:19:10, daz...@gmail.com (daz...@gmail.com) wrote: have moved to the lightbend forum. On Wednesday, 4 April 2018 12:39:22

Re: [akka-user][deprecated] Akka Http and consuming a response of "application/stream+json" type

Hi Michael, I assume your question is about how to get a Source[MyType] from such streamed incoming entity? The streaming and backpressure itself is “always on”, so the missing bit is the marshalling — you are right we didn’t document it very well, so I went ahead and added the docs:

Re: [akka-user][deprecated] Akka remoting via kafka

This has been cross-posted to https://discuss.lightbend.com/t/akka-remoting-via-kafka/415/5 (and has discussion there) -- Cheers, Konrad 'ktoso ' Malawski Akka @ Lightbend On March 22, 2018 at 3:45:49, Vadim Bobrov (vadimbob...@gmail.com)

Re: [akka-user][deprecated] Microservice Architecture in Akka

Hi there, May I suggest asking the question in the new https://discuss.akka.io forums, as this mailing list is going to move into read-only mode soon? (as documented in it’s header, email footers, and on https://akka.io/blog/news/2018/03/13/discuss.akka.io-announced) > In case of write service

Re: [akka-user][deprecated] Akka persistence and internally stateless actors

Hi Mark, Notice: This mailing list is going to be made read-only shortly, please ask new questions on the: https://discuss.akka.io forum (see footer of every email in this group for details). Akka Persistence is specifically designed for event-sourcing, and persisting Actor state. If you don’t

[akka-user] Announcing discuss.akka.io!

Dear hakkers, We’re pleased to announce a new way to communicate with the core team and communities around the Akka projects (including Akka HTTP, Alpakka the various persistence plugins and all other community projects), as well as downstream projects such as Play and Lagom:

Re: [akka-user] Akka-Streams and Android

Sorry, it’s been years since I’ve done Android development… Maybe someone else on the list will have insights or ideas where better to ask -- Cheers, Konrad 'ktoso ' Malawski Akka @ Lightbend On March 8, 2018 at 1:58:29, 'Matt' via Akka

Re: [akka-user] import context.dispatcher nullpointerexception

Yes it is nulled using unsafe. -- Cheers, Konrad 'ktoso ' Malawski Akka @ Lightbend On March 8, 2018 at 7:32:56, Heiko Seeberger (loe...@posteo.de) wrote: `import context.dispatcher` is what „everybody“ is doing, not? I’m using it all

Re: [akka-user] Akka-Streams and Android

Akka requires JDK8, which Android is not AFAIR… they support Java8 syntax nowadays but not JDK8 bytecode right? You could use ancient versions of Akka which would run on JDK6 bytecode, but that’s strongly discouraged. -- Cheers, Konrad 'ktoso ' Malawski Akka @

Re: [akka-user] Getting the HTTP server's bound port seems to be impossible?

On 07/03/18 01:11, Konrad “ktoso” Malawski wrote: > The difference is in the binding call you can do, there’s a few styles, yet > each gives back a binding, which contains an address: > > val bindingFuture = Http().bindAndHandle(routes, interface = > "0.0.0.0", por

Re: [akka-user] Getting the HTTP server's bound port seems to be impossible?

What do you mean? Binding is not any different if you use high / low level DSLs (that’s the routing DSL vs. just matching incoming objects). The difference is in the binding call you can do, there’s a few styles, yet each gives back a binding, which contains an address: val bindingFuture =

Re: Aw: [akka-user] Akka 2.5.11 - materialization of Flow.lazyInit

To reply about: > I think the two methods Source.lazily and Flow.lazyInit should be alligned (in their name and in their materialized values) No, those are different things and should not be name-aligned. The lazyInit wording is used to talk about “on first element”, while we use the lazily to

Re: Aw: [akka-user] Akka 2.5.11 - materialization of Flow.lazyInit

Whoa (!), thanks for the great catch. You are absolutely right that the Flow.lazyInit is incorrect. It is not possible to get the M strictly from the Future[M] after all. I skimmed tests and they seem to not verify this; The Sink version is fine, so at least that. Could you log a bug about this

Re: [akka-user] Artery remoting seems to be endian-dependent

Ping in one place is enough, reopened :-) -- Cheers, Konrad 'ktoso <http://kto.so>' Malawski Akka <http://akka.io/> @ Lightbend <http://lightbend.com/> On March 1, 2018 at 19:54:20, Alan Burlison (alan.burli...@gmail.com) wrote: On 01/03/18 10:44, Konrad “ktoso” Malawski wrot

Re: [akka-user] Artery remoting seems to be endian-dependent

Thanks, I’ll close the one I had opened then -- Cheers, Konrad 'ktoso ' Malawski Akka @ Lightbend On March 1, 2018 at 19:43:23, Alan Burlison (alan.burli...@gmail.com) wrote: Submitted as https://github.com/akka/akka/issues/24639 --

Re: [akka-user] Artery remoting seems to be endian-dependent

Here’s the ticket: https://github.com/akka/akka/issues/24636 I did not find your github handle, please comment or sub the issue if you want to track it there. -- Cheers, Konrad 'ktoso ' Malawski Akka @ Lightbend On March 1, 2018 at

Re: [akka-user] Artery remoting seems to be endian-dependent

.so>' Malawski Akka <http://akka.io/> @ Lightbend <http://lightbend.com/> On March 1, 2018 at 3:37:06, Alan Burlison (alan.burli...@gmail.com) wrote: On 27/02/18 09:43, Konrad “ktoso” Malawski wrote: > Thanks Alan, > please do report back here or as a ticket on github.com/akka/akka

Re: [akka-user] Artery remoting seems to be endian-dependent

rlison (alan.burli...@gmail.com) wrote: On 27/02/18 06:32, Konrad “ktoso” Malawski wrote: > I’d expect some failures to be logged if your guess is correct, nothing in > the logs? There's a message about the connect to the other node timing out, but no other detail - hence the question :-) > Tha

Re: [akka-user] Artery remoting seems to be endian-dependent

I’d expect some failures to be logged if your guess is correct, nothing in the logs? You can start with setting akka.loglevel = DEBUG There’s more things like making sure akka.remote.log-remote-lifecycle-events = on but debug should really contain all we need (esp since expecting warnings or

Re: [akka-user] Akka actoreRef with macWire DI, actoreRef is not set

= { > case TriggerActor1() => > println("Actor1 triggered from REST controller. Send msg to actor 2") > failedService.testSend() > //actor2 ! Msg1() > case Msg2() => println("got msg2 from actor 1") > } > > > On Thu, F

Re: [akka-user] Akka actoreRef with macWire DI, actoreRef is not set

se that to communicate, things work fine. Is the Q clear now? I am injecting dependencies with MacWire On Thu, Feb 22, 2018 at 11:07 PM Kanwaljeet Singh <ksachd...@gmail.com> wrote: > this is nto a macwire question I think. > > On Thu, Feb 22, 2018 at 11:06 PM Konrad “ktoso” Malaw

Re: [akka-user] Akka actoreRef with macWire DI, actoreRef is not set

The other questions still stand, please make yourself understandable if you need help :) -- Cheers, Konrad 'ktoso ' Malawski Akka @ Lightbend On February 23, 2018 at 16:05:22, ksachd...@gmail.com (ksachd...@gmail.com) wrote: 1.

Re: [akka-user] Akka actoreRef with macWire DI, actoreRef is not set

I don’t understand what’s going where or how ;-) Could you share code? Also, isn’t this a macwire question? Better to ask on https://github.com/adamw/macwire/issues ? -- Cheers, Konrad 'ktoso ' Malawski Akka @ Lightbend On February 23,

Re: [akka-user] Flow.mapAsync and downstream demand

In general relying on exact timing of pulls is rather seen as an anti pattern… Even if you do a custom stage, it’s very brittle, as any element put before your stage could cause pulls, simply because that’s how things work. The same can be said about simply changed buffer sizes between stages —

Re: [akka-user] allow-java-serialization = off breaks remoting

You’re attempting to send a function. remote ! Identify <<< Identify here is wrong Note that it is a case class, that takes a parameter: final case class Identify(messageId: Any) remote ! Identify(“hello”) should work just fine. -- Cheers, Konrad 'ktoso ' Malawski Akka

Re: [akka-user] Re: Swakka - a new extension to akka-http for Swagger/OpenApi

Awesome, and +1 for the move to github (starred, watched) :-) -- Cheers, Konrad 'ktoso ' Malawski Akka @ Lightbend On February 21, 2018 at 18:03:10, Jeremy Townson (jeremy.town...@gmail.com) wrote: Thanks, Patrik. I have raised

Re: [akka-user] Futures, Promises and Actors

Hi Alan, the reason is basically that a Future represents some computation that is “running” (same as a Thread), so serializing it does not make much sense. (Yes, there’s trickery and magic we could do, but we avoid such magic tricks). Rather, use the `future pipeTo someActor` pattern to deal

Re: [akka-user] [Akka Streams] Difference between KillSwitch and Materializer.shutdown()

First warning sign: Why would you have one stream per materializer? shutting down the materializer while things are running is very brutal. It’s like forcefully pulling the carpet from under someone’s feet, and the laughing as they spill their coffee upon themselves — don’t do this as the go-to

Re: [akka-user] Akka Actor usage in Apache Spark and Apache Flink

subscribed to the Google Groups >> "Akka User List" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to akka-user+...@googlegroups.com. >> To post to this group, send email to akka...@googlegroups.com. >> Visit t

Re: [akka-user] Source.queue with java sample

If you’re talking about doing akka streams / reactive streams over the network (seems you imply that by mentioning ‘on other system’), then the queue is not going to give you what you want. That pattern is however trivial with a new feature that we’re about to release in the upcoming release of

Re: [akka-user] Source.queue with java sample

Browse the docs :-) https://doc.akka.io/japi/akka/current/akka/stream/javadsl/Source.html#queue-int-akka.stream.OverflowStrategy- -- Cheers, Konrad 'ktoso ' Malawski Akka @ Lightbend On February 13, 2018 at 13:48:41, 薛永飞

Re: [akka-user] Akka Cluster Http Management Setup

Happy hakking~! -- Cheers, Konrad 'ktoso ' Malawski Akka @ Lightbend On February 12, 2018 at 11:04:28, Kilic Ali-Firat (kilic.alifi...@gmail.com) wrote: Hi Konrad, It was the first time that I was using akka management, reading the

Re: [akka-user] Akka Cluster Http Management Setup

You did not say which versions of libs you’re on, please say that always in such threads :) Assuming latest versions. The 2551 port is NOT the port that any HTTP is on; it’s where Akka remoting is bound to, HTTPing onto that one is not right :) How did you start the management endpoint? You’d

Re: [akka-user] Re: Akka Concurrency - Trying to call actors in parallel from an actor

Hi Rob, ask is not the problem. The Await’s shown in the above code are. Ask is not blocking, and sometimes perfectly fine. Using Await is an anti pattern in general, but in Actors and other reactive things is where it’s really bad. Please read this section of the docs that shows what blocking

Re: [akka-user] Akka Cluster Sharding in Chat room app

No. I mean that the sharded actor would extend PersistentActor, which gives you that recovery -- Cheers, Konrad 'ktoso <http://kto.so>' Malawski Akka <http://akka.io/> @ Lightbend <http://lightbend.com/> On February 9, 2018 at 14:21:06, Konrad “ktoso” Malawski ( konrad.mala

Re: [akka-user] Akka Cluster Sharding in Chat room app

Hi there, sharding is the thing that “starts things on the other node”. The thing that “recovers state” is akka persistence: https://doc.akka.io/docs/akka/snapshot/persistence.html?language=scala One often uses those two together, gaining the capability you just hinted at. Happy hakking --

Re: [akka-user] Akka, Akka Typed and dead code elimination

d might Akka Typed be a way forward in that regard? Cheers, -C On 3 Feb 2018, at 3:43 pm, Konrad “ktoso” Malawski < konrad.malaw...@lightbend.com> wrote: Hi Christopher, I’ve worked in the past on an Scala on Android project, so have had the “pleasure” of battling proguard for similar rea

Re: [akka-user] Akka, Akka Typed and dead code elimination

Hi Christopher, I’ve worked in the past on an Scala on Android project, so have had the “pleasure” of battling proguard for similar reasons. In general I guess the “core stuff” needs to be kept, which would mostly be the akka.actor and dungeon things. AFAIR proguard is ale to understand

Re: [akka-user] Cancel Actor job

Have a look at "cluster sharding”, it’s smarter than just routers. -- Cheers, Konrad 'ktoso ' Malawski Akka @ Lightbend On February 2, 2018 at 11:09:19, Richard Gong (gong...@gmail.com) wrote: That works in a single machine. Now take a

Re: [akka-user] How to shut down ActorSystem after all Actors have stopped?

There is no reliable way to know what “everything is done” means. This is because operations are asynchronous, and if you were to observe “oh! nothing is in any mailbox!” the next millisecond something may actually be in the mailbox, because it was just being asynchonously added. Shutting down

Re: [akka-user] Akka Default Dispatcher creating 9000+ Worker Threads!!

Please read the docs about this effect here: https://doc.akka.io/docs/akka/current/dispatchers.html#blocking-needs-careful-management It’s the Fork Join Pools (JDK) reaction to doing “bad things”™ (blocking) to it. The solution is as Johan explained. -- Cheers, Konrad 'ktoso '

Re: [akka-user] Cancel Actor job

Actors may not be that cheap. They are ~400 bytes for an Actor; plus whatever you put inside one of course, but that’s your state, not the Actor’s fault ;) I tried to create a worker actor every time the master actor received a start job message and found out that it created a new thread to run

Re: [akka-user] akka-http remote to akka cluster or join the cluster?

Using the cluster client is not recommended (as of it’s current implementation at least, in early 2018 ;-)). You can absolutely join your HTTP app into the same cluster and then most apps make use of Cluster Sharding to distribute the load across the cluster. Read up about it here;

[akka-user] Re: decorate actor events / events processing as a way to implement open tracing capabilities

Hi there Daz, I would strongly recommend using a proven implementation of tracing, i.e. the Lightbend Monitoring stack and it's Open Tracing support: https://developer.lightbend.com/docs/monitoring/latest/extensions/opentracing.html Implementing it manually may seem like doable or at first, but

Re: [akka-user] expectNoMessage keeps unexpected message in the queue

I see! Thanks for digging that up. I think that was an un-intended change so I’ll fix that right away. Issue here https://github.com/akka/akka/issues/24270 PR soon. -- Cheers, Konrad 'ktoso ' Malawski Akka @ Lightbend On January 8, 2018

Re: [akka-user] Processing `If-None-Match`

You can deconstruct the data structure on your own like this: val tag = EntityTag("kappa", weak = true) val ifNoneMatch = `If-None-Match`(tag) ifNoneMatch.m match { case EntityTagRange.Default(tags) if tags.nonEmpty ⇒ tags.head.tag case EntityTagRange.Default(tags) ⇒ "" case

Re: [akka-user] alpakka version of "Producer" or "Consumer" object?

1. alpakka kinesis connector works well with KPL as well as KCL It uses import com.amazonaws.services.kinesis.AmazonKinesisAsync KPL seems to be the “kinesis data streams” api? That seems to use the same PutRecord etc logic as we do though. 2. KinesisSources and KinesisSinks both work as

Re: [akka-user] expectNoMessage keeps unexpected message in the queue

What do you mean? What queue? They are both implemented using the exact same internal method: @deprecated(message = "Use expectNoMessage instead", since = "2.5.5") def expectNoMsg(max: FiniteDuration) { expectNoMsg_internal(max.dilated) } /** * Assert that no message is received for the

Re: [akka-user] Akka 2.5.8 (Java Edition) Error initializing: java.lang.IllegalStateException: not yet initialized

Are you not accidentally mixing Akka versions? What does your dependency file look like with regards to Akka dependencies. Akka Streams and Actor etc should all be on the same version. -- Cheers, Konrad 'ktoso ' Malawski Akka @ Lightbend

Re: [akka-user] alpakka version of "Producer" or "Consumer" object?

Hi Soichi, “Producer” and “Consumer” are words used in Kafka, as such Alpakka’s Kafka integration uses them as well. (Note that Akka-Steam-Kafka is part of Alpakka, even if in an separate repository) The prime idea in all Alpakka things is that there are Sources (i.e. the Consumer (consumes from

Re: [akka-user] File based durable mailboxes for akka actors

Seems Durable (filebased) mailboxes weren’t even in 2.3, but 2.2… So even more ancient ;-) A question regarding them, made me assume you’re using those ancient version of Akka. Please give Persistence a try. There’s nothing durable mailboxes did better (or even as good as) Persistence does

Re: [akka-user] File based durable mailboxes for akka actors

Firstly, Akka 2.3 is not supported anymore… Since 2015. Please upgrade to an actively maintained version, such as Akka 2.5. Akka 2.4 will be EOL shortly as well. 2.4 and 2.5 are binary compatible so there’s no reason whatsoever to remain on 2.4 (not mentioning 2.3). Akka 2.3 was enver released

Re: [akka-user] Re: akka-http is there an example of showing how to integrate with servlet container?

Matt is correct, Akka HTTP is a complete server implementation, all the way down the sockets, through parsing and rendering headers, lifecycle management etc etc. It does so in a fully streaming manner as well, which is it’s strong point. Embedding Akka HTTP inside a servlet container sells it

Re: [akka-user] access to http response databytes stream materialized value

data= data.mapMaterializedValue(mat => doThings(mat)) Is how you can achieve it. Yes, it’s the current best practice in those situations. -- Cheers, Konrad 'ktoso ' Malawski Akka @ Lightbend On December 30, 2017 at

Re: [akka-user] Why does Akka Http AuthenticationDirective use Tuple1?

Just out of curiosity, why is the AuthenticationDirective using a Tuple1[T] instead of just T? Is this because of forward compatibility or has this some other reason? It’s because we have infrastructure for combining directives of arbitrary arity touples into other “combined” directives, where

Re: [akka-user] Akka Streams for synchronous request processing

In short I want to execute Akka graph from my API with out materializing every time. What’s your reason for this? Just so we’re on the same page and not imagining reasons for doing this :) Problem that I am facing: How to pass request object to source node of graph. That’s as simple as using a

Re: [akka-user] Akka Streams for synchronous request processing

Sure it’d just work… What specifically do you have in mind? What do you mean by “We should be able to plug-in out partial graphs to the flow.” (specifically, what’s the use case). -- Cheers, Konrad 'ktoso ' Malawski Akka @ Lightbend On

Re: [akka-user] cachingProhibited causes 404 not found to be returned by the server

Could you provide a small reproducer showcasing the issue as repo? -- Cheers, Konrad 'ktoso ' Malawski Akka @ Lightbend On December 20, 2017 at 9:14:41, Nicolae Marasoiu ( nicolae.maras...@gmail.com) wrote: Hi, I have js files and a

Re: [akka-user] Re: How to measure performance of Actor Message from one actor reaching to another actor

Since you’d be measuring remoting there, on the boundary between nodes, I highly recommend making use of its “new” (has been out there quite a few months) implemenation: Artery, see docs here: https://doc.akka.io/docs/akka/2.4/scala/remoting-artery.html -- Cheers, Konrad 'ktoso '

Re: [akka-user] Is it easy to use akka-http to build ...?

It’s pretty much as simple as using this directive: https://doc.akka.io/docs/akka-http/current/scala/http/routing-dsl/directives/file-and-resource-directives/getFromDirectory.html

Re: [akka-user] Last IntelliJ update (2017.3) breaks developing with Akka / Scala on Java

Hi Tomer, Thanks for reporting it to the IntelliJ team. Could you post a working link to the issue? The one posted does not seem to work. -- Cheers, Konrad 'ktoso ' Malawski Akka @ Lightbend On December 5, 2017 at 21:49:14, Tomer

Re: [akka-user] Akka Cluster Bootstrap ?

What do you want to know, that’s a pretty generic question ;-) We’re working on it. It works, it’s not done yet, will have to be cleaned-up quite a bit and documented. -- Cheers, Konrad 'ktoso ' Malawski Akka @ Lightbend On December 4,

Re: [akka-user] Akka persistence in production - recommended journals?

LevelDB is not, in any case, intended for production systems. Production ready journals would be: - the cassandra one, maintained by the akka team, it is most mature and has most features - the jdbc one, community maintained but seems to work well - we’ve heard of people using the mongo one, but

Re: [akka-user] Akka Typed and stack safety

That’d only be the case in completely synchronous execution. And the behaviours body would actually execute on that line — but it doesn’t. Here once you returned a new behaviour, control is given back to whoever is invoking things (in great simplification, “the actor system”). -- Cheers, Konrad

Re: [akka-user] Overriding onUpstreamFinish behaviour for FlowOps

What kind of Flow exactly. What does it do? See this too https://doc.akka.io/docs/akka/current/stream/stream-error.html?language=scala#delayed-restarts-with-a-backoff-stage other than supervision which isn’t generic. -- Cheers, Konrad 'ktoso ' Malawski Akka @

Re: [akka-user] Parsing Configuration

Hard to tell without knowing exactly what you’re doing there, but usually an explicit resolve is not needed. -- Cheers, Konrad 'ktoso ' Malawski Akka @ Lightbend On November 27, 2017 at 13:02:41, Joseph Mansigian (

Re: [akka-user] Android client connecting to Akka cluster via sockets

We’re working on an ClusterClient replacement that would use HTTP(2) or GRPC as it’s transport, this would be more or less what you’re after and also allow to keep the convenience of Actor messaging. I’d strongly discourage reverse engineering the protocol as such impl will be rather brittle, and

Re: [akka-user] Older version of Akka framework

Hi Jani, Use your dependency management tool such as sbt, maven or gradle to download dependencies. They’re all hosted on maven central. No actively maintained version of Akka is compatible with JDK6. You can use a not-maintained version of 2.3.x though — though we strongly discourage that since

Re: [akka-user] FSMs and Akka Streams

Hi John, your problem description is a bit abstract so not quite sure what to advice there, however: please do bear in mind that Streams do not replace Actors. They complement them. Streams are nice for linear things, though Actors are nice for dynamic and distributed settings. It depends on your

Re: [akka-user] Streaming proxy/tunel on top of akka-http

Akka-HTTP does support completely streaming things, that’s pretty much it’s main use case. Please share code and or specifics about what does not work. -- Cheers, Konrad 'ktoso ' Malawski Akka @ Lightbend On November 8, 2017 at 12:05:15,

Re: [akka-user] ActorRef proxy - had somebody implemented?

Normally you’d simple have an Actor do this, instead of hacking into the internals as proposed in your snippet :-) Have an actor who’d keep messages and forward to the target once it’s received it. Having that said, we have the concept of such “FutureRef” defined and implemented in AkkaTyped,

Re: [akka-user] ActorSystem FatalError Handling

When such errors are thrown all bets are off basically, in any app, not just akka. You can turn off the system automatically terminating — check reference.conf, though as I said — all bets are off then anyway because runtime is in potentially “bad state" -- Cheers, Konrad 'ktoso

Re: [akka-user] Timer of GroupedWithin (akka-stream-kafka) does not seem to be working

Please report in one space at the same time. This was already reported on the issue tracker by yourself. This is to avoid wasting cycles and time. Thanks. -- Cheers, Konrad 'ktoso ' Malawski Akka @ Lightbend On October 27, 2017 at

Re: [akka-user] Akka TCP and Slow Start Restart

problem with Akka TCP but I know less about how friendly Akka remoting is to attackers. Ever come across someone using Akka remoting in an open internet type service...? On Wed, Oct 25, 2017 at 4:26 AM, Konrad “ktoso” Malawski < konrad.malaw...@lightbend.com> wrote: > What do you mean

Re: [akka-user] Akka cluster or Kubernetes

They’re completely different. Kubernetes is where you run apps. It shedules entire apps onto a set of nodes. Akka cluster IS the app. It runs on a set of nodes, and leverages health mechanisms to be able to smartly balance load and actors across them. Akka cluster apps are the apps that

Re: [akka-user] Akka TCP and Slow Start Restart

That’s one of the reasons the new remoting is Aeron (and thus UDP, with TCP-like delivery semantics) based… :-) -- Cheers, Konrad 'ktoso ' Malawski Akka @ Lightbend On October 24, 2017 at 3:59:30, Alan McSherry (alanmcshe...@gmail.com)

Re: [akka-user] No shutDown on Materializer

on Materializer vs ActorMaterializer? On Mon, Oct 23, 2017 at 7:39 PM, Konrad “ktoso” Malawski < konrad.malaw...@lightbend.com> wrote: > Hi Richard, > Saying that “using Materializer” will cause leaks is somewhat of a weird > phrasing, since that sounds just like “using ActorSystem can caus

Re: [akka-user] No shutDown on Materializer

Hi Richard, Saying that “using Materializer” will cause leaks is somewhat of a weird phrasing, since that sounds just like “using ActorSystem can cause leaks” — well sure, just like “using objects can cause leaks” :-) Let’s step back and analyse where your colleague’s statement came from, and

Re: [akka-user] Complete generate a null value in akka-http

Don’t return null in scala code, that’s very not-scala-style. Instead you could return empty things, or best rather even to throw an exception and make your handler https://doc.akka.io/docs/akka-http/current/scala/http/routing-dsl/exception-handling.html make it into a not found response. --

Re: [akka-user] Spray->Akka-Http Migration - seeing high 99th percentile latencies post-migration

Step 1 – don’t panic ;-) Step 2 – as I already asked for, please share actual details of the benchmarks. It is not good to discuss benchmarks without any insight into what / how exactly you’re measuring. -- Cheers, Konrad 'ktoso ' Malawski Akka @ Lightbend

Re: [akka-user] Re: Spray->Akka-Http Migration - seeing high 99th percentile latencies post-migration

Short lived connections are slightly more costly in Akka-HTTP than in Spray, due to the streaming infrastructure. -- Cheers, Konrad 'ktoso ' Malawski Akka @ Lightbend On October 17, 2017 at 9:48:20, Gary Malouf (malouf.g...@gmail.com)

Re: [akka-user] Implements CRDTs conters more than 100 000

It’s as the docs explain: It is not intended for *Big Data*. The number of top level entries should not exceed 10. When a new node is added to the cluster all these entries are transferred (gossiped) to the new node. The entries are split up in chunks and all existing nodes collaborate in the

Re: [akka-user] Uncaught error from thread - ContentType$WithMissingCharset

Happy hakking, cheers :) — Konrad `kto.so` Malawski Akka @ Lightbend On 12 October 2017 at 00:27:11, bordec...@gmail.com (bordec...@gmail.com) wrote: Hi Konrad, I think, the above VERSIONS resolved my issue. Thank you very much for the response. I tested

Re: [akka-user] [akka-http] Virtual hosts

Simply Http().bind two times given the same routes ;) Though in reality people would hide akka-http behind ngnix or something similar and do the tls things there very often. — Konrad `kto.so` Malawski Akka @ Lightbend On 11 October 2017 at 15:10:34,

Re: [akka-user] [akka-http] Virtual hosts

What’s the actual use case? By itself no. — Konrad `kto.so` Malawski Akka @ Lightbend On 11 October 2017 at 14:44:59, Slowaner (turchaninov.nik...@gmail.com) wrote: Is there any feature to bind many virtual hosts at one interface with same listening IP

Re: [akka-user] Uncaught error from thread - ContentType$WithMissingCharset

Weird indeed; With regards to versions, please always use the latest - esp when reporting issues like this. Please try 10.0.10 and 2.5.6 as I suggested above. Can you post a reproducer (repository) where we could reproduce this? — Konrad `kto.so` Malawski Akka @ Lightbend

Re: [akka-user] Uncaught error from thread - ContentType$WithMissingCharset

Actually depend on akka-http 10.0.10 and akka 2.5.6 ;-) — Konrad `kto.so` Malawski Akka @ Lightbend On 11 October 2017 at 10:15:34, bordec...@gmail.com (bordec...@gmail.com) wrote: Thanks for quick reply, Konrad. Actually, I'm using - these json parsing

Re: [akka-user] Uncaught error from thread - ContentType$WithMissingCharset

The exception is pretty clear about something being wrong with dependencies: > java.lang.NoClassDefFoundError: akka/http/scaladsl/model/ContentType$WithMissingCharset How do you configure this project? What’s your dependencies / build file / build system? — Konrad `kto.so` Malawski Akka

Re: [akka-user] yourkit CPU ignore list

.materialize? Or does that indicate a problem with the way play is setup? On 10 October 2017 at 10:49, Konrad “ktoso” Malawski <konrad.malaw...@lightbend.com> wrote: > ForkJoin noice mostly – people sometimes panic about ForkJoinPool#scan > specifically (which shows up when there’s nothing to

Re: [akka-user] yourkit CPU ignore list

ForkJoin noice mostly – people sometimes panic about ForkJoinPool#scan specifically (which shows up when there’s nothing to do, so it spins looking for work). — Konrad `kto.so` Malawski Akka @ Lightbend On 10 October 2017 at 18:47:37, Sam Halliday

Re: [akka-user] Changed osgi.ee requirement in Akka 2.5.6

Hi there, Its not an intended change as far as I can see. Could you open a ticket please? ( GitHub.com/Akka/Akka ) We’ve been upgrading plugins to enable publishing with jdk9 recently so something must have happened to abt-Osgi during that On October 7, 2017 at 8:16:40, Oliver Heger

Re: [akka-user] Akka Cluster with different seed node sequence

Hi Prateek, No, this is a misunderstanding of how seed-nodes work. The first node in that list MUST be the same node if using the seed-nodes process. What you did by making each node have it’s own address as the first in their seed node list is form 3 independent clusters. This works as

Re: [akka-user] [akka-streams] Shared Materializer in akka extensions

So rather unlikely people will want access to your materialiser there. The sharing of materializer is most important for lifecycle - killing a materializer kills all streams it hosts, so in your case it’s unlikely you want to bind your streams to random other people’s streams lifecycles. I

  1   2   3   >