[akka-user] Akka stream and akka cluster

[Alexey Romanchuk]

Hey hakkers!

Do you have any plans to implement clustered stream materializer to 
distribute stream parts in cluster? If yes do you have any estimations or 
ETA?

Right now it is possible to manually distribute load using futures and map 
async, but clustered materializer will be really cool.

Thanks!

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are 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+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Re: new project - akka streams/http - is using the current spray release with akka streams and migrating later too painful?

[richard]

Hey Giovanni,

I just asked a very similar question a couple days ago, some of the info 
you need was already answered there:

https://groups.google.com/forum/#!searchin/akka-user/New$20projects$20should$20use$20Spray.io$20or$20Akka-HTTP/akka-user/JHktsLhEvAM/_0b01aqTuPYJ

Cheers

On Tuesday, 3 February 2015 09:34:41 UTC+10, Giovanni Alberto Caporaletti 
wrote:
>
> Hi,
> I need to start a new project in a couple of months (and hopefully have a 
> first working prototype in 2-3 months more). I am a rxscala/java user, and 
> am following the reactive streams/akka streams projects with huge interest.
>
> For the api layer, akka-http is too immature to be used right now (I need 
> websockets and ssl for example), although I'd really like to use the new 
> akka streams api for the reactive logic. Do you think it makes sense/is 
> possible to use the latest release of spray and integrate it with the 
> current milestone of akka-streams only to migrate everything to akka-http 
> later on? If not, what do you suggest? *When do you think akka 
> streams/http 1.0 final will be released?*
>
> Alternatively, do you think it would be a good choice to start with 
> rxscala (maybe using the reactive streams adapters, but I've never used 
> them) and then migrate to akka streams?
>
>
> Thanks
> G
>
> TL;DR: I've been using rxscala for another project, I really want to use 
> akka streams for a new one but need ssl, websocket and implementation 
> maturity of spray. What do I do?
>
>
>

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are 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+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Https support for akka-http

[richard]

Great to hear that! These days SSL is a firm requirement for anything web...

Cheers

On Tuesday, 3 February 2015 22:36:27 UTC+10, rklaehn wrote:
>
> Hi Roland,
>
> I am well aware that there is a lot going on behind the scenes. I meant 
> "nothing fancy" from a user perspective.
>
> Great to hear that it will be in 1.0!
>
> Am Dienstag, 3. Februar 2015 10:30:47 UTC+1 schrieb rkuhn:
>>
>> Hi Rüdiger,
>>
>> “nothing fancy” is quite a euphemism when talking about TLS ;-) We’re 
>> working on it right now, it is a tad more difficult than we anticipated, 
>> but Akka HTTP 1.0 will definitely have it.
>>
>> Regards,
>>
>> Roland
>>
>> 3 feb 2015 kl. 09:41 skrev rklaehn :
>>
>> Hi all,
>>
>> any estimate on when we can expect https support for akka-http? Will it 
>> be part of 1.0, or will we have to wait longer?
>>
>> I don't need anything fancy. Just the ability to connect to a REST api 
>> via https as a client.
>>
>> Cheers,
>>
>> Rüdiger
>>
>> -- 
>> >> Read the docs: http://akka.io/docs/
>> >> Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>> >> Search the archives: https://groups.google.com/group/akka-user
>> --- 
>> You received this message because you are 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 this group at http://groups.google.com/group/akka-user.
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>>
>>
>> *Dr. Roland Kuhn*
>> *Akka Tech Lead*
>> Typesafe  – Reactive apps on the JVM.
>> twitter: @rolandkuhn
>> 
>>  
>>

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are 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+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Re: [akka-http 1.0-M2] Trying to add backpressure

[Viktor Klang]

The best kids of bugs are the non-bugs :)

On Tue, Feb 3, 2015 at 9:06 PM, Luis Ángel Vicente Sánchez <
langel.gro...@gmail.com> wrote:

> As usual... after asking a question, you find the answer yourself. The
> tool I'm using, was keeping the same connection alive; therefore all
> requests from that connection were handle by the same branch.
>
> El martes, 3 de febrero de 2015, 19:57:04 (UTC), Luis Ángel Vicente
> Sánchez escribió:
>
>> Dear hakkers,
>>
>> I have been trying to add back pressure to an akka-http application using
>> a transformation Stage and I have found something... unexpected. I have
>> created a SafetyStage that buffers up to a maximum number of elements:
>>
>> https://github.com/lvicentesanchez/random/blob/master/src/main/scala/io/
>> github/lvicentesanchez/streams/stage/SafetyStage.scala
>>
>> I have also simulated a random failure with a simple random number
>> generator.
>>
>> Instead of handling akka-http connections using the method handleWith of
>> the ServerBinding object, I'm creating the following FlowGraph:
>>
>> https://github.com/lvicentesanchez/random/blob/master/src/main/scala/io/
>> github/lvicentesanchez/Boot.scala#L56
>>
>> The connection Source is transformed using the SafetyStage. If the
>> maximum capacity, or a random error happens, a Left object is created; if
>> not, a Right object is created. A FlexiRoute sends the Left requests to a
>> sink that handles every failed/discarded connnection (it completes them
>> with  503 error); Right requests go to a sink that handles them using an
>> akka-http router.
>>
>> In my tests, once one of the Sink handles the first IncomingConnnection,
>> all future connections are handled using the "handler" of that Sink. I.e.
>> if the random number generator decided that the first connection suffered
>> an error, all future connections would also be completed with a 503 error.
>>
>> I guess what I'm trying to do is fundamentally wrong, but I still don't
>> understand why the transformation stage is completely ignored once the
>> first connection is handled.
>>
>> Regards,
>>
>> Luis
>>
>  --
> >> Read the docs: http://akka.io/docs/
> >> Check the FAQ:
> http://doc.akka.io/docs/akka/current/additional/faq.html
> >> Search the archives: https://groups.google.com/group/akka-user
> ---
> You received this message because you are 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+unsubscr...@googlegroups.com.
> To post to this group, send email to akka-user@googlegroups.com.
> Visit this group at http://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Cheers,
√

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are 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+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Re: [akka-http 1.0-M2] Trying to add backpressure

[Viktor Klang]

The best typo as well.

s/kids/kinds

On Tue, Feb 3, 2015 at 9:16 PM, Viktor Klang  wrote:

> The best kids of bugs are the non-bugs :)
>
> On Tue, Feb 3, 2015 at 9:06 PM, Luis Ángel Vicente Sánchez <
> langel.gro...@gmail.com> wrote:
>
>> As usual... after asking a question, you find the answer yourself. The
>> tool I'm using, was keeping the same connection alive; therefore all
>> requests from that connection were handle by the same branch.
>>
>> El martes, 3 de febrero de 2015, 19:57:04 (UTC), Luis Ángel Vicente
>> Sánchez escribió:
>>
>>> Dear hakkers,
>>>
>>> I have been trying to add back pressure to an akka-http application
>>> using a transformation Stage and I have found something... unexpected. I
>>> have created a SafetyStage that buffers up to a maximum number of elements:
>>>
>>> https://github.com/lvicentesanchez/random/blob/master/src/main/scala/io/
>>> github/lvicentesanchez/streams/stage/SafetyStage.scala
>>>
>>> I have also simulated a random failure with a simple random number
>>> generator.
>>>
>>> Instead of handling akka-http connections using the method handleWith of
>>> the ServerBinding object, I'm creating the following FlowGraph:
>>>
>>> https://github.com/lvicentesanchez/random/blob/master/src/main/scala/io/
>>> github/lvicentesanchez/Boot.scala#L56
>>>
>>> The connection Source is transformed using the SafetyStage. If the
>>> maximum capacity, or a random error happens, a Left object is created; if
>>> not, a Right object is created. A FlexiRoute sends the Left requests to a
>>> sink that handles every failed/discarded connnection (it completes them
>>> with  503 error); Right requests go to a sink that handles them using an
>>> akka-http router.
>>>
>>> In my tests, once one of the Sink handles the first IncomingConnnection,
>>> all future connections are handled using the "handler" of that Sink. I.e.
>>> if the random number generator decided that the first connection suffered
>>> an error, all future connections would also be completed with a 503 error.
>>>
>>> I guess what I'm trying to do is fundamentally wrong, but I still don't
>>> understand why the transformation stage is completely ignored once the
>>> first connection is handled.
>>>
>>> Regards,
>>>
>>> Luis
>>>
>>  --
>> >> Read the docs: http://akka.io/docs/
>> >> Check the FAQ:
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>> >> Search the archives: https://groups.google.com/group/akka-user
>> ---
>> You received this message because you are 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+unsubscr...@googlegroups.com.
>> To post to this group, send email to akka-user@googlegroups.com.
>> Visit this group at http://groups.google.com/group/akka-user.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Cheers,
> √
>



-- 
Cheers,
√

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are 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+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Re: [akka-http 1.0-M2] Trying to add backpressure

[Luis Ángel Vicente Sánchez]

As usual... after asking a question, you find the answer yourself. The tool 
I'm using, was keeping the same connection alive; therefore all requests 
from that connection were handle by the same branch.

El martes, 3 de febrero de 2015, 19:57:04 (UTC), Luis Ángel Vicente Sánchez 
escribió:
>
> Dear hakkers,
>
> I have been trying to add back pressure to an akka-http application using 
> a transformation Stage and I have found something... unexpected. I have 
> created a SafetyStage that buffers up to a maximum number of elements:
>
>
> https://github.com/lvicentesanchez/random/blob/master/src/main/scala/io/github/lvicentesanchez/streams/stage/SafetyStage.scala
>
> I have also simulated a random failure with a simple random number 
> generator.
>
> Instead of handling akka-http connections using the method handleWith of 
> the ServerBinding object, I'm creating the following FlowGraph:
>
>
> https://github.com/lvicentesanchez/random/blob/master/src/main/scala/io/github/lvicentesanchez/Boot.scala#L56
>
> The connection Source is transformed using the SafetyStage. If the maximum 
> capacity, or a random error happens, a Left object is created; if not, a 
> Right object is created. A FlexiRoute sends the Left requests to a sink 
> that handles every failed/discarded connnection (it completes them with 
>  503 error); Right requests go to a sink that handles them using an 
> akka-http router.
>
> In my tests, once one of the Sink handles the first IncomingConnnection, 
> all future connections are handled using the "handler" of that Sink. I.e. 
> if the random number generator decided that the first connection suffered 
> an error, all future connections would also be completed with a 503 error.
>
> I guess what I'm trying to do is fundamentally wrong, but I still don't 
> understand why the transformation stage is completely ignored once the 
> first connection is handled.
>
> Regards,
>
> Luis
>

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are 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+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] [akka-http 1.0-M2] Trying to add backpressure

[Luis Ángel Vicente Sánchez]

Dear hakkers,

I have been trying to add back pressure to an akka-http application using a 
transformation Stage and I have found something... unexpected. I have 
created a SafetyStage that buffers up to a maximum number of elements:

https://github.com/lvicentesanchez/random/blob/master/src/main/scala/io/github/lvicentesanchez/streams/stage/SafetyStage.scala

I have also simulated a random failure with a simple random number 
generator.

Instead of handling akka-http connections using the method handleWith of 
the ServerBinding object, I'm creating the following FlowGraph:

https://github.com/lvicentesanchez/random/blob/master/src/main/scala/io/github/lvicentesanchez/Boot.scala#L56

The connection Source is transformed using the SafetyStage. If the maximum 
capacity, or a random error happens, a Left object is created; if not, a 
Right object is created. A FlexiRoute sends the Left requests to a sink 
that handles every failed/discarded connnection (it completes them with 
 503 error); Right requests go to a sink that handles them using an 
akka-http router.

In my tests, once one of the Sink handles the first IncomingConnnection, 
all future connections are handled using the "handler" of that Sink. I.e. 
if the random number generator decided that the first connection suffered 
an error, all future connections would also be completed with a 503 error.

I guess what I'm trying to do is fundamentally wrong, but I still don't 
understand why the transformation stage is completely ignored once the 
first connection is handled.

Regards,

Luis

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are 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+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Linking actors after creation

[Viktor Klang]

Hi Ugo,

Thanks for your question!

No, Akka does not support any notion of "adoption".

On Tue, Feb 3, 2015 at 6:15 PM, Ugo Matrangolo 
wrote:

> Hi,
>
> trying to wrap my head around Akka and I have simple question: is it
> possible to create a parent-child relationship between two actors *after*
> the 2nd one has been created (and not from the context of the first one, of
> course) ??
>
> Regards,
> Ugo
>
> --
> >> Read the docs: http://akka.io/docs/
> >> Check the FAQ:
> http://doc.akka.io/docs/akka/current/additional/faq.html
> >> Search the archives: https://groups.google.com/group/akka-user
> ---
> You received this message because you are 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+unsubscr...@googlegroups.com.
> To post to this group, send email to akka-user@googlegroups.com.
> Visit this group at http://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Cheers,
√

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are 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+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Recovering from the Quarantined state

[Mark Kegel]

We are using akka 2.3.4, but I don't think this is an issue with a specific 
version of akka. In fact the docs explicitly state that you have to restart 
the akka node after its been Quarantined.

I'm looking for some way to detect that my node has been quarantined so 
that I can force an exit, so that our puppet system can restart it, or just 
restart the akka system programmatically without exiting the process. This 
seems like basic error handling and recovery but I see nothing in the docs 
on how a person is supposed to handle this, or how they can even be 
notified of the issue.

Is there any kind of exception that bubbles back to user code, or a cluster 
state message that I can receive, for when my local akka instance can't 
rejoin the cluster?

Is there any way a supervisor hierarchy can help solve this problem?

If someone can point me to code that is able to respond and recover from 
such failures intelligently, and using akka approved idioms, that would be 
most appreciated.

Mark



On Tuesday, February 3, 2015 at 6:32:20 AM UTC-6, Patrik Nordwall wrote:
>
> What version of Akka are you using? We fixed some issue related to 
> quarantining in 2.3.9.
> /Patrik
>
> On Mon, Jan 26, 2015 at 5:20 PM, Mark Kegel  > wrote:
>
>> We are using akka in a clustered configuration at work. Its a very simple 
>> cluster with just three node types: an admin node, "live" nodes, and 
>> "preview" nodes. The admin node will manage nodes of the other two types, 
>> and ask for things like status and uptime. Every so often one of the 
>> live/preview nodes will become unresponsive to requests from the admin 
>> node. The only way we've been able to fix this is to restart the node.
>>
>> From reading the akka docs this seems to correspond to the node becoming 
>> Quarantined. While I appreciate that this state is necessary to maintain 
>> consistency, I'm at a loss in finding docs that show how to respond in code 
>> when this happens. On our admin node we'll know that some other 
>> live/preview node has failed and will require a restart, but what would 
>> work best is if we could have a service watching locally on the failed 
>> live/preview node that could force a restart of that nodes' JVM.
>>
>> Is there any kind of exception that bubbles back to user code, or a 
>> cluster state message that I can receive, for when my local akka instance 
>> can't rejoin the cluster?
>>
>> Is there any way a supervisor hierarchy can help solve this problem?
>>
>> If someone can point me to code that is able to respond and recover from 
>> such failures intelligently, and using akka approved idioms, that would be 
>> most appreciated.
>>
>> Mark
>>
>> -- 
>> >> Read the docs: http://akka.io/docs/
>> >> Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>> >> Search the archives: https://groups.google.com/group/akka-user
>> --- 
>> You received this message because you are 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 this group at http://groups.google.com/group/akka-user.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
>
> Patrik Nordwall
> Typesafe  -  Reactive apps on the JVM
> Twitter: @patriknw
>
>  

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are 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+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Linking actors after creation

[Ugo Matrangolo]

Hi,

trying to wrap my head around Akka and I have simple question: is it 
possible to create a parent-child relationship between two actors *after* 
the 2nd one has been created (and not from the context of the first one, of 
course) ??

Regards,
Ugo

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are 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+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Akka HTTP - back-pressure on incoming connections

[Luis Ángel Vicente Sánchez]

Ok... I guess using a FlexiRoute is not going to work. I forgot that is 
demand driven... :(

El martes, 3 de febrero de 2015, 13:53:10 (UTC), Luis Ángel Vicente Sánchez 
escribió:
>
> Did you make any progress on this? I have a flow that has process incoming 
> messages from a SQS queue and a REST endpoint; the message format and 
> processing is the same for both sources so my plan is to create a actor 
> publisher that will receive messages from the REST layer and an infinite 
> source that will pull messages from SQS. Messages coming from the REST 
> endpoint will have an optional "continuation" that will be used to complete 
> the HTTP request (the continuation function is created using the 
> completeWith directive).
>
>
> https://github.com/lvicentesanchez/random/blob/master/src/main/scala/io/github/lvicentesanchez/Boot.scala#L41
>
> My current publisher is unbounded,
>
>
> https://github.com/lvicentesanchez/random/blob/master/src/main/scala/io/github/lvicentesanchez/streams/source/UnboundedPublisher.scala
>
> so there is a potential memory issue there on top of the DDoS caused by 
> opening to many connections.
>
> I could implement the connection backpressure by creating a 
> BoundedPublisher that can hold a maximum number of elements in a buffer. If 
> we receive a request from the REST layer and the buffer is full, my 
> BoundedPublisher will use the continuation to complete the request with a 
> 503 Server busy. The problem with this approach is that I will have to 
> change the continuation to be able to handle the backpressure case and my 
> response objects would have to carry low level information, if I want to be 
> able to create a generic BoundPublisher source.
>
> An alternative approach would be to create a "buffering" FlexiRoute with 2 
> outputs connected to Source.connection. That flexiroute would buffer up-to 
> N requests; if a new request arrives, when the buffer is full, I would send 
> it to the "backpressure" output that would end in a sink that would will 
> complete the connection. If the buffer is not full it will be routed it to 
> the "routing" output, that will handle it using an akka-http routing Flow 
> (created with Route.asyncHandler)
>
> I'm leaning towards the second approach, but I don't know if it's feasible 
> or not.
>
> El miércoles, 28 de enero de 2015, 9:20:33 (UTC), Jean Rossier escribió:
>>
>> Hi Roland,
>>
>> thanks for the reply.
>> Do you know if this feature will be available in the 1.0 release ? if 
>> yes, when should it be available ? 
>>
>> Regarding the "awkward" implementation, and following your advise, I'm 
>> trying to do something like the following:
>> val serverBinding = Http(system).bind(interface = host, port = port)
>> serverBinding.connections.buffer(5, 
>> OverflowStrategy.dropTail).map(incomingConnectionToHttpRequest).mapAsync[HttpResponse](httpRequestToHttpResponseFuture).to(BlackholeSink).run()
>>
>> but I can't figure out how to get an HttpRequest out of an 
>> IncomingConnection. Is there any helper available in Akka HTTP ?
>>
>> Thanks,
>> Jean
>>
>> On Monday, January 26, 2015 at 10:35:59 AM UTC+1, rkuhn wrote:
>>>
>>> Hi Jean,
>>>
>>> calling “connection handleWith myFlow” is a really quick operation, 
>>> hence you see no back-pressure kicking in. The feature you are after is 
>>> currently rather awkward to implement, you’d have to replace handleWith 
>>> with 
>>> manually joining and running the connection’s Flow in order to obtain a 
>>> Future for its termination, and then you’d mapAsync into a BlackholeSink 
>>> instead of using a ForeachSink.
>>>
>>> Since this is a common thing people will want to do, we will provide 
>>> this (or an equivalent solution) with Akka HTTP; this is one of the joys of 
>>> using development previews :-) But thanks for reporting in any case!
>>>
>>> Regards,
>>>
>>> Roland
>>>
>>> 26 jan 2015 kl. 10:04 skrev Jean Rossier :
>>>
>>> I would have expected some failed requests.
>>> In my test, I'm sending 200 concurrent requests (the processing of each 
>>> request takes circa 200ms), Since I have a buffer of 5, I thought that some 
>>> requests would have been dropped and my client would have received some 
>>> errors. But, in my test, all requests are replied sucessfully.
>>> I thought OverflowStrategy.dropTail would drop the incoming requests 
>>> when the buffer is full.
>>>
>>> Jean
>>>
>>> On Monday, January 26, 2015 at 9:38:36 AM UTC+1, drewhk wrote:

 Hi Jean,

 On Mon, Jan 26, 2015 at 9:03 AM, Jean Rossier  
 wrote:

> Hello,
>
> I'm wondering if there is a way to use back-pressure mechanism on 
> incoming connections with Akka HTTP ? 
> The documentation mentions clearly that there is no back-pressure 
> applied to the connections Source if we use the startHandlingWith* 
> functions (
> http://doc.akka.io/api/akka-stream-and-http-experimental/1.0-M2/?_ga=1.267496717.2041479737.1421658563#akka.http.Http$$ServerBinding).
>  
>>>

[akka-user] Is there any way to change actor's hierarchy (eg: orphan actor)

[chansey97]

Hello,

I am creating a rendering system in my game engine. 

I found that Akka is a good solution for this.

My quesion is:

Is there any way to change actor's hierarchy (eg: orphan actor)

For instance, a scene graph:

- Terrain

- TankUUID12345

  - TurretUUID67890

Tank's actor path is user/TankUUID12345.

Tank Turret's actor path is user/TankUUID12345/TurretUUID67890.

When TankUUID12345 destroy, I expect TurretUUID67890 be still in the scene 
but orphan.

Path should be changed: user/TankUUID12345/TurretUUID67890 change to 
user/TurretUUID67890

Any advice would be very appreciated.

Very thanks.

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are 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+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Trying to persist heavy load cause a strange crash

[Avi Levi]

Hi ,
I want to start using actors with heavy rate messages . actor's last state 
is very important 
I was following the persistence example shown at 
here http://doc.akka.io/docs/akka/2.3.9/scala/persistence.html#event-sourcing 
I tried to send a heavy load of messages 

for (i <-0 to 10){
  persistentActor ! Cmd("foo"+i)
}


and using the persistAsync like this 

 val receiveCommand: Receive = {
case Cmd(data) =>
  persistAsync(Evt(s"${data}-${numEvents}"))(updateState)
case "snap"  => saveSnapshot(state)
case "print" => println(state)
  }



before shutdown I added Thread.sleep(15) to make sure that all persists . 
at first all seems to be ok , however re-running the app shows that some are 
going to dead-letter 


*[INFO] [02/03/2015 15:35:18.187] [example-akka.actor.default-dispatcher-3] 
[akka://example/user/persistentActor-4-scala] Message [java.lang.String] from 
Actor[akka://example/deadLetters] to 
Actor[akka://example/user/persistentActor-4-scala#1206460640] was not 
delivered. [1] dead letters encountered. This logging can be turned off or 
adjusted with configuration settings 'akka.log-dead-letters' and 
'akka.log-dead-letters-during-shutdown'.
[INFO] [02/03/2015 15:35:18.192] [example-akka.actor.default-dispatcher-3] 
[akka://example/user/persistentActor-4-scala] Message 
[akka.persistence.Recover] from 
Actor[akka://example/user/persistentActor-4-scala#1206460640] to 
Actor[akka://example/user/persistentActor-4-scala#1206460640] was not 
delivered. [2] dead letters encountered. This logging can be turned off or 
adjusted with configuration settings 'akka.log-dead-letters' and 
'akka.log-dead-letters-during-shutdown'.
*


or getting something like :

*[INFO] [02/03/2015 15:54:32.732] 
[example-akka.actor.default-dispatcher-11] 
[akka://example/user/persistentActor-4-scala] Message 
[akka.persistence.JournalProtocol$ReplayedMessage] from 
Actor[akka://example/deadLetters] to 
Actor[akka://example/user/persistentActor-4-scala#-973984210] was not 
delivered. [1] dead letters encountered. This logging can be turned off or 
adjusted with configuration settings 'akka.log-dead-letters' and 
'akka.log-dead-letters-during-shutdown'.*

*[INFO] [02/03/2015 15:54:32.735] [example-akka.actor.default-dispatcher-3] 
[akka://example/user/persistentActor-4-scala] Message 
[akka.persistence.JournalProtocol$ReplayedMessage] from 
Actor[akka://example/deadLetters] to 
Actor[akka://example/user/persistentActor-4-scala#-973984210] was not 
delivered. [10] dead letters encountered, no more dead letters will be 
logged. This logging can be turned off or adjusted with configuration 
settings 'akka.log-dead-letters' and 
'akka.log-dead-letters-during-shutdown'.*
*#*
*# A fatal error has been detected by the Java Runtime Environment:*
*#*
*#  SIGSEGV (0xb) at pc=0x7fa2a3e06b6a, pid=18870, tid=140335801857792*
*#*
*# JRE version: Java(TM) SE Runtime Environment (7.0_71-b14) (build 
1.7.0_71-b14)*
*# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.71-b01 mixed mode 
linux-amd64 compressed oops)*
*# Problematic frame:*
*# V  [libjvm.so+0x97bb6a]  Unsafe_GetNativeByte+0xaa*
*#*
*# Failed to write core dump. Core dumps have been disabled. To enable core 
dumping, try "ulimit -c unlimited" before starting Java again*
*#*
*# An error report file with more information is saved as:*
*# /home/tadmin/projects/akka-sample-persistence-scala/hs_err_pid18870.log*
*#*
*# If you would like to submit a bug report, please visit:*
*#   http://bugreport.sun.com/bugreport/crash.jsp*
*#*


how can I persist a state of an actor that should handle heavy rate of messages 
?


Thanks

Avi




-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are 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+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Akka HTTP - back-pressure on incoming connections

[Luis Ángel Vicente Sánchez]

Did you make any progress on this? I have a flow that has process incoming 
messages from a SQS queue and a REST endpoint; the message format and 
processing is the same for both sources so my plan is to create a actor 
publisher that will receive messages from the REST layer and an infinite 
source that will pull messages from SQS. Messages coming from the REST 
endpoint will have an optional "continuation" that will be used to complete 
the HTTP request (the continuation function is created using the 
completeWith directive).

https://github.com/lvicentesanchez/random/blob/master/src/main/scala/io/github/lvicentesanchez/Boot.scala#L41

My current publisher is unbounded,

https://github.com/lvicentesanchez/random/blob/master/src/main/scala/io/github/lvicentesanchez/streams/source/UnboundedPublisher.scala

so there is a potential memory issue there on top of the DDoS caused by 
opening to many connections.

I could implement the connection backpressure by creating a 
BoundedPublisher that can hold a maximum number of elements in a buffer. If 
we receive a request from the REST layer and the buffer is full, my 
BoundedPublisher will use the continuation to complete the request with a 
503 Server busy. The problem with this approach is that I will have to 
change the continuation to be able to handle the backpressure case and my 
response objects would have to carry low level information, if I want to be 
able to create a generic BoundPublisher source.

An alternative approach would be to create a "buffering" FlexiRoute with 2 
outputs connected to Source.connection. That flexiroute would buffer up-to 
N requests; if a new request arrives, when the buffer is full, I would send 
it to the "backpressure" output that would end in a sink that would will 
complete the connection. If the buffer is not full it will be routed it to 
the "routing" output, that will handle it using an akka-http routing Flow 
(created with Route.asyncHandler)

I'm leaning towards the second approach, but I don't know if it's feasible 
or not.

El miércoles, 28 de enero de 2015, 9:20:33 (UTC), Jean Rossier escribió:
>
> Hi Roland,
>
> thanks for the reply.
> Do you know if this feature will be available in the 1.0 release ? if yes, 
> when should it be available ? 
>
> Regarding the "awkward" implementation, and following your advise, I'm 
> trying to do something like the following:
> val serverBinding = Http(system).bind(interface = host, port = port)
> serverBinding.connections.buffer(5, 
> OverflowStrategy.dropTail).map(incomingConnectionToHttpRequest).mapAsync[HttpResponse](httpRequestToHttpResponseFuture).to(BlackholeSink).run()
>
> but I can't figure out how to get an HttpRequest out of an 
> IncomingConnection. Is there any helper available in Akka HTTP ?
>
> Thanks,
> Jean
>
> On Monday, January 26, 2015 at 10:35:59 AM UTC+1, rkuhn wrote:
>>
>> Hi Jean,
>>
>> calling “connection handleWith myFlow” is a really quick operation, 
>> hence you see no back-pressure kicking in. The feature you are after is 
>> currently rather awkward to implement, you’d have to replace handleWith with 
>> manually joining and running the connection’s Flow in order to obtain a 
>> Future for its termination, and then you’d mapAsync into a BlackholeSink 
>> instead of using a ForeachSink.
>>
>> Since this is a common thing people will want to do, we will provide this 
>> (or an equivalent solution) with Akka HTTP; this is one of the joys of 
>> using development previews :-) But thanks for reporting in any case!
>>
>> Regards,
>>
>> Roland
>>
>> 26 jan 2015 kl. 10:04 skrev Jean Rossier :
>>
>> I would have expected some failed requests.
>> In my test, I'm sending 200 concurrent requests (the processing of each 
>> request takes circa 200ms), Since I have a buffer of 5, I thought that some 
>> requests would have been dropped and my client would have received some 
>> errors. But, in my test, all requests are replied sucessfully.
>> I thought OverflowStrategy.dropTail would drop the incoming requests when 
>> the buffer is full.
>>
>> Jean
>>
>> On Monday, January 26, 2015 at 9:38:36 AM UTC+1, drewhk wrote:
>>>
>>> Hi Jean,
>>>
>>> On Mon, Jan 26, 2015 at 9:03 AM, Jean Rossier  
>>> wrote:
>>>
 Hello,

 I'm wondering if there is a way to use back-pressure mechanism on 
 incoming connections with Akka HTTP ? 
 The documentation mentions clearly that there is no back-pressure 
 applied to the connections Source if we use the startHandlingWith* 
 functions (
 http://doc.akka.io/api/akka-stream-and-http-experimental/1.0-M2/?_ga=1.267496717.2041479737.1421658563#akka.http.Http$$ServerBinding).
  
 Therefore, I tried to do something like the following:
 val serverBinding = Http(system).bind(interface = "localhost", port = 
 port)
 serverBinding.connections.buffer(5, 
 OverflowStrategy.dropTail).to(ForeachSink(_ handleWith myFlow)).run()

 But, when sending a bunch of concurrent connections to my

Re: [akka-user] Re: Send message from netty code to actor system

[Jabbar Azam]

Oops I meant channel handler.

On Tuesday, 3 February 2015 13:32:21 UTC, Jabbar Azam wrote:
>
> Hello,
>
> Sorry for the late reply. For some reason the forum messages didn't get 
> forwarded to my email.
>
> I was thinking of using typedactors because I am trying to integrate non 
> actor code(cloudhopper SMPP which uses netty) into an actor system. Netty 
> does use callbacks so I can use asynchronous behaviour.
>
> Do you think I could encapsulate a netty channel inside an actor? A netty 
> channel can call callbacks whenever something changes in the channel.
>
> On Friday, 30 January 2015 12:38:14 UTC, Björn Antonsson wrote:
>>
>> Hi,
>>
>> Are you sure that you need to block the sending code while the actor does 
>> its work? Is there an asynchronous API in netty that you can use where the 
>> actor would invoke a callback when it has finished processing the packet?
>>
>> B/
>>
>> On 27 January 2015 at 11:03:26, Jabbar Azam (aja...@gmail.com) wrote:
>>
>> I think I need to look at typedactors.
>>
>> On Tuesday, 27 January 2015 09:29:43 UTC, Jabbar Azam wrote: 
>>>
>>> Hello, 
>>>
>>> How do I send a message from java non actor based code into an actor 
>>> system? The code will be running on the same node and will be part of the 
>>> same source code. So netty will be running, receiving packets, which will 
>>> send any received packets into an actor system. The actor system will 
>>> process the packets and then send the response payload back to the netty 
>>> code.
>>>
>>>
>>>   --
>> >> Read the docs: http://akka.io/docs/
>> >> Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>> >> Search the archives: https://groups.google.com/group/akka-user
>> ---
>> You received this message because you are 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 this group at http://groups.google.com/group/akka-user.
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>> -- 
>> Björn Antonsson
>> Typesafe  – Reactive Apps on the JVM
>> twitter: @bantonsson 
>>
>>

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are 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+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Re: Send message from netty code to actor system

[Jabbar Azam]

Hello,

I can't use Xitrum. I'm using Cloudhopper-smpp which uses netty. I don't 
fancy writing a SMPP library.

On Monday, 2 February 2015 09:45:33 UTC, Ngoc Dao wrote:
>
> You can try Xitrum web framework (scroll down to see the Akka actor 
> example):
> http://xitrum-framework.github.io/ 
> 
>
>
> On Tuesday, January 27, 2015 at 6:29:43 PM UTC+9, Jabbar Azam wrote:
>>
>> Hello,
>>
>> How do I send a message from java non actor based code into an actor 
>> system? The code will be running on the same node and will be part of the 
>> same source code. So netty will be running, receiving packets, which will 
>> send any received packets into an actor system. The actor system will 
>> process the packets and then send the response payload back to the netty 
>> code.
>>
>>
>>

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are 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+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Re: Send message from netty code to actor system

[Jabbar Azam]

Hello,

Sorry for the late reply. For some reason the forum messages didn't get 
forwarded to my email.

I was thinking of using typedactors because I am trying to integrate non 
actor code(cloudhopper SMPP which uses netty) into an actor system. Netty 
does use callbacks so I can use asynchronous behaviour.

Do you think I could encapsulate a netty channel inside an actor? A netty 
channel can call callbacks whenever something changes in the channel.

On Friday, 30 January 2015 12:38:14 UTC, Björn Antonsson wrote:
>
> Hi,
>
> Are you sure that you need to block the sending code while the actor does 
> its work? Is there an asynchronous API in netty that you can use where the 
> actor would invoke a callback when it has finished processing the packet?
>
> B/
>
> On 27 January 2015 at 11:03:26, Jabbar Azam (aja...@gmail.com 
> ) wrote:
>
> I think I need to look at typedactors.
>
> On Tuesday, 27 January 2015 09:29:43 UTC, Jabbar Azam wrote: 
>>
>> Hello, 
>>
>> How do I send a message from java non actor based code into an actor 
>> system? The code will be running on the same node and will be part of the 
>> same source code. So netty will be running, receiving packets, which will 
>> send any received packets into an actor system. The actor system will 
>> process the packets and then send the response payload back to the netty 
>> code.
>>
>>
>>   --
> >> Read the docs: http://akka.io/docs/
> >> Check the FAQ: 
> http://doc.akka.io/docs/akka/current/additional/faq.html
> >> Search the archives: https://groups.google.com/group/akka-user
> ---
> You received this message because you are 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 this group at http://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>
>
> -- 
> Björn Antonsson
> Typesafe  – Reactive Apps on the JVM
> twitter: @bantonsson 
>
>

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are 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+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Https support for akka-http

[rklaehn]

Hi Roland,

I am well aware that there is a lot going on behind the scenes. I meant 
"nothing fancy" from a user perspective.

Great to hear that it will be in 1.0!

Am Dienstag, 3. Februar 2015 10:30:47 UTC+1 schrieb rkuhn:
>
> Hi Rüdiger,
>
> “nothing fancy” is quite a euphemism when talking about TLS ;-) We’re 
> working on it right now, it is a tad more difficult than we anticipated, 
> but Akka HTTP 1.0 will definitely have it.
>
> Regards,
>
> Roland
>
> 3 feb 2015 kl. 09:41 skrev rklaehn >:
>
> Hi all,
>
> any estimate on when we can expect https support for akka-http? Will it be 
> part of 1.0, or will we have to wait longer?
>
> I don't need anything fancy. Just the ability to connect to a REST api via 
> https as a client.
>
> Cheers,
>
> Rüdiger
>
> -- 
> >> Read the docs: http://akka.io/docs/
> >> Check the FAQ: 
> http://doc.akka.io/docs/akka/current/additional/faq.html
> >> Search the archives: https://groups.google.com/group/akka-user
> --- 
> You received this message because you are 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 this group at http://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>
>
>
>
> *Dr. Roland Kuhn*
> *Akka Tech Lead*
> Typesafe  – Reactive apps on the JVM.
> twitter: @rolandkuhn
> 
>  
>

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are 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+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] ClusterClient load balancing

[Patrik Nordwall]

On Sat, Jan 24, 2015 at 5:08 PM, Hengky Sucanda 
wrote:

> Hi Martynas,
>
> Yes i think you are right, what i meant was about the control of the load
> balancing. The frontend node actually is part of the cluster as well, they
> just have different role. So i think it was clear that it would not be
> possible now if i want to change the load balancing mechanism.
>

Don't use ClusterClient when client and server are part of same cluster.
Then you should use DistributedPubSub, which provides same features.
You can use a few different routing strategies with pub-sub. See
http://doc.akka.io/docs/akka/2.3.9/contrib/distributed-pub-sub.html

/Patrik


>
>
> On Friday, January 23, 2015 at 10:34:44 PM UTC+7, Martynas Mickevičius
> wrote:
>>
>> Hi Hengky,
>>
>> what do you mean by load balancing? As you have already discovered if
>> several actors are registered to the same path, a message for that path
>> will by sent to randomly picked actor. This is random load balancing.
>>
>> If you need more control, you can join the frontend node to the cluster
>> and use PubSub (which is actually used to implement ClusterClient) or
>> Cluster Sharding.
>>
>> On Fri, Jan 23, 2015 at 9:20 AM, Hengky Sucanda 
>> wrote:
>>
>>> Hi Guys,
>>>
>>> I'm currently developing an application using Play and Akka, and
>>> currently is deploying one frontend nodes with multiple backend nodes. The
>>> frontend node connects to the backend using ClusterClient. My question is,
>>> does ClusterClient have load balancing mechanism so it can properly
>>> distribute the message to other backend nodes? From what i have read in the
>>> docs, it says that ClusterClient will send it to a random destination in
>>> case of a multiple entries matching the path. Is there a way for me to load
>>> balance the frontend and backend message sending if i am using
>>> ClusterClient?
>>>
>>> --
>>> >> Read the docs: http://akka.io/docs/
>>> >> Check the FAQ: http://doc.akka.io/docs/akka/
>>> current/additional/faq.html
>>> >> Search the archives: https://groups.google.com/
>>> group/akka-user
>>> ---
>>> You received this message because you are 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 this group at http://groups.google.com/group/akka-user.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Martynas Mickevičius
>> Typesafe  – Reactive
>>  Apps on the JVM
>>
>  --
> >> Read the docs: http://akka.io/docs/
> >> Check the FAQ:
> http://doc.akka.io/docs/akka/current/additional/faq.html
> >> Search the archives: https://groups.google.com/group/akka-user
> ---
> You received this message because you are 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+unsubscr...@googlegroups.com.
> To post to this group, send email to akka-user@googlegroups.com.
> Visit this group at http://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>



-- 

Patrik Nordwall
Typesafe  -  Reactive apps on the JVM
Twitter: @patriknw

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are 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+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Recovering from the Quarantined state

[Patrik Nordwall]

What version of Akka are you using? We fixed some issue related to
quarantining in 2.3.9.
/Patrik

On Mon, Jan 26, 2015 at 5:20 PM, Mark Kegel  wrote:

> We are using akka in a clustered configuration at work. Its a very simple
> cluster with just three node types: an admin node, "live" nodes, and
> "preview" nodes. The admin node will manage nodes of the other two types,
> and ask for things like status and uptime. Every so often one of the
> live/preview nodes will become unresponsive to requests from the admin
> node. The only way we've been able to fix this is to restart the node.
>
> From reading the akka docs this seems to correspond to the node becoming
> Quarantined. While I appreciate that this state is necessary to maintain
> consistency, I'm at a loss in finding docs that show how to respond in code
> when this happens. On our admin node we'll know that some other
> live/preview node has failed and will require a restart, but what would
> work best is if we could have a service watching locally on the failed
> live/preview node that could force a restart of that nodes' JVM.
>
> Is there any kind of exception that bubbles back to user code, or a
> cluster state message that I can receive, for when my local akka instance
> can't rejoin the cluster?
>
> Is there any way a supervisor hierarchy can help solve this problem?
>
> If someone can point me to code that is able to respond and recover from
> such failures intelligently, and using akka approved idioms, that would be
> most appreciated.
>
> Mark
>
> --
> >> Read the docs: http://akka.io/docs/
> >> Check the FAQ:
> http://doc.akka.io/docs/akka/current/additional/faq.html
> >> Search the archives: https://groups.google.com/group/akka-user
> ---
> You received this message because you are 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+unsubscr...@googlegroups.com.
> To post to this group, send email to akka-user@googlegroups.com.
> Visit this group at http://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>



-- 

Patrik Nordwall
Typesafe  -  Reactive apps on the JVM
Twitter: @patriknw

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are 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+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Akka HTTP activator

[Akka Team]

Hi Łukasz,

Thank you, this really looks cool!

-Endre

On Sat, Jan 31, 2015 at 3:44 PM, Łukasz Sowa  wrote:

> Hey, I've just published first (to my best knowledge) akka-http activator
> with comprehensive tutorial to spare others time & pain figuring out
> differences between akka-http & Spray:
> https://typesafe.com/activator/template/akka-http-microservice
>
> It all started here:
> https://groups.google.com/forum/#!topic/akka-user/8m4gDs2vDpY - thanks
> for contributions!
>
> Best,
> Łukasz
>
> --
> >> Read the docs: http://akka.io/docs/
> >> Check the FAQ:
> http://doc.akka.io/docs/akka/current/additional/faq.html
> >> Search the archives: https://groups.google.com/group/akka-user
> ---
> You received this message because you are 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+unsubscr...@googlegroups.com.
> To post to this group, send email to akka-user@googlegroups.com.
> Visit this group at http://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Akka Team
Typesafe - The software stack for applications that scale
Blog: letitcrash.com
Twitter: @akkateam

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are 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+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Https support for akka-http

[Roland Kuhn]

Hi Rüdiger,

“nothing fancy” is quite a euphemism when talking about TLS ;-) We’re working 
on it right now, it is a tad more difficult than we anticipated, but Akka HTTP 
1.0 will definitely have it.

Regards,

Roland

> 3 feb 2015 kl. 09:41 skrev rklaehn :
> 
> Hi all,
> 
> any estimate on when we can expect https support for akka-http? Will it be 
> part of 1.0, or will we have to wait longer?
> 
> I don't need anything fancy. Just the ability to connect to a REST api via 
> https as a client.
> 
> Cheers,
> 
> Rüdiger
> 
> -- 
> >> Read the docs: http://akka.io/docs/ 
> >> Check the FAQ: 
> >> http://doc.akka.io/docs/akka/current/additional/faq.html 
> >> 
> >> Search the archives: https://groups.google.com/group/akka-user 
> >> 
> --- 
> You received this message because you are 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+unsubscr...@googlegroups.com 
> .
> To post to this group, send email to akka-user@googlegroups.com 
> .
> Visit this group at http://groups.google.com/group/akka-user 
> .
> For more options, visit https://groups.google.com/d/optout 
> .



Dr. Roland Kuhn
Akka Tech Lead
Typesafe  – Reactive apps on the JVM.
twitter: @rolandkuhn
 

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are 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+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Https support for akka-http

[rklaehn]

Hi all,

any estimate on when we can expect https support for akka-http? Will it be 
part of 1.0, or will we have to wait longer?

I don't need anything fancy. Just the ability to connect to a REST api via 
https as a client.

Cheers,

Rüdiger

-- 
>>  Read the docs: http://akka.io/docs/
>>  Check the FAQ: 
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>  Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are 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+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.