[jboss-jira] [JBoss JIRA] (WFLY-7533) hibernate.hbm2ddl.auto value="update" on PostgresSQL 9.4 DB issue with Hibenate 5.1 & Wildfly 10.1.0

Parag Goyal created WFLY-7533: --------------------------------- Summary: hibernate.hbm2ddl.auto value="update" on PostgresSQL 9.4 DB issue with Hibenate 5.1 & Wildfly 10.1.0 Key: WFLY-7533 URL: https://issues.jboss.org/browse/WFLY-7533 Project: WildFly Issue Type: Bug Components: JPA / Hibernate Affects Versions: 10.1.0.Final Reporter: Parag Goyal Assignee: Scott Marlow I have an application presently running (without issue) on Wildfly 8.2.1 Final & PostgresSQL 9.4(x86), now we are trying to upgrade our application to WildFly 10.1.0 (Final) with PostgresSQL 9.4(x86). Most of this upgrade is going well but the upgrade from Hibernate 4.3.7 (on Wildfly 8.2.1) to Hibernate 5.0.1 (on WildFly 10.1) is causing an issue. Specifically, in persistence.xml we have below property and DB is PostgresSQL 9.4(x86). <property name="hibernate.hbm2ddl.auto" value="update"/> NOTE: We have not done any schema change or other DB changes with this upgrade and also pointing to same database instance on PostgresSQL 9.4(x86) which was successfully running with Wildfly 8.2.1 instance. Seems <property name="hibernate.hbm2ddl.auto" value="update"/> is behaving like <property name="hibernate.hbm2ddl.auto" value="create"/> and It is trying to create tables which are actually already exists. i.e. 1) Erroneously it determines that it needs to create new relation(s). 2) Fail to do above step. Following is stack trace: Caused by: javax.persistence.PersistenceException: [PersistenceUnit: cms_layoutmgt] Unable to build Hibernate SessionFactory Caused by: org.hibernate.tool.schema.spi.SchemaManagementException: Unable to execute schema management to JDBC target [create table CMS_LAYM_APPLICATIONS (ID serial not null, mCommandLineArg varchar(255), mDescription varchar(4000), mHandleByCaption boolean NOT NULL DEFAULT TRUE, mName varchar(255), mPath varchar(255), mTags varchar(2000), mWindowTitle varchar(255), mWorkingDir varchar(255), Display_Id int4, primary key (ID))] Caused by: org.postgresql.util.PSQLException: ERROR: relation \\\"cms_laym_applications\\\" already exists\", Kindly provide solution for above issue, thanks in advance. -- This message was sent by Atlassian JIRA (v7.2.3#72005)