akka 2.3.4 clustering issue

Hi,

I am using akka 2.3.4 and play 2.3.1 (activator based). I am developing a ProductCluster based on akka distributed workers on the typesafe. When I start the master process, it automatically starts a cluster named sbt-web. I don't know why it is happening. I am not doing anything like that. This was not happening when I was using akka 2.2.3 and play 2.2.3. When I migrated to latest play and akka I am facing this weird issue.

Funny thing is that, sbt-web cluster picks the ip address and port from the akka configuration that I wanted to reserve for ProductCluster and hence ProductCluster can't start.

Any help on what is this sbt-web cluster - will be appreciated.

Thanks & Regards,
Rohit



[INFO] [07/25/2014 17:37:53.864] [main] [Remoting] Starting remoting                                                    
[INFO] [07/25/2014 17:37:54.057] [main] [Remoting] Remoting started; listening on addresses :[akka.tcp://sbt-web@172.16.144.66:48197]
[INFO] [07/25/2014 17:37:54.059] [main] [Remoting] Remoting now listens on addresses: [akka.tcp://sbt-web@172.16.144.66:48197]       
[INFO] [07/25/2014 17:37:54.094] [main] [Cluster(akka://sbt-web)] Cluster Node [akka.tcp://sbt-web@172.16.144.66:48197] - Starting up...
[WARN] [07/25/2014 17:37:54.095] [main] [Cluster(akka://sbt-web)] [akka.cluster.auto-down] setting is replaced by [akka.cluster.auto-down-unreachable-after]
[INFO] [07/25/2014 17:37:54.199] [main] [Cluster(akka://sbt-web)] Cluster Node [akka.tcp://sbt-web@172.16.144.66:48197] - Registered cluster JMX MBean [akka:type=Cluster]
[INFO] [07/25/2014 17:37:54.200] [main] [Cluster(akka://sbt-web)] Cluster Node [akka.tcp://sbt-web@172.16.144.66:48197] - Started up successfully                         
[INFO] [07/25/2014 17:37:54.210] [sbt-web-akka.actor.default-dispatcher-6] [Cluster(akka://sbt-web)] Cluster Node [akka.tcp://sbt-web@172.16.144.66:48197] - Metrics will be retreived from MBeans, and may be incorrect on some platforms. To increase metric accuracy add the 'sigar.jar' to the classpath and the appropriate platform-specific native libary to 'java.library.path'. Reason: java.lang.ClassNotFoundException: org.hyperic.sigar.Sigar                                                                                                                                                     
[INFO] [07/25/2014 17:37:54.219] [sbt-web-akka.actor.default-dispatcher-6] [Cluster(akka://sbt-web)] Cluster Node [akka.tcp://sbt-web@172.16.144.66:48197] - Metrics collection has started successfully                                                                                                                                                                                                  
[WARN] [07/25/2014 17:37:54.515] [sbt-web-akka.remote.default-remote-dispatcher-15] [akka.tcp://sbt-web@172.16.144.66:48197/system/endpointManager/reliableEndpointWriter-akka.tcp%3A%2F%2FProductCluster%40172.16.144.66%3A2551-0/endpointWriter] AssociationError [akka.tcp://sbt-web@172.16.144.66:48197] -> [akka.tcp://ProductCluster@172.16.144.66:2551]: Error [Invalid address: akka.tcp://ProductCluster@172.16.144.66:2551] [         
ConfigFactory is pretty awesome. You can avoid try-catchs most of the time

```scala
val config = ConfigFactory.load().withFallback(ConfigFactory.parse("""
sbt-web.akka {
  log-dead-letters = 0
  log-dead-letters-during-shutdown = off
}
""")).getConfig("sbt-web")