Skip to content

Commit 6608b22

Browse files
BimsaraBodaragamaBimsaraBodaragama
committed
Chnage Heading Levels
1 parent 320e5d3 commit 6608b22

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

49 files changed

+98
-98
lines changed

‎en/identity-server/5.10.0/docs/setup/changing-to-ibm-db2.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -281,7 +281,7 @@ The elements in the above configuration are described below:
281281
| **rollbackOnReturn** | If ` defaultAutoCommit ` =false, then you can set ` rollbackOnReturn ` =true so that the pool can terminate the transaction by calling rollback on the connection as it is returned to the pool. The default value is false. |
282282

283283

284-
### Driver-Level Timeouts (Recommended for Production)
284+
## Driver-Level Timeouts (Recommended for Production)
285285

286286
If the database becomes unresponsive, WSO2 Identity Server threads can get stuck waiting for a JDBC connection. This happens because the Tomcat JDBC Pool can't abort connection creation by itself ([source](https://github.com/apache/tomcat/blob/9.0.82/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/ConnectionPool.java#L693-L702){: target="_blank"}).
287287
@@ -298,7 +298,7 @@ Also note the distinction:
298298
299299
> **Note:** The `PoolExhaustedException` warning log is logged only when `maxWait` expires ([source](https://github.com/apache/tomcat/blob/9.0.82/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/ConnectionPool.java#L739-L741){: target="_blank"}). It does **not** cover delays inside the driver’s connection or read operations. Driver-level timeouts are required to handle those cases.
300300
301-
#### Example: IBM DB2 database
301+
### Example: IBM DB2 database
302302
303303
```toml
304304
[database.identity_db]

‎en/identity-server/5.10.0/docs/setup/changing-to-mssql.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -269,7 +269,7 @@ The elements in the above configuration are described below:
269269
| **rollbackOnReturn** | If ` defaultAutoCommit ` =false, then you can set ` rollbackOnReturn ` =true so that the pool can terminate the transaction by calling rollback on the connection as it is returned to the pool. The default value is false. |
270270

271271

272-
### Driver-Level Timeouts (Recommended for Production)
272+
## Driver-Level Timeouts (Recommended for Production)
273273

274274
If the database becomes unresponsive, WSO2 Identity Server threads can get stuck waiting for a JDBC connection. This happens because the Tomcat JDBC Pool can't abort connection creation by itself ([source](https://github.com/apache/tomcat/blob/9.0.82/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/ConnectionPool.java#L693-L702){: target="_blank"}).
275275
@@ -286,7 +286,7 @@ Also note the distinction:
286286
287287
> **Note:** The `PoolExhaustedException` warning log is logged only when `maxWait` expires ([source](https://github.com/apache/tomcat/blob/9.0.82/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/ConnectionPool.java#L739-L741){: target="_blank"}). It does **not** cover delays inside the driver’s connection or read operations. Driver-level timeouts are required to handle those cases.
288288
289-
#### Example: MSSQL database
289+
### Example: MSSQL database
290290
291291
```toml
292292
[database.identity_db]

‎en/identity-server/5.10.0/docs/setup/changing-to-mysql.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -279,7 +279,7 @@ The elements in the above configuration are described below:
279279
| **rollbackOnReturn** | If ` defaultAutoCommit ` =false, then you can set ` rollbackOnReturn ` =true so that the pool can terminate the transaction by calling rollback on the connection as it is returned to the pool. The default value is false. |
280280

281281

282-
### Driver-Level Timeouts (Recommended for Production)
282+
## Driver-Level Timeouts (Recommended for Production)
283283

284284
If the database becomes unresponsive, WSO2 Identity Server threads can get stuck waiting for a JDBC connection. This happens because the Tomcat JDBC Pool can't abort connection creation by itself ([source](https://github.com/apache/tomcat/blob/9.0.82/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/ConnectionPool.java#L693-L702){: target="_blank"}).
285285
@@ -296,7 +296,7 @@ Also note the distinction:
296296
297297
> **Note:** The `PoolExhaustedException` warning log is logged only when `maxWait` expires ([source](https://github.com/apache/tomcat/blob/9.0.82/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/ConnectionPool.java#L739-L741){: target="_blank"}). It does **not** cover delays inside the driver’s connection or read operations. Driver-level timeouts are required to handle those cases.
298298
299-
#### Example: MySQL database
299+
### Example: MySQL database
300300
301301
```toml
302302
[database.identity_db]

‎en/identity-server/5.10.0/docs/setup/changing-to-oracle-rac.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -201,7 +201,7 @@ validate, it will be dropped from the pool, and another attempt will be made to
201201
Pool](http://tomcat.apache.org/tomcat-9.0-doc/jdbc-pool.html#Tomcat_JDBC_Enhanced_Attributes).
202202

203203

204-
### Driver-Level Timeouts (Recommended for Production)
204+
## Driver-Level Timeouts (Recommended for Production)
205205

206206
If the database becomes unresponsive, WSO2 Identity Server threads can get stuck waiting for a JDBC connection. This happens because the Tomcat JDBC Pool can't abort connection creation by itself ([source](https://github.com/apache/tomcat/blob/9.0.82/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/ConnectionPool.java#L693-L702){: target="_blank"}).
207207

@@ -218,7 +218,7 @@ Also note the distinction:
218218

219219
> **Note:** The `PoolExhaustedException` warning log is logged only when `maxWait` expires ([source](https://github.com/apache/tomcat/blob/9.0.82/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/ConnectionPool.java#L739-L741){: target="_blank"}). It does **not** cover delays inside the driver’s connection or read operations. Driver-level timeouts are required to handle those cases.
220220
221-
#### Example: Oracle RAC database
221+
### Example: Oracle RAC database
222222

223223
```toml
224224
[database.identity_db]

‎en/identity-server/5.10.0/docs/setup/changing-to-oracle.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -267,7 +267,7 @@ The elements in the above configuration are described below:
267267
| **rollbackOnReturn** | If ` defaultAutoCommit ` =false, then you can set ` rollbackOnReturn ` =true so that the pool can terminate the transaction by calling rollback on the connection as it is returned to the pool. The default value is false. |
268268

269269

270-
### Driver-Level Timeouts (Recommended for Production)
270+
## Driver-Level Timeouts (Recommended for Production)
271271

272272
If the database becomes unresponsive, WSO2 Identity Server threads can get stuck waiting for a JDBC connection. This happens because the Tomcat JDBC Pool can't abort connection creation by itself ([source](https://github.com/apache/tomcat/blob/9.0.82/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/ConnectionPool.java#L693-L702){: target="_blank"}).
273273
@@ -284,7 +284,7 @@ Also note the distinction:
284284
285285
> **Note:** The `PoolExhaustedException` warning log is logged only when `maxWait` expires ([source](https://github.com/apache/tomcat/blob/9.0.82/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/ConnectionPool.java#L739-L741){: target="_blank"}). It does **not** cover delays inside the driver’s connection or read operations. Driver-level timeouts are required to handle those cases.
286286
287-
#### Example: Oracle database
287+
### Example: Oracle database
288288
289289
```toml
290290
[database.identity_db]

‎en/identity-server/5.10.0/docs/setup/changing-to-postgresql.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -267,7 +267,7 @@ The elements in the above configuration are described below:
267267
| **rollbackOnReturn** | If ` defaultAutoCommit ` =false, then you can set ` rollbackOnReturn ` =true so that the pool can terminate the transaction by calling rollback on the connection as it is returned to the pool. The default value is false. |
268268

269269

270-
### Driver-Level Timeouts (Recommended for Production)
270+
## Driver-Level Timeouts (Recommended for Production)
271271

272272
If the database becomes unresponsive, WSO2 Identity Server threads can get stuck waiting for a JDBC connection. This happens because the Tomcat JDBC Pool can't abort connection creation by itself ([source](https://github.com/apache/tomcat/blob/9.0.82/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/ConnectionPool.java#L693-L702){: target="_blank"}).
273273
@@ -284,7 +284,7 @@ Also note the distinction:
284284
285285
> **Note:** The `PoolExhaustedException` warning log is logged only when `maxWait` expires ([source](https://github.com/apache/tomcat/blob/9.0.82/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/ConnectionPool.java#L739-L741){: target="_blank"}). It does **not** cover delays inside the driver’s connection or read operations. Driver-level timeouts are required to handle those cases.
286286
287-
#### Example: PostgreSQL database
287+
### Example: PostgreSQL database
288288
289289
```toml
290290
[database.identity_db]

‎en/identity-server/5.10.0/docs/setup/changing-to-remote-h2.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -286,7 +286,7 @@ The elements in the above configuration are described below:
286286
| **rollbackOnReturn** | If ` defaultAutoCommit ` =false, then you can set ` rollbackOnReturn ` =true so that the pool can terminate the transaction by calling rollback on the connection as it is returned to the pool. The default value is false. |
287287

288288

289-
### Driver-Level Timeouts (Recommended for Production)
289+
## Driver-Level Timeouts (Recommended for Production)
290290

291291
If the database becomes unresponsive, WSO2 Identity Server threads can get stuck waiting for a JDBC connection. This happens because the Tomcat JDBC Pool can't abort connection creation by itself ([source](https://github.com/apache/tomcat/blob/9.0.82/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/ConnectionPool.java#L693-L702){: target="_blank"}).
292292
@@ -303,7 +303,7 @@ Also note the distinction:
303303
304304
> **Note:** The `PoolExhaustedException` warning log is logged only when `maxWait` expires ([source](https://github.com/apache/tomcat/blob/9.0.82/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/ConnectionPool.java#L739-L741){: target="_blank"}). It does **not** cover delays inside the driver’s connection or read operations. Driver-level timeouts are required to handle those cases.
305305
306-
#### Example: Remote H2 database
306+
### Example: Remote H2 database
307307
308308
```toml
309309
[database.identity_db]

‎en/identity-server/5.11.0/docs/setup/changing-to-ibm-db2.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -280,7 +280,7 @@ The elements in the above configuration are described below:
280280
| |
281281
| **rollbackOnReturn** | If ` defaultAutoCommit ` =false, then you can set ` rollbackOnReturn ` =true so that the pool can terminate the transaction by calling rollback on the connection as it is returned to the pool. The default value is false. |
282282

283-
### Driver-Level Timeouts (Recommended for Production)
283+
## Driver-Level Timeouts (Recommended for Production)
284284

285285
If the database becomes unresponsive, WSO2 Identity Server threads can get stuck waiting for a JDBC connection. This happens because the Tomcat JDBC Pool can't abort connection creation by itself ([source](https://github.com/apache/tomcat/blob/9.0.82/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/ConnectionPool.java#L693-L702){: target="_blank"}).
286286

@@ -297,7 +297,7 @@ Also note the distinction:
297297

298298
> **Note:** The `PoolExhaustedException` warning log is logged only when `maxWait` expires ([source](https://github.com/apache/tomcat/blob/9.0.82/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/ConnectionPool.java#L739-L741){: target="_blank"}). It does **not** cover delays inside the driver’s connection or read operations. Driver-level timeouts are required to handle those cases.
299299

300-
#### Example: IBM DB2 database
300+
### Example: IBM DB2 database
301301

302302
```toml
303303
[database.identity_db]

‎en/identity-server/5.11.0/docs/setup/changing-to-mssql.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -268,7 +268,7 @@ The elements in the above configuration are described below:
268268
| **commitOnReturn** | If ` defaultAutoCommit ` =false, then you can set ` commitOnReturn ` =true, so that the pool can complete the transaction by calling the commit on the connection as it is returned to the pool. However, If ` rollbackOnReturn ` =true then this attribute is ignored. The default value is false. |
269269
| **rollbackOnReturn** | If ` defaultAutoCommit ` =false, then you can set ` rollbackOnReturn ` =true so that the pool can terminate the transaction by calling rollback on the connection as it is returned to the pool. The default value is false. |
270270

271-
### Driver-Level Timeouts (Recommended for Production)
271+
## Driver-Level Timeouts (Recommended for Production)
272272

273273
If the database becomes unresponsive, WSO2 Identity Server threads can get stuck waiting for a JDBC connection. This happens because the Tomcat JDBC Pool can't abort connection creation by itself ([source](https://github.com/apache/tomcat/blob/9.0.82/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/ConnectionPool.java#L693-L702){: target="_blank"}).
274274
@@ -285,7 +285,7 @@ Also note the distinction:
285285
286286
> **Note:** The `PoolExhaustedException` warning log is logged only when `maxWait` expires ([source](https://github.com/apache/tomcat/blob/9.0.82/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/ConnectionPool.java#L739-L741){: target="_blank"}). It does **not** cover delays inside the driver’s connection or read operations. Driver-level timeouts are required to handle those cases.
287287
288-
#### Example: MSSQL database
288+
### Example: MSSQL database
289289
290290
```toml
291291
[database.identity_db]

‎en/identity-server/5.11.0/docs/setup/changing-to-mysql.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -285,7 +285,7 @@ The elements in the above configuration are described below:
285285
| **commitOnReturn** | If ` defaultAutoCommit ` =false, then you can set ` commitOnReturn ` =true, so that the pool can complete the transaction by calling the commit on the connection as it is returned to the pool. However, If ` rollbackOnReturn ` =true then this attribute is ignored. The default value is false. |
286286
| **rollbackOnReturn** | If ` defaultAutoCommit ` =false, then you can set ` rollbackOnReturn ` =true so that the pool can terminate the transaction by calling rollback on the connection as it is returned to the pool. The default value is false. |
287287

288-
### Driver-Level Timeouts (Recommended for Production)
288+
## Driver-Level Timeouts (Recommended for Production)
289289

290290
If the database becomes unresponsive, WSO2 Identity Server threads can get stuck waiting for a JDBC connection. This happens because the Tomcat JDBC Pool can't abort connection creation by itself ([source](https://github.com/apache/tomcat/blob/9.0.82/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/ConnectionPool.java#L693-L702){: target="_blank"}).
291291
@@ -302,7 +302,7 @@ Also note the distinction:
302302
303303
> **Note:** The `PoolExhaustedException` warning log is logged only when `maxWait` expires ([source](https://github.com/apache/tomcat/blob/9.0.82/modules/jdbc-pool/src/main/java/org/apache/tomcat/jdbc/pool/ConnectionPool.java#L739-L741){: target="_blank"}). It does **not** cover delays inside the driver’s connection or read operations. Driver-level timeouts are required to handle those cases.
304304
305-
#### Example: MySQL database
305+
### Example: MySQL database
306306
307307
```toml
308308
[database.identity_db]

0 commit comments

Comments
 (0)