[ https://issues.apache.org/jira/browse/ARTEMIS-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16442535#comment-16442535 ]
ASF subversion and git services commented on ARTEMIS-1653: ---------------------------------------------------------- Commit af15fc43c663977be3cf2f82865936e3f5d02cda in activemq-artemis's branch refs/heads/1.x from [~nlippke] [ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=af15fc4 ] ARTEMIS-1653 Allow database tables to be created externally (cherry picked from commit eab498456762c3df0f786b1f9ae4e372fdbbfa32) > 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)