We face a strange behavior after upgrade from hibernate 4.1.10 to 5.2.10.
The following code is working on version (4.1.10)

Session session1 = sessionFactory.openSession();
System.out.println("session 1 opened");
session1.beginTransaction();
System.out.println("Transaction 1 begin");

/////

Session session2 = sessionFactory.openSession();
System.out.println("session 2 opened");
session2.beginTransaction();
System.out.println("Transaction 2 begin");
session2.getTransaction().commit();
System.out.println("Transaction 2 commit");
session2.close();
System.out.println("session 2 close");

//////

session1.getTransaction().commit();
System.out.println("Transaction 1 commit");
session1.close();
System.out.println("session 1 close");

with the following config

<property name="connection.datasource">.....</property>
<property name="transaction.factory_class">org.hibernate.transaction.JTATransactionFactory</property>
<property name="transaction.manager_lookup_class">org.hibernate.transaction.WeblogicTransactionManagerLookup</property>


and we get the session factory using this code

Configuration configuration = new Configuration();
configuration.configure("com/code/dal/hibernate.cfg.xml");
ServiceRegistry serviceRegistry = new ServiceRegistryBuilder().applySettings(configuration.getProperties()).buildServiceRegistry();
sessionFactory = configuration.buildSessionFactory(serviceRegistry);


The same code throw " java.lang.IllegalStateException: Transaction already active" after the upgrade.

The new config is

<property name="connection.datasource">........</property>
<property name="hibernate.transaction.coordinator_class">org.hibernate.resource.transaction.backend.jta.internal.JtaTransactionCoordinatorBuilderImpl</property>
<property name="hibernate.transaction.jta.platform">org.hibernate.engine.transaction.jta.platform.internal.WeblogicJtaPlatform</property>

and we now get the session factory using this code

StandardServiceRegistry standardRegistry = new StandardServiceRegistryBuilder().configure("com/code/dal/hibernate.cfg.xml").build();
Metadata metadata = new MetadataSources(standardRegistry).getMetadataBuilder().build();
sessionFactory = metadata.getSessionFactoryBuilder().build();

It's not legal to coordinate transactions manually in JTA. I created a test for this use case:



When I try to run it, I get:



which is fine since we are in a JTA environment.

What you need to do is let the JTA TransactionManager do the management for you.



Which works like a charm. Use the Java EE application server to coordinate that for you.

Thanks a lot for your quick response.

I tried the following snippet of code :

Session session1 = sessionFactory.openSession();
Bean b = new Bean();
b.setName("test");
session1.save(b);
session1.close();

and nothing has been inserted at the database

Also, I want to mention that the behavior mentioned at the original post was working before the upgrade.

From the configs alone, I can't tell why this might happen, so you need to debug it and see what's causing the issue.

We already debug our code carefully and also attache the source code of hibernate itself to the libs and debug inside it and found the following:

There is only one TransactionManager. Before beginning any transaction any call to transactionManager.getStatus() it returns "inactive" after beginning any transaction the status turns to "active" and we won't be able to begin any subsequent transactions. We tried also to disable the cache so we have different objects from the "TransactionManager" but also all the inquiries for the status after beginning the first one returns "active".