Well that was a little harsh.
OP (and others): I've definitely run in to what I can only call "weirdness"
when trying to rely too heavily on Play's internal actor system for my own
purposes. I've found it's much more reliable to create my own (I use a
plugin for this).
On Tuesday, February
Same issue with Play 2.3.6 and Akka 2.3.6, spent a day trying all kinds of
workarounds and nothing worked.
Proof that technologies like these will take time to become reliable for
companies. A day lost looking for hopeless solutions to problems like these
is too much for young startups, and thi
Hi guys,
sorry we didn't reply in this thread (seems we missed it somehow).
In general the code as shown should be working fine in any Akka version...
Raymond's hint that using a "plain actor system" works may hint at some
configuration differences with respect to "play's actor system", hm.
Could
Hey, I'm also having this issue... Any new updates? :)
--
>> 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
Last update:
Workaround is to change the client code on the Play 2.3-M1 side to look
like :
object Application extends Controller {
val as = ActorSystem("TrailingHammer", ConfigFactory.load("TrailingHammer"))
val backend = as.actorSelection(RootActorPath(backendAddress) / "user" /
"Shad
Quick update:
another test i ran this time round is that the cluster application is left
running (i.e. Play 2.3 + Akka 2.3.2) and i had a client connect to the
clustered application using Play 2.2 + Akka 2.2.3 and this time round i am
able to connect to the router and send messages to the envi
