My Java Spring web service on Azure and its MySQL database exhibit over 100 SQL connections, all tied to two outbound IP addresses. Why does this happen?
hey, im guessin its a connction pool misconfigurashun in spring settings causing extra sql sessions. azure’s fixed ip load may be working against you. have you tried fiddlin with pool sizes to see any changes? whats yer experince so far?
maybe its not the pool setup but azure holding open idle connecitons longer than expected. check your idle timeout settings and see if that trims excess sql connections. also verify if any other configurations could be influencing this behaviour
hey, i wonder if azure sometimes recreates connections to keep performance stable? could your timeouts or keepalive settings be a bit off? what do you think might be triggering those extra connections? would love to hear your experimnts.
In a similar situation, I discovered that the excessive number of SQL connections was partly due to how my connection pool was configured in the Java Spring application as well as Azure’s networking behavior. Adjusting the pool size to better match the demand and setting a proper timeout for idle connections helped prevent the accumulation of unused connections. Additionally, using detailed logging was instrumental in tracking how connections were managed. These changes resulted in improved resource utilization and more consistent behavior across the Azure environment.