[JPA 2.0] Redoploying app deletes my database?

[Abdullah Dokuyucu]

Hello all,

I'm using Glassfish v3 as app server, Java EE 6 Web, JSF and EclipseLink (JPA 2.0). My project was working just fine, redeploying was no problem, even if I deleted a table from my database EclipseLink would regenerate it without any hassle. But now when I drop a table from my database it will give me the following error:

com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table 'dkyc.question' doesn't exist

when it used to simply remake the table from the Entity. Also, when I undeploy the application, all my tables get dropped! Redeploying remakes the tables but of course the data is lost then.

If someone can helping in this it would be much appreciated.

My persistence.xml:

  <?xml version="1.0" encoding="UTF-8"?>
<persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">
  <persistence-unit name="DkycCreate" transaction-type="JTA">
    <provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
    <jta-data-source>jdbc/dkyc</jta-data-source>
    <properties>
      <property name="eclipselink.ddl-generation" value="create-tables"/>
    </properties>
  </persistence-unit>
  <persistence-unit name="DkycDropCreate" transaction-type="JTA">
    <jta-data-source>jdbc/dkyc</jta-data-source>
    <properties>
      <property name="eclipselink.ddl-generation" value="drop-and-create-tables"/>
    </properties>
  </persistence-unit>
</persistence>
  

And this is the sun-resources.xml

  <?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE resources PUBLIC "-//Sun Microsystems, Inc.//DTD Application Server 9.0 Resource Definitions //EN" "http://www.sun.com/software/appserver/dtds/sun-resources_1_3.dtd">
<resources>
    <jdbc-connection-pool allow-non-component-callers="false" associate-with-thread="false" connection-creation-retry-attempts="0" connection-creation-retry-interval-in-seconds="10" connection-leak-reclaim="false" connection-leak-timeout-in-seconds="0" connection-validation-method="auto-commit" datasource-classname="com.mysql.jdbc.jdbc2.optional.MysqlDataSource" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="true" lazy-connection-association="false" lazy-connection-enlistment="false" match-connections="false" max-connection-usage-count="0" max-pool-size="32" max-wait-time-in-millis="60000" name="mysql_dkyc_rootPool" non-transactional-connections="false" pool-resize-quantity="2" res-type="javax.sql.DataSource" statement-timeout-in-seconds="-1" steady-pool-size="8" validate-atmost-once-period-in-seconds="0" wrap-jdbc-objects="false">
        <property name="serverName" value="localhost"/>
        <property name="portNumber" value="3306"/>
        <property name="databaseName" value="dkyc"/>
        <property name="User" value="root"/>
        <property name="Password" value="mysql"/>
        <property name="URL" value="jdbc:mysql://localhost:3306/dkyc"/>
        <property name="driverClass" value="com.mysql.jdbc.Driver"/>
    </jdbc-connection-pool>
    <jdbc-resource enabled="true" pool-name="mysql_dkyc_rootPool" jndi-name="jdbc/dkyc"  object-type="user"/>
</resources>  

[James Sutherland]

In your persistence.xml you have,

<property name="eclipselink.ddl-generation" value="drop-and-create-tables"/>

This will cause your database to be dropped and re-created when this persistent unit is initialized. If you do not want this, then remove this setting.

EclipseLink will never drop your database on undeploy.

The ddl-generation of "create" should create any missing tables, but this depends on the changes and constraints from existing tables.

What did you change from when it was working?

[Abdullah Dokuyucu]

I deleted and remade my persistance units, which didn't seem to affect. I had an unused realm defined on the server, I deleted that. It's back to normal now... I had that realm defined since a while but looks like it messed with my Glassfish-v3 at some point.

I still couldn't figure out what exactly coused it.

[Abdullah Dokuyucu]

@Stateless
public class ProfileFacade {
    @PersistenceContext(unitName = "DkycCreate")
    private EntityManager em;

I have a persistance unit that has table generation strategy as "Create" and a version of it with the "Drop and Create". Now most tables have the Create one and then another one has got

@PersistenceContext(unitName = "DkycDropCreate")

So I cannot use them together?

I think this problem started after I tried to have a third persistence unit that used a different JNDI and Connection pool (which was for another schema). I was trying to have my application persist from 2 different schemas (from same MySQL server though).

[James Sutherland]

If they have different schema/tables it is fine. But if they share the same tables, then one will be dropping the others tables.