Mention Artery port 25520 in migration guide
This commit is contained in:
parent
df7e5578bb
commit
f2dd10ceb9
1 changed files with 10 additions and 2 deletions
|
|
@ -125,10 +125,18 @@ when migrating from classic remoting.
|
|||
|
||||
The protocol part in the Akka `Address`, for example `"akka.tcp://actorSystemName@10.0.0.1:2552/user/actorName"`
|
||||
has changed from `akka.tcp` to `akka`. If you have configured or hardcoded any such addresses you have to change
|
||||
them to `"akka://actorSystemName@10.0.0.1:2552/user/actorName"`. `akka` is used also when TLS is enabled.
|
||||
them to `"akka://actorSystemName@10.0.0.1:25520/user/actorName"`. `akka` is used also when TLS is enabled.
|
||||
One typical place where such address is used is in the `seed-nodes` configuration.
|
||||
|
||||
The configuration is different, so you might have to revisit any custom configuration. See the full
|
||||
The default port is 25520 instead of 2552 to avoid connections between Artery and classic remoting due to
|
||||
misconfiguration. You can run Artery on 2552 if you prefer that (e.g. existing firewall rules) and then you
|
||||
have to configure the port with:
|
||||
|
||||
```
|
||||
akka.remote.artery.canonical.port = 2552
|
||||
```
|
||||
|
||||
The configuration for Artery is different, so you might have to revisit any custom configuration. See the full
|
||||
@ref:[reference configuration for Artery](../general/configuration.md#config-akka-remote-artery) and
|
||||
@ref:[reference configuration for classic remoting](../general/configuration.md#config-akka-remote).
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue