Cheers,
> Martin
>
> On 16.05.14 08:41, Raymond Tay wrote:
>
> Hi akka devs,
>
> I have a scenario where a `akka-cluster-2.3.2` is running
> `akka-persistence-2.3.2` and 2 nodes participate. Next, we create two
> _distinct_ sets of (processor, view, actor, channel)
Hi akka devs,
I have a scenario where a `akka-cluster-2.3.2` is running
`akka-persistence-2.3.2` and 2 nodes participate. Next, we create two
_distinct_ sets of (processor, view, actor, channel) to represent two
domain objects in our application. Next, we have the two data sets write
stuff to
> On 08.05.14 08:23, Raymond Tay wrote:
>
> Hi all,
>
> Was wondering whether LevelDB supports multiple yet distinct processors
> into the same journal within the same `ActorSystem` ?
>
>
> Sure, they only must have different processorIds. An application only ha
Hi all,
Was wondering whether LevelDB supports multiple yet distinct processors
into the same journal within the same `ActorSystem` ?
Br,
Raymond
--
>> Read the docs: http://akka.io/docs/
>> Check the FAQ:
>> http://doc.akka.io/docs/akka/current/additional/fa
kendAddress) / "user" /
"ShadowFrontend")
// use `backend` in callbacks instead
}
Instead of using Play's Akka system. Anyone else met this issue ? Seems
like i'm the only one hitting this. Oh well...
On Monday, April 28, 2014 5:14:15 PM UTC+8, Raymond Tay wrote:
&
environment running
Play 2.3 + Akka 2.3.2
Will continue to dig to see what's going on here.
On Monday, April 28, 2014 3:41:07 PM UTC+8, Raymond Tay wrote:
>
> Hi Akka users,
>
> I've got a situation that's perplexing. It began with Akka 2.3.2 and i
> have a Play 2.3
Hi Akka users,
I've got a situation that's perplexing. It began with Akka 2.3.2 and i have
a Play 2.3-M1 attempting to connect to a Akka 2.3.2 actor (part of a
cluster named TrailingHammer) and it's not able to do so by throwing an
error message like the following:
play.api.Application$$anon$1