We’re experiencing the issue again today.
Yes, the DB does have a firewall in between. Documentation seems to indicate there is a default timeout value of 4 minutes on the firewall, but the connections from SonarQube remain viable much longer than that. If that’s the case, I would expect an application to be able to recover from this type of situation without intervention.
It’s possible that the ticket you linked is related, but the problem described on it is very generic. Also it’s marked as resolved in SonarQube 9.8 which we are on.
The db is in the same Azure region and VNet, but on separate subnets (I believe).