No luck for me, moving on.
--
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 "
Thank you!
On Thursday, July 10, 2014 12:43:22 AM UTC+8, √ wrote:
>
> I believe this code answers it :)
>
>
> https://github.com/akka/akka/blob/release-2.3-dev/akka-stream/src/main/scala/akka/stream/impl/FlowImpl.scala#L71
>
>
> On Wed, Jul 9, 2014 at 6:23 PM, Sean Zhong > wrote:
>
>> When checki
I believe this code answers it :)
https://github.com/akka/akka/blob/release-2.3-dev/akka-stream/src/main/scala/akka/stream/impl/FlowImpl.scala#L71
On Wed, Jul 9, 2014 at 6:23 PM, Sean Zhong wrote:
> When checking examples from https://github.com/adamw/reactmq.git, we saw
> two similar usage of
When checking examples from https://github.com/adamw/reactmq.git, we saw
two similar usage of Flow:
One is:
Flow(conn.inputStream)
.mapConcat(reconcileFrames.apply)
.produceTo(materializer, sendToQueueConsumer)
The other is:
Flow(receiveFromQueueProducer
Aha. In that case it would probably be better to join the cluster and
listen on some ClusterState topic on the distributed PubSub.
On Wed, Jul 9, 2014 at 12:13 PM, Muki wrote:
> Hi Martynas,
>
> Ah, nice. I will try that out as a starting point.
>
> The documentation only shows *ClusterClient*
I see that there are some errors while instantiating actors:
[WARN] [07/09/2014 10:13:24.242]
[BrainRoutingSystem-akka.actor.default-dispatcher-3]
[akka.tcp://BrainRoutingSystem@Vortex:2553/system/endpointManager/
reliableEndpointWriter-akka.tcp%3A%2F%2FDisBrainBackend%40Vortex%3A2552-0]
Associati
I think you have a fair point. Logging causes of the exceptions could be
useful under the DEBUG level. Would you be up for submitting a PR for this?
:)
On Tue, Jul 8, 2014 at 11:47 PM, Mint wrote:
> Hi Martynas,
>
> Thank you very much for this information. I'll try to subscribe to event
> stre
Hi Martynas,
Ah, nice. I will try that out as a starting point.
The documentation only shows *ClusterClient* requests. If I want
to update data on a websocket (e.g. cluster nodes online),
I would have to implement a polling strategy? Like scheduling
a *ClusterState* message to a *ClusterMonitor*
Right :-)
Just tried with 2.3.3 and I observe the same behaviour
Pierre
Il giorno mercoledì 9 luglio 2014 10:46:49 UTC+2, Konrad Malawski ha
scritto:
>
> This could be one known issue in 2.3.2, please upgrade to 2.3.3 (or
> better, to 2.3.4 right away) and we’ll talk :-)
>
> — k
>
> On 9 July
This could be one known issue in 2.3.2, please upgrade to 2.3.3 (or better, to
2.3.4 right away) and we’ll talk :-)
— k
On 9 July 2014 at 10:44:17, Pierre Falda (p.fa...@disbrain.com) wrote:
Hello everyone,
I had a simple two layer akka (test)deployment with akka 2.2.1 and was working
well.
It
Hello everyone,
I had a simple two layer akka (test)deployment with akka 2.2.1 and was
working well.
It was quite simple: a machine is responsible for router creation and
forwarding requests it receives from play servers to the worker.
Some days ago I tried to switch to 2.3.2 and I found some
11 matches
Mail list logo
