You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "clebert suconic (JIRA)" <ji...@apache.org> on 2019/03/14 18:30:08 UTC

[jira] [Closed] (ARTEMIS-1979) Table names with DB2 should be upper-cases

     [ https://issues.apache.org/jira/browse/ARTEMIS-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

clebert suconic closed ARTEMIS-1979.
------------------------------------

> Table names with DB2 should be upper-cases
> ------------------------------------------
>
>                 Key: ARTEMIS-1979
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1979
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 2.6.2
>            Reporter: Francesco Nigro
>            Assignee: Francesco Nigro
>            Priority: Minor
>             Fix For: 2.7.0
>
>
> This issue is happening on Wildfly, but it affects Artemis as well.
> To reproduce it:
>  * Configure Artemis in Wildfly to use DB2 JDBC persistence store.
>  * Redefine name of a database table and use lower case letters.
>  * Restart Wildfly
> After the restart of Wildfly, boot of Artemis component fails. It seems that if table name is in lower case, Artemis is not able to detect that the particular table exists and tries to recreate it. The create operation fails and thus initialization of JDBC driver fails as well.
> The same scenario works with Oracle 12c database: the broker is turning Oracle table names to upper cases thanks to table-names-case property on journal-sql.properties configuration file.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)