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
Problem using ably-java with newrelic #258
Comments
What's the status of this? |
At the time we investigated this, the only known workaround was to disable newrelic; see |
@thoersch what version of NewRelic are you using when you see this issue? |
We're not -- we're a prospect client only at this point and wanted to ensure this was not an issue anymore before proceeding further. We do use NR so it's important that it's not an issue anymore. We're also not the reporter of the issue so unsure what version they had. We're using 3.44.1 though, if that helps. |
@thoersch given this has not been reported since Dec 2016, I very much doubt this is still an issue with NewRelic. However, if you do encounter this issue, we will have to dive deeper and resolve the issue. I am very confident that if the issue still exists, a workaround could be found, even if that requires us discussing the issue with NewRelic and/or forking their library and seeing if we can get a fix merged in upstream. |
I would recommend testing it in your environment either way to see if the issue is present or not. Given this was reported and not reproduced at the time, we have no way of knowing if this issue was necessarily caused solely by NewRelic. |
I've tested against a recent version of NewRelic on Android, and both websocket connections and HTTP requests seem to work without any issues. I set up the NewRelic integration with:
in
in the app dependencies. In my code I was setting up NewRelic with every option that could give rise to interference with the Ably library:
This was with ably-java for Android v 1.0.7. |
@thoersch I'm not seeing that version in https://docs.newrelic.com/docs/release-notes/mobile-release-notes/android-release-notes |
I'm closing this - as far as we know, there aren't any issues now with new relic. |
Customer reported a
io.ably.lib.types.AblyException: java.io.IOException: readBufferBytes failed
exception callingably.channels.get(channelId).history(null).items();
(with ably-java 0.8.8). Stacktrace:They report that on disabling newrelic, the problem disappears. They're using a newrelic version of "5.+" (?).
We should try and reproduce this, and figure out what's causing the bad interaction between ably-java and newrelic.
The text was updated successfully, but these errors were encountered: