oracle jdbc thin client login hangs no error

The following table lists various transient errors that applications can receive when connecting to Azure SQL Database. However, these events can occasionally take longer to finish, such as when a large transaction causes a long-running recovery. Most reconfiguration events are generally short-lived and should be completed in less than 60 seconds at most. Database reconfiguration events occur because of a planned event (for example, a software upgrade) or an unplanned event (for example, a process crash, or load balancing). This kind of error condition is called a transient fault. This dynamic behavior might cause your client program to lose its connection to the database or instance. The Azure infrastructure has the ability to dynamically reconfigure servers when heavy workloads arise in the SQL Database service. Transient fault error messages (40197, 40613 and others)

You can use Azure SQL Connectivity Checker to detect and fix a wide variety of connectivity errors to Azure SQL Database, Azure SQL Managed Instance and in Azure Synapse Analytics environments.

Oracle jdbc thin client login hangs no error