Skip to content

Commit 955b042

Browse files
authored
Update service-bus-amqp-protocol-guide.md
1 parent 474d1f0 commit 955b042

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/service-bus-messaging/service-bus-amqp-protocol-guide.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -79,7 +79,7 @@ Azure Service Bus currently uses exactly one session for each connection. The Se
7979
Connections, channels, and sessions are ephemeral. If the underlying connection collapses, connections, TLS tunnel, SASL authorization context, and sessions must be reestablished.
8080

8181
### AMQP Outbound Port Requirements
82-
Clients using AMQP Connections over tcp requires port 5671 and 5672 to be opened in the local firewall. Along with these ports it might be necessary to open additional ports if the [EnableLinkRedirect](https://docs.microsoft.com/en-us/dotnet/api/microsoft.servicebus.messaging.amqp.amqptransportsettings.enablelinkredirect?view=azure-dotnet) feature is enabled. EnableLinkRedirect is a new messaging feature which helps to skip one hop while receiving messages thus helping to boost throughput. The client would start communicaiting directly with backend service over port range 104XX as seen below. A dotnet client would fail with socketexception (An attempt was made to access a socket in a way forbidden by its access permissions) if these ports are blocked by the firewall. This feature can be disabled by setting the connecting EnableAmqpLinkRedirect=false which would force the clients to communicate with remote service over port 5671.
82+
Clients using AMQP Connections over tcp requires port 5671 and 5672 to be opened in the local firewall. Along with these ports, it might be necessary to open additional ports if the [EnableLinkRedirect](https://docs.microsoft.com/en-us/dotnet/api/microsoft.servicebus.messaging.amqp.amqptransportsettings.enablelinkredirect?view=azure-dotnet) feature is enabled. EnableLinkRedirect is a new messaging feature which helps to skip one-hop while receiving messages thus helping to boost throughput. The client would start communicating directly with backend service over port range 104XX as seen below. A dotnet client would fail with socketexception (An attempt was made to access a socket in a way forbidden by its access permissions) if these ports are blocked by the firewall. This feature can be disabled by setting EnableAmqpLinkRedirect=false in the connectiong string, which would force the clients to communicate with remote service over port 5671.
8383

8484

8585
### Links

0 commit comments

Comments
 (0)