[jboss-jira] [JBoss JIRA] Created: (JBAS-4257) Jboss fails to start with MySQL due to case sensitive issue

[Benoit Xhenseval (JIRA)]

Jboss fails to start with MySQL due to case sensitive issue
-----------------------------------------------------------

                 Key: JBAS-4257
                 URL: http://jira.jboss.com/jira/browse/JBAS-4257
             Project: JBoss Application Server
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: Scheduling/Timers
    Affects Versions: JBossAS-4.0.5.GA
         Environment: Difference between Windows and Unix based.
            Reporter: Benoit Xhenseval
         Assigned To: Dimitris Andreadis


Hi,

Here is a case whereby the HARDCODED table name in org.jboss.ejb.txttimer GeneralPurposeDatabasePersistencePlugin is causing a problem.

Facts:
---------
1) MySQL is case SENSITIVE for database and table names under any OS, except Windows!
2) Since MySQL 4.0, all tables are created in lowercase regardless of the script
3) GeneralPurposeDatabasePersistencePlugin hardcodes the table TIMERS to be upper case.

Environment:
--------------------
1) Development happens under windows, hence all tables are in lower case 'timers'
2) Deployment will be on UNIX
3) the deployment database is created from a MySQL BACKUP of a development/test environment which is under Windows.
4) For extra security, Jboss will run with a datasource that CANNOT create a table

Issue:
---------
* the backup will contain only lowercase tables
* JBoss will try to see if table TIMERS exists but because of the case, will not find it
* JBoss then tries to create it, but will not be able to do so!

Resolution:
----------------
* In order to be truly portable, all scripts should use lower case for tables/databases.
* Ideally externalise the creation but otherwise, just use "timers" in lowercase
* Similar issue exist in the jms jboss-service.xml with JMS_MESSAGES etc. I would suggest changing the scripts to be in lower case.

Thanks

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira