-
Bug
-
Resolution: Done
-
Minor
-
AMQ 7.8.0.GA
-
False
-
False
-
-
?
-
Undefined
-
Verified in a release
-
When starting the broker with the new JDBC connection pooling feature, we have an incorrect configuration log (2021-01-29 19:34:59,254):
2021-01-29 19:34:58,057 INFO [org.apache.activemq.artemis.jdbc.store.drivers.JDBCDataSourceUtils] Initialising JDBC data source: org.apache.commons.dbcp2.BasicDataSource {password=ACTIVE_MQ, maxTotal=-1, driverClassName=oracle.jdbc.driver.OracleDriver, poolPreparedStatements=true, url=jdbc:oracle:thin:@(DESCRIPTION_LIST=(LOAD_BALANCE=off)(FAILOVER=on)(DESCRIPTION=(ENABLE=BROKEN)(CONNECT_TIMEOUT=3)(RETRY_COUNT=3)(ADDRESS_LIST=(LOAD_BALANCE=on)(ADDRESS=(PROTOCOL=TCP)(HOST=soadlx13-vscan01.utenze.bankit.it)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=AMQDMSTA1S)))(DESCRIPTION=(ENABLE=BROKEN)(CONNECT_TIMEOUT=3)(RETRY_COUNT=3)(ADDRESS_LIST=(LOAD_BALANCE=on)(ADDRESS=(PROTOCOL=TCP)(HOST=soadlx21-vscan01.utenze.bankit.it)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=AMQDMSTA1S)))), username=ACTIVE_MQ} 2021-01-29 19:34:59,254 INFO [org.apache.activemq.artemis.core.server] AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=true,jdbcDriverClassName=org.apache.derby.jdbc.EmbeddedDriver,jdbcConnectionUrl=null,messageTableName=MESSAGES,bindingsTableName=BINDINGS,largeMessageTableName=LARGE_MESSAGES,pageStoreTableName=PAGE_STORE,)
- clones
-
ENTMQBR-4609 JDBC connection pooling log
- Closed