-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to release a message: PooledSlicedByteBuf
Proxy Exception
#14
Comments
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? |
@sabbyanandan , @shakuzen , @mminella, here is the demo app to reproduce the issue: https://github.com/tzolov/prometheus-rsocket-demo |
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_connections
metrics is increased from 0 to 1 suggesting that the demo connects to the proxy. But then i get this exception in the proxy log:The text was updated successfully, but these errors were encountered: