Contrary to 5.0, invalid timezones received from the server will
result in the transaction being retried and cause the connection
to eventually put back to pool, after all attempts are
exhausted.
While this is not ideal, this has been done so to minimize
breaking changes in 4.x.
Contrary to 5.0, invalid timezones received from the server will result in the transaction being retried and cause the connection to eventually put back to pool, after all attempts are exhausted.
While this is not ideal, this has been done so to minimize breaking changes in 4.x.