Update jdbc-v2.md

Author: Paultagoras

docs/en/integrations/language-clients/java/jdbc-v2.md

@@ -181,7 +181,56 @@ try (HikariDataSource ds = new HikariDataSource(poolConfig);
 }
 ```
 
-
 ## More Information
 For more information, see our [GitHub repository](https://github.com/ClickHouse/clickhouse-java) and [Client-V2 documentation](/docs/en/integrations/language-clients/java/client-v2.md).
+
+
+## Troubleshooting
+### Logging
+The driver uses [slf4j](https://www.slf4j.org/) for logging, and will use the first available implementation on the classpath.
+
+### Resolving JDBC Timeout on Large Inserts
+
+When performing large inserts in ClickHouse with long execution times, you may encounter JDBC timeout errors like:
+
+```plaintext
+Caused by: java.sql.SQLException: Read timed out, server myHostname [uri=https://hostname.aws.clickhouse.cloud:8443]
+```
+These errors can disrupt the data insertion process and affect system stability. To address this issue you may need to adjust a few timeout settings in the client's OS.
+
+#### Mac OS
+
+On Mac OS, the following settings can be adjusted to resolve the issue:
+
+- `net.inet.tcp.keepidle`: 60000
+- `net.inet.tcp.keepintvl`: 45000
+- `net.inet.tcp.keepinit`: 45000
+- `net.inet.tcp.keepcnt`: 8
+- `net.inet.tcp.always_keepalive`: 1
+
+#### Linux
+
+On Linux, the equivalent settings alone may not resolve the issue. Additional steps are required due to the differences in how Linux handles socket keep-alive settings. Follow these steps:
+
+1. Adjust the following Linux kernel parameters in `/etc/sysctl.conf` or a related configuration file:
+
+    - `net.inet.tcp.keepidle`: 60000
+    - `net.inet.tcp.keepintvl`: 45000
+    - `net.inet.tcp.keepinit`: 45000
+    - `net.inet.tcp.keepcnt`: 8
+    - `net.inet.tcp.always_keepalive`: 1
+    - `net.ipv4.tcp_keepalive_intvl`: 75
+    - `net.ipv4.tcp_keepalive_probes`: 9
+    - `net.ipv4.tcp_keepalive_time`: 60 (You may consider lowering this value from the default 300 seconds)
+
+2. After modifying the kernel parameters, apply the changes by running the following command:
+
+   ```shell
+   sudo sysctl -p
+   ```
+
+After Setting those settings, you need to ensure that your client enables the Keep Alive option on the socket:
+
+```java
+properties.setProperty("socket_keepalive", "true");
 ```