Jeff Mesnil created ARTEMIS-836:
-----------------------------------
Summary: Server start log does not display the correct
configuration
Key: ARTEMIS-836
URL: https://issues.apache.org/jira/browse/ARTEMIS-836
Project: ActiveMQ Artemis
Issue Type: Improvement
Affects Versions: 1.4.0
Reporter: Jeff Mesnil
Priority: Minor
When Artemis is configured to use a data base store configuration, the log when
the server is started is misleading:
{noformat}
11:49:52,059 INFO [org.apache.activemq.artemis.core.server] (ServerService
Thread Pool -- 64) AMQ221000: live Message Broker is starting with
configuration Bro
ker Configuration
(clustered=false,journalDirectory=/Users/jmesnil/Developer/wildfly/dist/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/activemq/journal
,bindingsDirectory=/Users/jmesnil/Developer/wildfly/dist/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/activemq/bindings,largeMessagesDirectory=/Users/j
mesnil/Developer/wildfly/dist/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/activemq/largemessages,pagingDirectory=/Users/jmesnil/Developer/wildfly/dist
/target/wildfly-11.0.0.Alpha1-SNAPSHOT/standalone/data/activemq/paging)
{noformat}
None of these directories will actually be used by the server.
Instead it should display the datasource (or the JDBC connection URL) and the
name of the tables used to persist information.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
