[
https://issues.apache.org/jira/browse/ARTEMIS-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16541638#comment-16541638
]
ASF subversion and git services commented on ARTEMIS-1979:
----------------------------------------------------------
Commit 79ff3432d599ec4cd10f6613bdb2beb428aac960 in activemq-artemis's branch
refs/heads/master from [~nigro....@gmail.com]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=79ff343 ]
ARTEMIS-1979 Table names with DB2 should be upper-cases
DB2 JDBC driver fail to retrieve metadata information
if table names are lower-cases: similarly to Oracle, better
force any table name to be upper-cases to avoid broker being
unable to restart when lower-cases table names are used
> 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)
