[jira] [Comment Edited] (AMQ-6317) ActiveMQ createSchemaStatements are not executed on init if a previous createSchemaStatement failed on execution

["Gary Tully (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMQ-6317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15324130#comment-15324130 ] 

Gary Tully edited comment on AMQ-6317 at 6/10/16 9:23 AM:
----------------------------------------------------------

darn, that  util should be back in the broker module, like socketProxy etc.
I did an update to move that so that you can pull in the broker test-jar dependency: <artifactId>activemq-broker</artifactId><type>test-jar</type> into jdbc.

https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=f548aafa81fdb53b5c273bd15705a3d0fe2ef0e2


was (Author: gtully):
darn, that  util should be back in the broker module, like socketProxy etc.
I did an update to move that so that you can pull in the broker test-jar dependency: <artifactId>activemq-broker</artifactId><type>test-jar</type> into jdbc.

> ActiveMQ createSchemaStatements are not executed on init if a previous createSchemaStatement failed on execution
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-6317
>                 URL: https://issues.apache.org/jira/browse/AMQ-6317
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions: 5.12.3, 5.13.3
>         Environment: PostgreSql, Linux, Mac OS X
>            Reporter: Jeroen Bastijns
>
> On init the DefaultJDBCAdapter.doCreateTables-method is executed. This provides the tables needed for ActiveMQ in persistent mode.
> The createSchemaStatements are executed within one SQL Statement. 
> When one of the createSchemaStatements throws an SQLException (table already exists) the SQL Statement's transaction is aborted and all following createSchemaStatements are ignored.
> This is unwanted behaviour as the comment on the code block states that new statements like for example 'ALTER TABLE' (introduced in new versions of activemq) should be executed if the tables already exist.
> We had this issue when adding an extra createSchemaStatement for a JobScheduler table.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)