sabbyanandan
commented
5 years ago @tzolov: Perhaps you could add the link to the demo app, and that would help @shakuzen to get this going, to help reproduce the problem locally.
cc:/ @mminella
Open tzolov opened 5 years ago
sabbyanandan
commented
5 years ago @tzolov: Perhaps you could add the link to the demo app, and that would help @shakuzen to get this going, to help reproduce the problem locally.
cc:/ @mminella
shakuzen
commented
5 years ago Thanks for the report @tzolov. A demo app so I can reproduce this would be helpful. I think I didn't see this with the demo app I was using before. When is the error happening? Soon after the client connects? When a scrape from Prometheus happens? We might need help from the reactor-netty team as the stacktrace seems to be all netty/reactor-netty code.
tzolov
commented
5 years ago @sabbyanandan , @shakuzen , @mminella, here is the demo app to reproduce the issue: https://github.com/tzolov/prometheus-rsocket-demo and here is how i create the environment: https://github.com/tzolov/prometheus-rsocket-demo/blob/master/README.md
shakuzen
commented
5 years ago Unfortunately, I was not able to reproduce the reported error on my machine following the instructions. I sent a pull request to the repo that updates a few things to make sure the latest code is used and minimizes potential sources of differences. In addition to running the demo (client) app once, I ran it in a loop for about 10-15 runs.
Trying a demo Spring Boot app with the latest (0.8.0-SNAPSHOT) rsocket client and proxy but getting rsocket exceptions on the proxy side.
My proxy runs locally and the Boot application uses properties like this:
When i run the demo i can see that the
prometheus_proxy_scrape_active_connectionsmetrics is increased from 0 to 1 suggesting that the demo connects to the proxy. But then i get this exception in the proxy log: