Skip to content

Commit 16d1c89

Browse files
authored
Fixes
1 parent f3d7ea7 commit 16d1c89

File tree

1 file changed

+5
-8
lines changed

1 file changed

+5
-8
lines changed

articles/cosmos-db/sql/troubleshoot-service-unavailable-java-sdk-v4-sql.md

Lines changed: 5 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,11 @@ The Java v4 SDK wasn't able to connect to Azure Cosmos DB.
1818
The following list contains known causes and solutions for service unavailable exceptions.
1919

2020
### The required ports are being blocked
21-
Verify that all the [required ports](sql-sdk-connection-modes.md#service-port-ranges) are enabled.
21+
Verify that all the [required ports](sql-sdk-connection-modes.md#service-port-ranges) are enabled. If the account is configured with private endpoint then additional ports are required to be opened.
22+
23+
```
24+
failed to establish connection to {account name}.documents.azure.com/<unresolved>:3044 due to io.netty.channel.ConnectTimeoutException:
25+
```
2226

2327
### Client initialization failure
2428
The following exception is hit if the SDK is not able to talk to the Cosmos DB instance. This normally points to some security protocol like a firewall rule is blocking the requests.
@@ -44,13 +48,6 @@ Follow the [request timeout troubleshooting steps](troubleshoot-request-timeout-
4448
#### UnknownHostException
4549
UnknownHostException means that the Java framework cannot resolve the DNS entry for the Cosmos DB endpoint in the affected machine. You should verify that the machine can resolve the DNS entry or if you have any custom DNS resolution software (such as VPN or Proxy, or a custom solution), make sure it contains the right configuration for the DNS endpoint that the error is claiming cannot be resolved. If the error is constant, you can verify the machine's DNS resolution through a `curl` command to the endpoint described in the error.
4650
47-
### Ports are blocked
48-
When in Direct mode the full list of ports is required to be open. Not opening all the ports can cause direct calls to fail with the following error, but calls to gateway can succeed. To fix the issue open all the [required ports](sql-sdk-connection-modes.md#service-port-ranges). If the account is configured with private endpoint then additional ports are required to be opened.
49-
50-
```
51-
failed to establish connection to {account name}.documents.azure.com/<unresolved>:3044 due to io.netty.channel.ConnectTimeoutException:
52-
```
53-
5451
### Service outage
5552
Check the [Azure status](https://status.azure.com/status) to see if there's an ongoing issue.
5653

0 commit comments

Comments
 (0)