Azure-Samples / Azure-Samples/storage-blobs-java-quickstart
Error while running the application
- Dominant language
- Java
- Stars
- 16
- Forks
- 32
- PR merge metrics
- No merged PRs in 30d
Description
> Please provide us with the following information:
> ---------------------------------------------------------------
### This issue is for a: (mark with an `x`)
```
- [X] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)
```
### Minimal steps to reproduce
> Changed the code to have my Azure blo account and key
### Any log messages given by the failure
>
Azure Blob storage quick start sample
Creating container: asit
Error returned from the service. Http code: 500 and error code: SERVICE_INTERNAL_ERROR
The program has completed successfully.
Press the 'Enter' key while in the console to delete the sample files, example container, and exit the application.
Deleting the container
Service error. Http code: 500 and error code: SERVICE_INTERNAL_ERROR
Deleting the source, and downloaded files
### Expected/desired behavior
>
The application should have executed successfully.
### OS and Version?
> Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)
Windows 10
### Versions
>
### Mention any other details that might be useful
> ---------------------------------------------------------------
> Thanks! We'll be in touch soon.
Contributor guide
Research direction
Start by running the Azure Blob storage quick start sample with the reported Azure Blob account and key, then compare the container creation and deletion responses with the logged HTTP 500 SERVICE_INTERNAL_ERROR results. Done would require identifying a reproducible application or service failure and documenting a specific change or configuration fix; the issue does not name a source file or test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, java
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100