To verify that it is running with the right configuration you can try
setting this config property:
akka.log-config-on-start = on
http://doc.akka.io/docs/akka/2.3.9/scala/logging.html#Auxiliary_logging_options
/Patrik
On Fri, Apr 10, 2015 at 5:59 AM, Stefan Schmidt wrote:
> Hi Jim,
>
> I am al
Another thing that sometimes bites me on remote hosts that I'm not used to
is a local software firewall. Make sure the host itself isn't dropping
traffic back to your listening ports.
--
>> Read the docs: http://akka.io/docs/
>> Check the FAQ:
>> http://doc.a
Try setting JVM system params. For example, an early demo that I hacked up
looked like this. It isn't on EC2, but I don't think that EC2 is really
your problem. Hack out the stuff you don't care about and omit the -J if
not using sbt.
Instance 1:
sbt -J-Dakka.remote.netty.tcp.hostname=lo
Hi Jim,
Thanks for your reply.
Unfortunately the netty settings make no difference. I have set them to the
same parameters as the initial akka cluster address but still see the
issue. In fact the netty host address/port/sibling addresses are set
dynamically when akka is started first (as desc
