Re: [akka-user] Akka Config throwing reserved character error

I assume you followed the error message and applied the changes suggested by it? (Because that is not apparent from the code you provided) -- Cheers, √ On Jun 3, 2016 21:17, "Amruta" wrote: > > > To configure cassandra for akka in java using environment variables I am >

[akka-user] Akka Config throwing reserved character error

To configure cassandra for akka in java using environment variables I am writing the following code which is throwing the error String contactPoints = "cassandra-journal.contact-points=" + envHelper .getContactPoints(); contactPoints = contactPoints

Re: [akka-user] Scala - fromPublisher is not a member of object akka.stream.scaladsl.Source

You're welcome, I just got my crystal ball back from repair. fre 3 juni 2016 kl. 20:14 skrev Marco Rispoli : > You were spot on! > > Thank you for replying to my question. I found the problem. It wasn't the > code. And you were 100% right. It was related to the class path

Re: [akka-user] Scala - fromPublisher is not a member of object akka.stream.scaladsl.Source

You were spot on! Thank you for replying to my question. I found the problem. It wasn't the code. And you were 100% right. It was related to the class path (sort of). The problem was in Intellij libraries setup. at some point I did try to compile the project with SBT and it worked and ran

[akka-user] ANNOUNCE: Akka 2.4.7 Released

Dear hakkers, we—the Akka committers—are proud to announce a new patch release of Akka 2.4. This release contains a number of minor improvements and fixes spread out across many of the Akka modules and the documentation. Some noteworthy changes in the 2.4.7 release are: - A resource leak

[akka-user] Re: Job offer for Scala/Akka developer

We have positions opened again for Scala developers with Akka experience. We're slowly migrating our system architecture to employ more and more Akka and also our REST API towards Akka-http and some of our core features run on top of Akka cluster, so if you're Akka enthusiast, you'll definitly

Re: [akka-user] Re: In akka cluster, why a node which state is down can be makes reachable

Unreachable/reachable is orthogonal to the member status Up/Down/... It's just reflects what the failure detectors thinks about the node. It can flip back and forth independent of the member status. /Patrik fre 3 juni 2016 kl. 08:26 skrev <281725...@qq.com>: > But Why a node in the down state

Re: [akka-user] Re: Akka-Http perf difference chunked vs non-chunked

Right we have a ticket that sounds rather similar I believe (auto toStricting up unto a given limit), I agree it's a good idea. -- Konrad `ktoso` Malawski Akka @ Lightbend On 3 June 2016 at 11:21:00, daleksan (david.aleksandrow...@gmail.com) wrote: I can

[akka-user] Re: Akka-Http perf difference chunked vs non-chunked

I can confirm that changing the HTTP client to curl does fix the issue. I can see much bigger buffers used in this case. This answers my question however I would say Akka-Http still should be guarded from such case (i.e. never emit such small buffers, due to profound performance degradation,

Re: [akka-user] Clustering - New Incarnation unable to re-join

Hi Drew, When a cluster has nodes marked unreachable new nodes cannot be marked as up until those nodes are either reachable again or has been downed. This is what the "leader can currently not perform its duties, reachability status ..." message informs you about. As soon as the cluster has

Re: [akka-user] Kamon Aspectj weaving affecting Actor creation in Akka cluster

Hi Regu, So you mean that with a single node cluster but without kamon the actor is created by the pool but if you add kamon it stops working? Sounds suspiciously much like you have the allow-local-routees setting of the router set to off, could this be it? -- Johan Akka Team Typesafe -

Re: [akka-user] Shutdown and Cleanup of Akka Persistent Actor Journal and Snapshots

Hi Johan, Many thanks, thats what I needed. I had thought about context.become, but wasn't sure with the stashing -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >> http://doc.akka.io/docs/akka/current/additional/faq.html >> Search

Re: [akka-user] Shutdown and Cleanup of Akka Persistent Actor Journal and Snapshots

Hi Ian, Both deleteMessages and deleteSnapshots fire away a message to trigger the deletion, so as soon as they return it should be safe to stop the actor, there just wont be any actor left to accept the completion (or failure) messages for those two actions. Passing a message through the

[akka-user] Stateless service with repeated stream materialization or actor?

Hello, I am building a service which uses Akka Http Client to contact another service and return a Future. The current architecture result in materializing a stream repeatedly like that: val source = Source single (request, dummy) val result = source via pool runWith Sink.head What impact