After restarting Endevor Bridge for Git STC, the log shows:
liquibase - Exception during pool initialization.
Caused by: java.sql.SQLTimeoutException: Login timeout exceeded.
at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown Source)
at org.apache.derby.jdbc.InternalDriver.timeLogin(Unknown Source)
at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source)
at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source)
at org.apache.derby.jdbc.EmbeddedDriver.connect(Unknown Source)
at com.zaxxer.hikari.util.DriverDataSource.getConnection(DriverDataSource.java:138)
at com.zaxxer.hikari.pool.PoolBase.newConnection(PoolBase.java:364)
at com.zaxxer.hikari.pool.PoolBase.newPoolEntry(PoolBase.java:206)
at com.zaxxer.hikari.pool.HikariPool.createPoolEntry(HikariPool.java:476)
at com.zaxxer.hikari.pool.HikariPool.checkFailFast(HikariPool.java:561)
... 137 common frames omitted
Caused by: org.apache.derby.iapi.error.StandardException: Login timeout exceeded.
B4G 2.15.1
If B4G server is installed on a Mainframe system with limited resources, or a system is already experiencing high CPU usage when B4G starts, increase the database connection timeout setting (this is an internal setting with default value set to 15 seconds) in application.yml, then restart B4G server.
spring:
# database connection timeout
datasource:
default:
hikari:
connection-timeout: 30000
liquibase:
hikari:
connection-timeout: 30000
migrate:
hikari:
connection-timeout: 30000