Some api endpoints stop responding after a while
See original GitHub issueAfter updating to the latest dataflow and skipper version, the left panel of dataflow stopped working, the about call returned 404 error, this was described in: https://github.com/spring-cloud/spring-cloud-dataflow/issues/3924
After debugging the issue a little bit I saw that the pod with skipper running did indeed returned 404 after some time running.
This is the response when invoking Skipper api with curl after it gets in a wrong state:
curl -i http://skipper.somenamespace.svc.cluster.local/api
{
"_links" : {
"about" : {
"href" : "http://skipper.somenamespace.svc.cluster.local/api/about"
},
"release" : {
"href" : "http://skipper.somenamespace.svc.cluster.local/api/release"
},
"package" : {
"href" : "http://skipper.somenamespace.svc.cluster.local/api/package"
},
"profile" : {
"href" : "http://skipper.somenamespace.svc.cluster.local/api/profile"
}
}
}
If I restart the skipper pod the response becomes:
{
"_links" : {
"deployers" : {
"href" : "http://skipper.somenamespace.svc.cluster.local/api/deployers{?page,size,sort}",
"templated" : true
},
"repositories" : {
"href" : "http://skipper.somenamespace.svc.cluster.local/api/repositories{?page,size,sort}",
"templated" : true
},
"packageMetadata" : {
"href" : "http://skipper.somenamespace.svc.cluster.local/api/packageMetadata{?page,size,sort,projection}",
"templated" : true
},
"releases" : {
"href" : "http://skipper.somenamespace.svc.cluster.local/api/releases{?page,size,sort}",
"templated" : true
},
"about" : {
"href" : "http://skipper.somenamespace.svc.cluster.local/api/about"
},
"release" : {
"href" : "http://skipper.somenamespace.svc.cluster.local/api/release"
},
"package" : {
"href" : "http://skipper.somenamespace.svc.cluster.local/api/package"
},
"profile" : {
"href" : "http://skipper.somenamespace.svc.cluster.local/api/profile"
}
}
}
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (8 by maintainers)
Top Results From Across the Web
HTTP API stops responding while writing file - Stack Overflow
I have written an API http server in Go using Gorilla Mux. It works well. One of the endpoints is for uploading files...
Read more >Web API endpoints stops responding when a file upload is ...
Hi,. I am facing the following issue. I have implemented a application with Web Api 2. One of the endpoints accepts multipart which...
Read more >How do you know what's gone wrong when your API request ...
When an API request doesn't work, hopefully the client receives a sensible HTTP error status, like 409 or 500, which is a good...
Read more >Best Practices for REST API Error Handling - Baeldung
The simplest way we handle errors is to respond with an appropriate status code. Here are some common response codes: ... While basic,...
Read more >Resolve connection issues with API Gateway private API ...
If the API request doesn't produce any CloudWatch logs after logging is activated, then the request didn't reach the endpoint. If your API...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Most likely this issue is caused by https://jira.spring.io/browse/DATAREST-1502. It’s kinda hit and miss to reproduce as it’s jvm evicting references.
We’ll get needed fixes when we do a new release with Spring Boot 2.2.7. We’ll probably release latest on Monday.
@rstpv: Thank you for testing it and the confirmation. Appreciate it.