[ https://issues.apache.org/jira/browse/ARTEMIS-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16442536#comment-16442536 ]
ASF subversion and git services commented on ARTEMIS-1653: ---------------------------------------------------------- Commit 0da630be500ff90db091f2014cba7e3ac97db38d in activemq-artemis's branch refs/heads/1.x from [~nigro....@gmail.com] [ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=0da630b ] ARTEMIS-1653 Allow database tables to be created externally (cherry picked from commit c7651853cdb291dfa3bd2906e1e082fd06cff612) > Allow database tables to be created externally > ---------------------------------------------- > > Key: ARTEMIS-1653 > URL: https://issues.apache.org/jira/browse/ARTEMIS-1653 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Broker > Affects Versions: 2.4.0 > Reporter: Niels Lippke > Assignee: Francesco Nigro > Priority: Major > Fix For: 2.5.1 > > > In some environments (e.g. production) it is not allowed that applications > create their own schema. It's common practice to pass DDL-Statetements to > DBAs instead prior to rollout. > Currently the broker does not support this scenario. If the required tables > already exist the broker fails to start. > A better approach is that if the broker detects empy tables and initializes > them in the very same way it does if the tables dont't exist. > See also discussion in > [forum|http://activemq.2283324.n4.nabble.com/ARTEMIS-Server-doesn-t-start-if-JDBC-store-is-used-and-table-NODE-MANAGER-STORE-is-empty-td4735779.html]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)