[akka-user] Spray to Akka HTTP

2016-09-01 Thread Richard Rodseth
I'm struggling to convert the following response marshaller. ToResponseMarshaller is a trait and object in Spray, and Marshaller takes one type parameter. I've read the docs, and am stumped. Can anyone provide further guidance? // See https://bitbucket.org/binarycamp/spray-contrib/src trait

[akka-user] Akka and Streams Concurrency Fundamentals

2016-09-01 Thread Dagny T
I'd like to find reliable and current information for learning this using v2.4.9. I've posted a reply to someone else's related message; but wanted to call Forum attention to please help refer us to a useful Blog or GitHub repo on this topic; AND using the latest and greatest TestKit tools!

[akka-user] Re: research about concurrency bugs

2016-09-01 Thread Dagny T
Hey Carmen, I'm a Scala/Akka Newbie; but I think the idea in Scala is to use Actors to avert most concurrency bugs. So, essentially (Akka) Actors are things that can hold their own state, like Objects in traditional OOP languages. External Entities can Message to Actor references to signal it

Re: [akka-user] Nodes becomes unreachable due to serialization-issues with one single message

2016-09-01 Thread Moax76
Issue created: https://github.com/akka/akka/issues/21343 But I'll modify my serializer anyway. Thanks. -Morten On Thursday, September 1, 2016 at 8:33:04 PM UTC+2, Patrik Nordwall wrote: > > I think we should handle exceptions from serializer.toBinary as transient. > Can you please create an

Re: [akka-user] Problem Configuring ActorSystem

2016-09-01 Thread Patrik Nordwall
That feature with short names is not released yet. It's in the Artery branch. /Patrik tors 1 sep. 2016 kl. 10:42 skrev Konrad Malawski : > You can also just set the provider to "remote" (or "cluster"). > It's a bit simpler to not make a typo in those ;) > > On Thu, Sep 1,

Re: [akka-user] Nodes becomes unreachable due to serialization-issues with one single message

2016-09-01 Thread Patrik Nordwall
I think we should handle exceptions from serializer.toBinary as transient. Can you please create an issue. I can understand that the reason might be that it is a program bug and the system should probably not run with the bug, but I think error logging

Re: [akka-user] Nodes becomes unreachable due to serialization-issues with one single message

2016-09-01 Thread Moax76
Thanks a lot for the info. I'll fix my serializer so that it wraps all exceptions in NotSerializableException. Am I understanding it correct that I should only do this wrapping when serializing, and not deserializing? Thanks again. -Morten On Thursday, September 1, 2016 at 4:14:43 PM UTC+2,

Re: [akka-user] Nodes becomes unreachable due to serialization-issues with one single message

2016-09-01 Thread Martynas Mickevičius
EndpointWriter is only treating NotSerializableException as a transient one. So wrapping all of the exceptions from your serializer into NotSerializableException will not get the association dropped. Here is the discussion on having all of the exceptions transient:

Re: [akka-user] Fail to override Assembly Merge Strategy in multi-jvm node test

2016-09-01 Thread Martynas Mickevičius
You are setting assemblyMergeStrategy in assembly but the error is indicating that different assembly is being run: multi-jvm:assembly. Therefore in your build.sbt you should use: assemblyMergeStrategy in assembly in MultiJvm On Sun, Aug 21, 2016 at 7:53 PM, Lap Ming Lee

Re: [akka-user] Problem Configuring ActorSystem

2016-09-01 Thread Konrad Malawski
You can also just set the provider to "remote" (or "cluster"). It's a bit simpler to not make a typo in those ;) On Thu, Sep 1, 2016 at 6:14 AM, Viktor Klang wrote: > there's a comma in the class name > > -- > Cheers, > √ > > On Sep 1, 2016 5:11 AM, "Joseph Mansigian"

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

2016-09-01 Thread Endre Varga
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?

2016-09-01 Thread Victor
Ah I see :) Something like this: ... -> BidiFlow.port1 -> EmbededFlow -> BidiFlow.port2 -> ... Thanks, Victor Le jeudi 1 septembre 2016 10:14:04 UTC+2, drewhk a écrit : > > Hi Victor, > > Embedding is not the way to think about this. What you really want is a > BidiStage which then can be

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

2016-09-01 Thread Endre Varga
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? > >

[akka-user] Re: akka directive for uploading multiple files

2016-09-01 Thread Leo Wolf
Hi Cyril, Not yet now. I just use two solutions to fit the requirement, one is calling the api multiple times, and another is taring the whole file into a pkg and untaring it on server. Maybe this can help you. -- >> Read the docs: http://akka.io/docs/ >> Check the

[akka-user] Re: akka directive for uploading multiple files

2016-09-01 Thread Cyril Guh
Hi Leo, Have you found a solution? I am facing the same requirement and exploring solutions. On Thursday, June 2, 2016 at 4:25:40 PM UTC+10, Leo Wolf wrote: > > Hi, I'm using akka http for file uploading as bellow: > formFields('json.as[String]) { json => > > uploadedFile("file") { > > ... >