microsoft / microsoft/azure-tools-for-java
[IntelliJ][ReportedByUser] Uncaught Exception ***
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 262
- Forks
- 185
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 1
Description
[IntelliJ][ReportedByUser] Uncaught Exception *** exception class was changed or removed startRefreshLocationTimerAsync() - Unable to refresh database account from any location. Exception: {"ClassName":"CosmosException","userAgent":"azsdk-java-cosmos/4.38.0 Windows11/10.0 JRE/17.0.6","statusCode":403,"resourceAddress":"https://ct-n-zeaus-loy-mb-dev-acdb-eastus.documents.azure.com:443/","error":"{\"code\":\"Forbidden\",\"message\":\"Request originated from IP 108.196.239.63 through public internet. This is blocked by your Cosmos DB account firewall settings. More info: https://aka.ms/cosmosdb-tsg-forbidden\\r\\nActivityId: 79530eb6-4c73-4db7-a649-155d9ac85e46, Microsoft.Azure.Documents.Common/2.14.0, StatusCode: Forbidden","additionalErrorInfo":null}","innerErrorMessage":"Request originated from IP 108.196.239.63 through public internet. This is blocked by your Cosmos DB account firewall settings. More info: https://aka.ms/cosmosdb-tsg-forbidden\r\nActivityId: 79530eb6-4c73-4db7-a649-155d9ac85e46, Microsoft.Azure.Documents.Common/2.14.0, StatusCode: Forbidden","causeInfo":null,"responseHeaders":"{Transfer-Encoding=chunked, Strict-Transport-Security=max-age=31536000, Server=Microsoft-HTTPAPI/2.0, Content-Location=https://ct-n-zeaus-loy-mb-dev-acdb-eastus.documents.azure.com/, x-ms-gatewa
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at startRefreshLocationTimerAsync() and inspect how the IntelliJ tooling handles the reported CosmosException. The report shows a 403 caused by an Azure Cosmos DB firewall restriction, but it does not identify a source file, test, or expected behavior. Determine the intended handling and add coverage for the resolved behavior if the relevant test location can be found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, java
- Domain
- cloud, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100