Re: [akka-user] Re: akka-stream: How to define a Processor in Java

2016-04-17 Thread Johan Andrén 
In general you should seldom have to write your own stages as there is a very 
rich set of built in stages provided. For example if you have a 
request-response you want to perform with an actor you can use mapAsync to 
interact with the actor from a stream. Something like this:

val myProcessingActor: ActorRef = ???
val mySource: Source[Thing, NotUsed] = ???

val responses: Source[Response, NotUsed] = 
  mySource.mapAsync(1)(thing => (myProcessingActor ? 
Request(thing)).mapTo[Response])

responses.runForeach(println)

The first parameter to mapAsync specifies the maximum number of concurrent 
ongoing requests, if there is only one actor there is no need to allow more 
than 1 concurrent outstanding request as they will just queue up in the actor 
mailbox if you do.

When you materialize a stream using run it will be running inside one or more 
actors, but that is an internal implementation detail and the only part of that 
you will see is having to provide an ActorSystem to the ActorMaterializer which 
is needed to materialize a flow.

--
Johan Andrén
Akka Team, Lightbend Inc.


> 17 apr. 2016 kl. 04:35 skrev Guofeng Zhang :
> 
> Johan,
> 
> I read it, but Integration with actors is only a stub part. There is no 
> sample to demo how to do it. Is there any link or akka-stream test cast to 
> demo how to do it in detail?
> 
> Another question, the doc says that for a stream there are actors created to 
> run the stream. so if I use akka-stream, shall still need to coding actors 
> for a stream?
> 
> Thanks for your reply very much!
> 
> Guofeng
> 
> 
> 
> 
> On Sat, Apr 16, 2016 at 2:16 AM, Johan Andrén  > wrote:
> Hi Goufeng,
> 
> I would recommend you to read up on GraphStage rather than the 
> ActorSubscriber and ActorPublisher as it is a much more straight forward way 
> to create custom stages. You can find a pretty thorough walkthrough of how it 
> works and nice code samples in Java for GraphStage in the docs here: 
> http://doc.akka.io/docs/akka/2.4.4/java/stream/stream-customize.html 
> 
> 
> --
> Johan Andrén
> Akka Team, Lightbend Inc.
> 
> 
> 
> On Wednesday, April 13, 2016 at 8:58:45 AM UTC+2, Guofeng Zhang wrote:
> Hi,
> 
> I am learning akka-stream, so I want to understand the low-level detail. I 
> found the following post is very useful for my case:
> http://bryangilbert.com/blog/2015/02/04/akka-reactive-streams/ 
> 
> 
> In this post, the processor is defined in Scala as the following:
> class DoublingProcessor extends ActorSubscriber with 
> ActorPublisher[BigInteger] { }
> 
> My question is:
>  How to define the above process in Java?
> 
> Thanks for your help.
> 
> Guofeng
> 
> 
> -- 
> >> 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 https://groups.google.com/group/akka-user 
> .
> For more options, visit https://groups.google.com/d/optout 
> .
> 
> 
> -- 
> >> 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 a topic in the Google 
> Groups "Akka User List" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/akka-user/v23yQwhDhh8/unsubscribe 
> .
> To unsubscribe from this group and all its topics, 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 https://groups.google.com/group/akka-user 
> .
> For more options, visit https://groups.google.com/d/optout 
> .

--

Re: [akka-user] Akka Cluster: Why Member does not have name property?

2016-04-17 Thread Patrik Nordwall 
No, MemberUp is a notification that a node/ActorSystem was added to the
cluster.

You can read about ActorSystem here:
http://doc.akka.io/docs/akka/2.4.4/general/actor-systems.html

/Patrik

lör 16 apr. 2016 kl. 21:48 skrev Prasanna Thirumalai :

> I am sorry but I do not understand the difference between Member and an
> Actor. Isn't ActorSystem a hierarchical group of actors? When one creates
> an Actor in the ActorSystem, doesn't everyone in the system get a
> notification of new actor aka MemberUp?
>
>
> On Saturday, April 16, 2016 at 11:22:02 AM UTC-7, Patrik Nordwall wrote:
>
>> I think there is some misunderstanding. Member corresponds to an
>> ActorSystem, not an actor.
>>
>> /Patrik
>>
>> lör 16 apr. 2016 kl. 18:23 skrev Prasanna Thirumalai > >:
>>
> When I subscribe of cluster events, the 'Member' entity does not have any
>>> name property where this property is same as given to the corresponding
>>> actor in system.actorOf. Because of this, there does not seem to be a way
>>> to get ActorSelection for a member on a MemberUp event. I get around it by
>>> having a specially formatted role for each worker that gives its name. So
>>> why do cluster events not have the name property?
>>>
>>>
>>> --
>>> >> 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 https://groups.google.com/group/akka-user.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> >> 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 https://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
>>  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 https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] What config affects the number of threads for an ActorSystem?

2016-04-17 Thread Steve Rehrauer 
I have an application that doesn't specify a custom dispatcher.

We see the number of threads maxing out at 50, and would like to increase 
it.

This doesn't seem to line up with any of the default config I see in Akka?  
I see 

 akka.actor.default-dispatcher.fork-join-executor.parallelism-max = 64

and I've tried raising this particular config, but still don't see more 
than 50 active threads.

How can I affect this?

-- 
>>  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 https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Akka Cluster: Why Member does not have name property?

2016-04-17 Thread Prasanna Thirumalai 
Yes, I understand MemberUp is an event when a node comes up, but the 
MemberUp event contains Member attribute in it. 
(MemberUp(member)). Shouldn't that Member attribute in the 
MemberUp event contain the name of the node that came up in the cluster?

On Sunday, April 17, 2016 at 3:58:46 AM UTC-7, Patrik Nordwall wrote:
>
> No, MemberUp is a notification that a node/ActorSystem was added to the 
> cluster.
>
> You can read about ActorSystem here: 
> http://doc.akka.io/docs/akka/2.4.4/general/actor-systems.html
>
> /Patrik
>
> lör 16 apr. 2016 kl. 21:48 skrev Prasanna Thirumalai  >:
>
>> I am sorry but I do not understand the difference between Member and an 
>> Actor. Isn't ActorSystem a hierarchical group of actors? When one creates 
>> an Actor in the ActorSystem, doesn't everyone in the system get a 
>> notification of new actor aka MemberUp?
>>
>>
>> On Saturday, April 16, 2016 at 11:22:02 AM UTC-7, Patrik Nordwall wrote:
>>
>>> I think there is some misunderstanding. Member corresponds to an 
>>> ActorSystem, not an actor.
>>>
>>> /Patrik
>>>
>>> lör 16 apr. 2016 kl. 18:23 skrev Prasanna Thirumalai >> >:
>>>
>> When I subscribe of cluster events, the 'Member' entity does not have any 
 name property where this property is same as given to the corresponding 
 actor in system.actorOf. Because of this, there does not seem to be a way 
 to get ActorSelection for a member on a MemberUp event. I get around it by 
 having a specially formatted role for each worker that gives its name. So 
 why do cluster events not have the name property?


 -- 
 >> 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 https://groups.google.com/group/akka-user.
 For more options, visit https://groups.google.com/d/optout.

>>> -- 
>> >> 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 https://groups.google.com/group/akka-user.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
>>  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 https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Akka Singleton Cluster: Knowing when standby master has become primary

2016-04-17 Thread Prasanna Thirumalai 
In a singleton cluster with 2 seed nodes, one of them is primary master and 
other one is standby, what notification should I subscribe to in the 
standby master that informs it that it has been moved to primary?

-- 
>>  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 https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Akka Cluster: Why Member does not have name property?

2016-04-17 Thread Patrik Nordwall 
The address contains the the name of the ActorSystem, but that is not in
any way related to the actor that you mentioned earlier. The actor system
name must be the same for all cluster nodes, so that is not what you are
looking for. I'll read your other posts and try to understand what you want
to do.

/Patrik

sön 17 apr. 2016 kl. 19:00 skrev Prasanna Thirumalai :

> Yes, I understand MemberUp is an event when a node comes up, but the
> MemberUp event contains Member attribute in it.
> (MemberUp(member)). Shouldn't that Member attribute in the
> MemberUp event contain the name of the node that came up in the cluster?
>
>
> On Sunday, April 17, 2016 at 3:58:46 AM UTC-7, Patrik Nordwall wrote:
>
>> No, MemberUp is a notification that a node/ActorSystem was added to the
>> cluster.
>>
>> You can read about ActorSystem here:
>> http://doc.akka.io/docs/akka/2.4.4/general/actor-systems.html
>>
>> /Patrik
>>
>> lör 16 apr. 2016 kl. 21:48 skrev Prasanna Thirumalai > >:
>>
>>> I am sorry but I do not understand the difference between Member and an
>>> Actor. Isn't ActorSystem a hierarchical group of actors? When one creates
>>> an Actor in the ActorSystem, doesn't everyone in the system get a
>>> notification of new actor aka MemberUp?
>>>
>>>
>>> On Saturday, April 16, 2016 at 11:22:02 AM UTC-7, Patrik Nordwall wrote:
>>>
 I think there is some misunderstanding. Member corresponds to an
 ActorSystem, not an actor.

 /Patrik

 lör 16 apr. 2016 kl. 18:23 skrev Prasanna Thirumalai <
 prasa...@gmail.com>:

>>> When I subscribe of cluster events, the 'Member' entity does not have
> any name property where this property is same as given to the 
> corresponding
> actor in system.actorOf. Because of this, there does not seem to be a way
> to get ActorSelection for a member on a MemberUp event. I get around it by
> having a specially formatted role for each worker that gives its name. So
> why do cluster events not have the name property?
>
>
> --
> >> 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 https://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>
 --
>>> >> 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 https://groups.google.com/group/akka-user.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> >> 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 https://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
>>  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 https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Akka Singleton Cluster: Inconsistent cluster behavior on worker restart

2016-04-17 Thread Patrik Nordwall 
On Sat, Apr 16, 2016 at 5:57 PM, Prasanna Thirumalai 
wrote:

> I am using Akka Cluster 2.4.3 and trying to setup a simple cluster in my
> machine to understand its working better. I have a singleton cluster with
> remoting enabled with primary and standby master and one worker node. Each
> of these 3 run in separate JVMs
>
> Things work fine when all the nodes are started the first time. If I kill
> and restart the worker, I see following issues happening
>
> *Restart Worker*
>
> When the worker comes back after restart, the master on receiving MemberUp 
> event
> tries to resolve for the actorRef from the member address the following way
>
> context.actorSelection(member.address.toString).resolveOne(15 seconds)
>
> Actor selection is for sending messages to an actor path, not an
ActorSystem address (hostname:port). See
http://doc.akka.io/docs/akka/2.4.4/general/addressing.html

Perhaps you should also study this example:
http://doc.akka.io/docs/akka/2.4.4/scala/cluster-usage.html#Subscribe_to_Cluster_Events

/Patrik


> This fails with an exception saying ActorNotFound. This works with no
> problem when all the nodes are coming up for the first time in the cluster.
>
> *Restart worker again*
>
> This time, the worker comes up with the following message
>
> [WARN] [04/15/2016 18:24:24.991]
> [clustersystem-akka.remote.default-remote-dispatcher-5]
> [akka.remote.Remoting] Tried to associate with unreachable remote address
> [akka.tcp://clustersystem@host1:2551]. Address is now gated for 5000 ms,
> all messages to this address will be delivered to dead letters. Reason:
> [The remote system has quarantined this system. No further associations to
> the remote system are possible until this system is restarted.]
>
> *Restart worker again*
>
> This time the resolveOne on a MemberUp event works.
>
> I am having a bit of difficulty in understanding what is happening here, I
> have looked into the docs but I did not find anything that will help me in
> there.
>
> *application.conf*
>
> akka {
>   actor {
> provider = "akka.cluster.ClusterActorRefProvider"
>   }
>
>   remote {
> enabled-transports = ["akka.remote.netty.tcp"]
>   }
>
>   log-dead-letters = off
>   jvm-exit-on-fatal-error = on
>
>   loglevel = "DEBUG"
>
>   remote {
> log-remote-lifecycle-events = off
> netty.tcp {
>   hostname = "host1"
>   port = 0
> }
>   }
>
>   cluster {
> seed-nodes = [
>   "akka.tcp://clustersystem@host1:2551",
>   "akka.tcp://clustersystem@host1:2552"]
>
> auto-down-unreachable-after = 10s
>   }
>
>
>   extensions = ["akka.cluster.metrics.ClusterMetricsExtension"]}
>
> I start master nodes at ports 2551 and 2552 (provide the ports as command
> line args) and I start the worker on port 3551
>
>
> Posted the same question to stackoverflow:
> http://stackoverflow.com/questions/36659242/akka-singleton-cluster-resolveonce-of-a-worker-by-master-fails-after-restart
>
> --
> >> 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 https://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>



-- 

Patrik Nordwall
Akka Tech Lead
Lightbend  -  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 https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Akka Singleton Cluster: Knowing when standby master has become primary

2016-04-17 Thread Patrik Nordwall 
Perhaps take a look at Cluster Singleton documentation:
http://doc.akka.io/docs/akka/2.4.4/scala/cluster-singleton.html#cluster-singleton-scala

/Patrik

On Sun, Apr 17, 2016 at 7:01 PM, Prasanna Thirumalai 
wrote:

> In a singleton cluster with 2 seed nodes, one of them is primary master
> and other one is standby, what notification should I subscribe to in the
> standby master that informs it that it has been moved to primary?
>
> --
> >> 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 https://groups.google.com/group/akka-user.
> For more options, visit https://groups.google.com/d/optout.
>



-- 

Patrik Nordwall
Akka Tech Lead
Lightbend  -  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 https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Re: [akka-user] Akka HTTP performance for short lived connections

2016-04-17 Thread Adam 
OK, thanks.

So just to be certain - in the meantime, is it expected that I'll see Akka HTTP 
perform ~100 times worse (or let's just say "much worse") than Play framework 
for such cases?

I was hoping it's actually something that I'm doing wrong because I was 
expecting it to be worse per the README, but still at the same order of 
magnitude.

-- 
>>  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 https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[akka-user] Re: Akka HTTP performance for short lived connections

2016-04-17 Thread Andrew Gaydenko 
Adam, just curious, can you, please, supply some example ApacheBench output?

-- 
>>  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 https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.