You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment KalturaClientBase loses the information about the original (occurred) network errors because it catches them and throws KalturaApiException instead, without setting the original exception to the cause of the thrown exception.
Could it be possible to separate network errors from "normal" API errors? We'd like to handle networking errors with a different way (retry after a certain period of time) than other API errors.
The text was updated successfully, but these errors were encountered:
Thank for you reporting an issue and helping improve Kaltura!
To get the fastest response time, and help the maintainers review and test your reported issues or suggestions, please ensure that your issue includes the following (please comment with more info if you have not included all this info in your original issue):
Is the issue you're experiencing consistent and across platforms? or does it only happens on certain conditions?
please provide as much details as possible.
Which Kaltura deployment you're using: Kaltura SaaS, or self-hosted?
If self hosted, are you using the RPM or deb install?
Packages installed.
When using RPM, paste the output for:
# rpm -qa "kaltura*"
For deb based systems:
# dpkg -l "kaltura-*"
If running a self hosted ENV - provide the MySQL server version used
If running a self hosted ENV - is this a single all in 1 server or a cluster?
If running a self hosted ENV, while making the problematic request, run:
At the moment
KalturaClientBase
loses the information about the original (occurred) network errors because it catches them and throwsKalturaApiException
instead, without setting the original exception to the cause of the thrown exception.Could it be possible to separate network errors from "normal" API errors? We'd like to handle networking errors with a different way (retry after a certain period of time) than other API errors.
The text was updated successfully, but these errors were encountered: