[akka-user] unrecoverable Tcp connection with ByteString of moderate size (~250k)

2015-07-06 Thread Sam Halliday
Dear all, I had a few questions for this list last week regarding an unrecoverable error condition that I was seeing in Wandoulabs WebSockets. I have now isolated the problem to standard Scala 2.11.7 / Akka 2.3.11 Tcp.Write with the minimal example at the bottom of this email. It seems that

[akka-user] Re: unrecoverable Tcp connection with ByteString of moderate size (~250k)

2015-07-06 Thread Sam Halliday
Aha! Think I got it. I need to send ResumeWriting and listen for a WritingResumed, to recover from such a situation. On Monday, 6 July 2015 11:01:23 UTC+1, Sam Halliday wrote: I should say, that in every example I have tried... with payloads up to 30MB for the initial un-acked message, it

[akka-user] Re: Akka HTTP (RC-4): failing on blocking operations with simple test

2015-07-06 Thread Dmitry Vorobiov
Wow, it might be the cause, thank you, Egis! I ll check it soon! On Monday, July 6, 2015 at 11:45:17 AM UTC+2, Egis wrote: You are most likely getting these errors because of this regression in RC4: https://github.com/akka/akka/issues/17854 Your test should do what you expect with RC3. It

[akka-user] Re: unrecoverable Tcp connection with ByteString of moderate size (~250k)

2015-07-06 Thread Sam Halliday
This part of Register is also relevant * @param useResumeWriting If this is set to true then the connection actor *will refuse all further writes after issuing a [[CommandFailed]] *notification until [[ResumeWriting]] is received. This can *

[akka-user] Re: Akka HTTP (RC-4): failing on blocking operations with simple test

2015-07-06 Thread Egis
You are most likely getting these errors because of this regression in RC4: https://github.com/akka/akka/issues/17854 Your test should do what you expect with RC3. It would also work with RC4 if your client had HTTP KeepAlive enabled: ab -n 50 -c 4 -k http://localhost:9000/test Egis On

[akka-user] Re: unrecoverable Tcp connection with ByteString of moderate size (~250k)

2015-07-06 Thread Sam Halliday
I should say, that in every example I have tried... with payloads up to 30MB for the initial un-acked message, it always arrives at the destination. The subsequent, and retried, but the connection is completely dead and the Ack-ed message can never be sent. On Monday, 6 July 2015 10:59:38

[akka-user] Re: How can I extract Future[T] value in unmarshaller without blocking ?

2015-07-06 Thread Dmitry Vorobiov
Have you looked at onComplete / onSuccess directives that help processing futures? On Sunday, July 5, 2015 at 11:12:29 PM UTC+2, Jack Daniels wrote: I'm using akka-http 1.0.-RC4. How can I extract Future[T] value in unmarshaller without blocking ? Details are here

Re: [akka-user] Akka HTTP Streams vs Pulse Queues

2015-07-06 Thread Viktor Klang
Hi Eric, I'm not sure I can answer your very broad question, would you mind/be able to formulate a couple of more specific ones? On Fri, Jul 3, 2015 at 6:34 PM, Eric Kolotyluk eric.koloty...@gmail.com wrote: I have prototyped an application that basically multiplexes messages, assembles them

[akka-user] Re: How to create dispatcher's threads set to low priority?

2015-07-06 Thread kermitas
Please see the answer http://scalaakka.blogspot.com/2015/07/akka-dispatcher-with-low-priority.html . W dniu czwartek, 2 lipca 2015 15:45:10 UTC+2 użytkownik kermitas napisał: Hi group, what is the best way to assign dedicated ThreadFactory to dispatcher? My goal is to have all threads in

Re: [akka-user] Akka Stream Source as ActorPublisher

2015-07-06 Thread Viktor Klang
Hi Maxim, could you please minimize the problematic code into a self-contained, no extraneous pieces, snippet? On Mon, Jul 6, 2015 at 9:55 PM, Maxim Korolyov korolyov.ma...@gmail.com wrote: Hey, i was playing with akka stream and akka http and faced and issue, when source created as

[akka-user] Akka Stream Source as ActorPublisher

2015-07-06 Thread Maxim Korolyov
Hey, i was playing with akka stream and akka http and faced and issue, when source created as ActorPublisher doesn't publish any data to source. i have verified that `onNext` method of ActorPublisher is invoking and that the source is empty by adding a logging flow like this

[akka-user] Lost actor communication

2015-07-06 Thread Benjamin Black
I am running a 24 node cluster that is roughly split into two roles: frontend and backend. There is a streamer actor on the frontend node talking to a tracker actor on the backend node. There can be many streamer actors on several frontend nodes talking to one tracker actor. It would seem that

Re: [akka-user] Production Systems Using DistributedPubSub?

2015-07-06 Thread Michael Frank
what problem are you trying to solve with DistributedPubSub? if you are not tolerant to losing some messages, then DistributedPubSub might not be appropriate in your scenario. i wouldn't depend on always being able to gracefully leave the cluster in production! node failures and network

Re: [akka-user] Production Systems Using DistributedPubSub?

2015-07-06 Thread James Carman
I'm using DPS as a routing engine, basically. We will have multiple nodes of a particular type connecting into the system which are basically different applications that have different needs. These different applications should only consume a message one time, but it doesn't matter which of

Re: [akka-user] Akka and Node.js

2015-07-06 Thread Justin du coeur
On Sat, Jul 4, 2015 at 2:20 AM, Andi Nugroho Dirgantara andi.n.dirgant...@gmail.com wrote: I want my Node.js apps also works under Akka system maybe using node-java. Is it good practice? If it's not, is there any solution that Node.js can communicate with Akka? If you particularly want to