WildFly 37, Oracle UCP, Hibernate

[Stephan Mankart]

Hi all,

 we are struggling with the following setup: WildFly 37, Java 17, Hibernate.

We recently noticed that there is a problem with transaction management when we integrate UCP in our application code and expose it via JNDI. Methods annotated as @transactional don’t roll back cleanly in case there are nested transactional methods, because some part is committed midway through the steps when an error occurs.

Then we saw the following post in this group: WIldfly with Oracle UCP, FCF and TAC and with this approach the transaction issue is resolved.

However, when discussing some configuration details with my favorite non-human friend, it pointed out that:

• You are mixing Oracle UCP with WildFly’s own connection pooling, which leads to double pooling and reduces the effectiveness of RAC features such as Fast Connection Failover (FCF).

My questions now are:

1. Is the above statement about double pooling correct?
2. How big of a problem is the “reduced effectiveness”?
3. Is there another way of getting UCP and hibernate to work with WildFly 37? Getting the first approach “UCP via application code” to work seems to be very cumbersome because the UCP DataSource created in this way doesn’t get enlisted in WildFly’s transaction manager (Narayana). 

Any pointers/ experiences welcome!

Thanks,

Stephan 

[Tom Jenkinson]

Given Scott replied on the https://groups.google.com/g/wildfly/c/HfcH4VugxuM/m/3pbn6-WAAwAJ version, I will try to lock this one