I have an application that uses a mysql backend. I have been developing on my local machine for quite some time now with no problems, but recently setup the application on EC2. When the same application runs on the EC2 instance, the queries throw errors and say that schema.table does not exist. The query itself doesnt have the schema yet it still throws an error. Yet again it works fine when i connect to my local mysql database instead of the EC2 instance. Both databases are set up identically.

My connections are done through the datasource xml files in jboss. They are as follows.

What could I be missing?

<jndi-name>env/jdbc/Spotlete_DBase</jndi-name>

<!-- JDBC Connection URL-->
<connection-url>
jdbc:mysql://instancename:3306/databasename
</connection-url>

<!-- JDBC Driver Class -->
<driver-class>
com.mysql.jdbc.Driver
</driver-class>

<!--Login Information-->
<user-name>UN</user-name>
<password>PW</password>

<!--pooling parameters-->
<min-pool-size>1</min-pool-size>
<max-pool-size>3</max-pool-size>
<defaultAutoCommit>false</defaultAutoCommit>

<blocking-timeout-millis>5000</blocking-timeout-millis>
<idle-timeout-minutes>30</idle-timeout-minutes>
</local-tx-datasource>

I figured out the issue. I am working off of a windows machine, and the EC2 image is an Ubuntu machine. Apparently windows doesnt care about table names and case sensativity. I had the table names capitalized in the hibernate mappings, and mysql stores them as lowercase. Changing the mappings to lower case worked on both systems.