February 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-15970) Issue when combining Postgres driver, @MappedSuperclass, generics and enums

by Christian Beikov (JIRA)

1 year, 3 months

1
0
0 / 0

[JIRA] (HHH-15969) Inheritance: org.hibernate.PropertyAccessException Exception

by Christian Beikov (JIRA)

1 year, 3 months

1
0
0 / 0

[JIRA] (HHH-15665) Mariadb is missing identifier quote on SEQUENCE QUERY

by Christian Beikov (JIRA)

1 year, 3 months

1
0
0 / 0

[JIRA] (HHH-16003) Wrong alias used in subquery generated from JPQL

by Christian Beikov (JIRA)

1 year, 3 months

1
0
0 / 0

[JIRA] (HHH-16134) Deploying Hibernate on WAS 8.5.5 tries to use Liberty JTA Platform

by manolan (JIRA)

manolan ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMDU5OTA3NDcx... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16134?atlOrigin=eyJpIjoiMDU5OT... ) HHH-16134 ( https://hibernate.atlassian.net/browse/HHH-16134?atlOrigin=eyJpIjoiMDU5OT... ) Deploying Hibernate on WAS 8.5.5 tries to use Liberty JTA Platform ( https://hibernate.atlassian.net/browse/HHH-16134?atlOrigin=eyJpIjoiMDU5OT... ) Issue Type: Bug Affects Versions: 5.3.23 Assignee: Unassigned Components: hibernate-core Created: 03/Feb/2023 05:39 AM Environment: WAS 8.5.5.22 Priority: Major Reporter: manolan ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) When upgrading some old applications to Hibernate 5, we have encountered a problem where Hibernate tries to use the Liberty JTA Platform: o.s.o.h.SpringSessionContext - Could not introspect Hibernate JtaPlatform for SpringJtaSessionContext org.hibernate.engine.transaction.jta.platform.spi.JtaPlatformException: Could not obtain WebSphere Liberty transaction manager instance at org.hibernate.engine.transaction.jta.platform.internal.WebSphereLibertyJtaPlatform.locateTransactionManager(WebSphereLibertyJtaPlatform.java:42) I can override this by setting hibernate.transaction.jta.platform directly. Looking at *StandardJtaPlatformResolver* source code, I can see that it looks first for the existence of a class com.ibm.tx.jta.TransactionManagerFactory and, if it finds it, chooses to use Liberty. At a guess, I would say this check is flawed and this class is found in Websphere 8.5.5.x not just in the Liberty profile. ( https://hibernate.atlassian.net/browse/HHH-16134#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16134#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100214- sha1:6115380 )

1 year, 3 months

1
0
0 / 0

[JIRA] (HHH-16111) Field annotated with @Version does not increase when entity is updated using merge

by Marco Belladelli (JIRA)

Marco Belladelli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=637b480... ) *commented* on HHH-16111 ( https://hibernate.atlassian.net/browse/HHH-16111?atlOrigin=eyJpIjoiOWU5ZW... ) Re: Field annotated with @Version does not increase when entity is updated using merge ( https://hibernate.atlassian.net/browse/HHH-16111?atlOrigin=eyJpIjoiOWU5ZW... ) Hello Vijayasaradhi Danda ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) , thanks for reporting the issue and providing a reproducer! Looks like in Hibernate 5 you were using the Session#update method, and migrated to using merge with H6. The parent entity in your example has a @ManyToOne(mappedBy=...) association, making it the non-owning side of a bidirectional association. In this case, the JPA spec indicates that the Version attribute used for Optimistic Locking should not be increased. You can read more about version attributes here ( https://jakarta.ee/specifications/persistence/3.1/jakarta-persistence-spe... ). When using Session#update your case worked only because without the SelectBeforeUpdate mapping on your entity, Hibernate’s update method forces an update for the detached parent entity, regardless of its state, thus triggering the Verison increase you expected. If you want the Version attribute to be increased, you should remove the mappedBy from the parent side of the association and add the @JoinColumn there, making it the owning side of the relationship and triggering Optimistic Locking every time you make changes to the child entities collection. Let me know if you need additional help with your issue! ( https://hibernate.atlassian.net/browse/HHH-16111#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16111#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100214- sha1:6115380 )

1 year, 3 months

1
0
0 / 0

[JIRA] (HHH-16003) Wrong alias used in subquery generated from JPQL

by Christian Beikov (JIRA)

1 year, 3 months

1
0
0 / 0

[JIRA] (HHH-16122) Named type [class xxx] did not implement BasicType nor UserType

by Markus Heiden (JIRA)

Markus Heiden ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=6149cfc... ) *commented* on HHH-16122 ( https://hibernate.atlassian.net/browse/HHH-16122?atlOrigin=eyJpIjoiOWFhMT... ) Re: Named type [class xxx] did not implement BasicType nor UserType ( https://hibernate.atlassian.net/browse/HHH-16122?atlOrigin=eyJpIjoiOWFhMT... ) Hi Alexander, I am just a user too that has been hit by this problem. The Hibernate code is complex and not very self-explanatory. So I hope someone from the Hibernate team will help to fix this. If I find some more time, I will try to debug it further to provide a solution. ( https://hibernate.atlassian.net/browse/HHH-16122#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16122#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100214- sha1:6115380 )

1 year, 3 months

1
0
0 / 0

[JIRA] (HHH-16122) Named type [class xxx] did not implement BasicType nor UserType

by Alexander Savov (JIRA)

Alexander Savov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16122 ( https://hibernate.atlassian.net/browse/HHH-16122?atlOrigin=eyJpIjoiMjc2ZD... ) Re: Named type [class xxx] did not implement BasicType nor UserType ( https://hibernate.atlassian.net/browse/HHH-16122?atlOrigin=eyJpIjoiMjc2ZD... ) Hi Markus, Thanks for investigating and root-causing the issue. I saw your pull-request, still not sure I can correlate it to my initial problem. I’ll appreciate if you shed more light. Any idea for a workaround, hack, what-ever, cause this “ class TaskServiceDocument<E extends Enum<E>> “ is a base legacy class I’m not in position to touch and it is working fine with current Hibernate version. Any idea when there might be an official fix, if planned at all? I’m open to jump into some sort of live session, such as zoom, for the sake of efficiency. ( https://hibernate.atlassian.net/browse/HHH-16122#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16122#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100214- sha1:6115380 )

1 year, 3 months

1
0
0 / 0

[JIRA] (HHH-16112) Using hibernate.jdbc.batch_size configuration causes BatchedTooManyRowsAffectedException for OneToMany relationship with orphan removal

by Marco Belladelli (JIRA)

Marco Belladelli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=637b480... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMjllYzdhMDIx... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16112?atlOrigin=eyJpIjoiMjllYz... ) HHH-16112 ( https://hibernate.atlassian.net/browse/HHH-16112?atlOrigin=eyJpIjoiMjllYz... ) Using hibernate.jdbc.batch_size configuration causes BatchedTooManyRowsAffectedException for OneToMany relationship with orphan removal ( https://hibernate.atlassian.net/browse/HHH-16112?atlOrigin=eyJpIjoiMjllYz... ) Change By: Marco Belladelli ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=637b480... ) Summary: Using hibernate.jdbc.batch_size configuration , merge operation to remove a child of entities raises causes BatchedTooManyRowsAffectedException if the child to be removed also has for OneToMany relationship to other children that has to be removed as orphans. with orphan removal ( https://hibernate.atlassian.net/browse/HHH-16112#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16112#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100214- sha1:6115380 )

1 year, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues February 2023