| TestConductorStartController Method |
Start the
Controller, which in turn will
bind to a TCP port as specified in the `akka.testconductor.port` config
property, where 0 denotes automatic allocation. Since the latter is
actually preferred, a `Future[Int]` is returned which will be completed
with the port number actually chosen, so that this can then be communicated
to the players for their proper start-up.
This method also invokes Player.startClient,
since it is expected that the conductor participates in barriers for
overall coordination. The returned Future will only be completed once the
client’s start-up finishes, which in fact waits for all other players to
connect.
Namespace:
Akka.Remote.TestKit
Assembly:
Akka.Remote.TestKit (in Akka.Remote.TestKit.dll) Version: 1.2.3.42 (1.2.3.42)
Syntax public Task<IPEndPoint> StartController(
int participants,
RoleName name,
IPEndPoint controllerPort
)
member StartController :
participants : int *
name : RoleName *
controllerPort : IPEndPoint -> Task<IPEndPoint>
Parameters
- participants
- Type: SystemInt32
participants gives the number of participants which shall connect
before any of their startClient() operations complete
- name
- Type: Akka.Remote.TestKitRoleName
- controllerPort
- Type: System.NetIPEndPoint
Return Value
Type:
TaskIPEndPoint[Missing <returns> documentation for "M:Akka.Remote.TestKit.TestConductor.StartController(System.Int32,Akka.Remote.TestKit.RoleName,System.Net.IPEndPoint)"]
See Also