July 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-16968) StackOverflowError when using NaturalIdLoadAccess and bi-directional association

by Joris Kuipers (JIRA)

Joris Kuipers ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16968 ( https://hibernate.atlassian.net/browse/HHH-16968?atlOrigin=eyJpIjoiZGI4Nm... ) Re: StackOverflowError when using NaturalIdLoadAccess and bi-directional association ( https://hibernate.atlassian.net/browse/HHH-16968?atlOrigin=eyJpIjoiZGI4Nm... ) I just tried with 6.2.7 (hadn’t done that yet), but it results in the same issue. ( https://hibernate.atlassian.net/browse/HHH-16968#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16968#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#100232- sha1:a133497 )

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16833) Assertion Error when inserting two entities linked with a OneToOne relation

by Andrea Boriero (JIRA)

Andrea Boriero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16833 ( https://hibernate.atlassian.net/browse/HHH-16833?atlOrigin=eyJpIjoiZmNjMz... ) Re: Assertion Error when inserting two entities linked with a OneToOne relation ( https://hibernate.atlassian.net/browse/HHH-16833?atlOrigin=eyJpIjoiZmNjMz... ) Hi Simon Convent ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=6155bc7... ) , thanks to you for reporting the issue and for the test case. ( https://hibernate.atlassian.net/browse/HHH-16833#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16833#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#100232- sha1:a133497 )

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16977) NullPointerException in EntityEntryContext.downgradeLocks

by Laurent Klock (JIRA)

Laurent Klock ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5b8d279... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNTgzYjhiMTdm... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16977?atlOrigin=eyJpIjoiNTgzYj... ) HHH-16977 ( https://hibernate.atlassian.net/browse/HHH-16977?atlOrigin=eyJpIjoiNTgzYj... ) NullPointerException in EntityEntryContext.downgradeLocks ( https://hibernate.atlassian.net/browse/HHH-16977?atlOrigin=eyJpIjoiNTgzYj... ) Issue Type: Bug Affects Versions: 5.6.15 Assignee: Unassigned Components: hibernate-core Created: 24/Jul/2023 01:53 AM Priority: Major Reporter: Laurent Klock ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5b8d279... ) We have the following error that appears systematically after completion of transaction It doesn’t seem to have an impact on transaction completion but it is growing unnecessarily the log files <1690183921438> <[severity-value: 16] [rid: 0] [partition-id: 0] [partition-name: DOMAIN] > <BEA-110401> <Ignoring error in afterCompletion. Object=org.hibernate.resource.transaction.backend.jta.internal.synchronization.RegisteredSynchronization@69031366, Exception=java.lang.NullPointerException java.lang.NullPointerException at org.hibernate.engine.internal.EntityEntryContext.downgradeLocks(EntityEntryContext.java:371) at org.hibernate.engine.internal.StatefulPersistenceContext.afterTransactionCompletion(StatefulPersistenceContext.java:303) at org.hibernate.internal.SessionImpl.afterTransactionCompletion(SessionImpl.java:2448) at org.hibernate.engine.jdbc.internal.JdbcCoordinatorImpl.afterTransactionCompletion(JdbcCoordinatorImpl.java:456) at org.hibernate.resource.transaction.backend.jta.internal.JtaTransactionCoordinatorImpl.afterCompletion(JtaTransactionCoordinatorImpl.java:385) at org.hibernate.resource.transaction.backend.jta.internal.synchronization.SynchronizationCallbackCoordinatorNonTrackingImpl.doAfterCompletion(SynchronizationCallbackCoordinatorNonTrackingImpl.java:60) at org.hibernate.resource.transaction.backend.jta.internal.synchronization.SynchronizationCallbackCoordinatorTrackingImpl.afterCompletion(SynchronizationCallbackCoordinatorTrackingImpl.java:72) at org.hibernate.resource.transaction.backend.jta.internal.synchronization.RegisteredSynchronization.afterCompletion(RegisteredSynchronization.java:44) at weblogic.transaction.internal.ServerSCInfo.doAfterCompletion(ServerSCInfo.java:1145) at weblogic.transaction.internal.ServerSCInfo.callAfterCompletionsForTier(ServerSCInfo.java:1121) at weblogic.transaction.internal.ServerSCInfo.callAfterCompletions(ServerSCInfo.java:1093) at weblogic.transaction.internal.ServerTransactionImpl.callAfterCompletions(ServerTransactionImpl.java:3762) at weblogic.transaction.internal.ServerTransactionImpl.afterCommittedStateHousekeeping(ServerTransactionImpl.java:3651) at weblogic.transaction.internal.ServerTransactionImpl.setCommitted(ServerTransactionImpl.java:3705) at weblogic.transaction.internal.ServerTransactionImpl.globalRetryCommit(ServerTransactionImpl.java:3421) at weblogic.transaction.internal.ServerTransactionImpl.globalCommit(ServerTransactionImpl.java:3316) at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:322) at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:270) at weblogic.ejb.container.internal.BaseLocalObject.postInvoke1(BaseLocalObject.java:316) at weblogic.ejb.container.internal.BaseLocalObject.__WL_postInvokeTxRetry(BaseLocalObject.java:195) at weblogic.ejb.container.internal.SessionLocalMethodInvoker.invoke(SessionLocalMethodInvoker.java:46) at eu.europa.ec.estat.disschain.ref2diss.impl.AuditorImpl_od5q9s_AuditorImpl.terminateProcess(Unknown Source) at eu.europa.ec.estat.disschain.eb2diss.dispatcher.AbstractDispatcher.resolveContext(AbstractDispatcher.java:115) ( https://hibernate.atlassian.net/browse/HHH-16977#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16977#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#100232- sha1:a133497 )

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16882) Invalid alias in a @Where clause with @Inheritance(JOINED)

by Vincent Bouthinon (JIRA)

Vincent Bouthinon ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=70121%3... ) *commented* on HHH-16882 ( https://hibernate.atlassian.net/browse/HHH-16882?atlOrigin=eyJpIjoiZDYxZj... ) Re: Invalid alias in a @Where clause with @Inheritance(JOINED) ( https://hibernate.atlassian.net/browse/HHH-16882?atlOrigin=eyJpIjoiZDYxZj... ) Sorry in holiday. Ah, I don't think that has already worked in a previous Hibernate version. No problem to change this ticket to an enhancement. In my case, it's an attribute that is mapped by a @MappedSuperClass for logical deletion. So, all our objects must carry a @Where clause with this attribute as the predicate, @Where("active=1") , which I dynamically add to avoid having to put it manually on all objects ( https://hibernate.atlassian.net/browse/HHH-16882#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16882#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#100232- sha1:a133497 )

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16976) Timestamps are not properly handled in batched select queries

by Alex Nistico (JIRA)

Alex Nistico ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNGQ3YzE1ZjFi... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16976?atlOrigin=eyJpIjoiNGQ3Yz... ) HHH-16976 ( https://hibernate.atlassian.net/browse/HHH-16976?atlOrigin=eyJpIjoiNGQ3Yz... ) Timestamps are not properly handled in batched select queries ( https://hibernate.atlassian.net/browse/HHH-16976?atlOrigin=eyJpIjoiNGQ3Yz... ) Change By: Alex Nistico ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) In Hibernate 6 entities are selected using JDBC arrays for their key lookup when bach size > 1, the problem is that the JDBC driver could create the array of object to bind by just calling toString() on the instances, and java.sql.Timestamp produces a string representation that is based on the system timezone, which is not necessarily the same timezone as the database failing to retrieve entities by id. The problem can be worked around by annotating the entity with @BatchSize(size=1), but that is not ideal. Attached is a reproduction project ( https://hibernate.atlassian.net/browse/HHH-16976#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16976#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#100232- sha1:a133497 )

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16976) Timestamps are not properly handled in batched select queries

by Alex Nistico (JIRA)

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16976) Timestamps are not properly handled in batched select queries

by Alex Nistico (JIRA)

Alex Nistico ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiM2NiY2VjNmRk... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16976?atlOrigin=eyJpIjoiM2NiY2... ) HHH-16976 ( https://hibernate.atlassian.net/browse/HHH-16976?atlOrigin=eyJpIjoiM2NiY2... ) Timestamps are not properly handled in batched select queries ( https://hibernate.atlassian.net/browse/HHH-16976?atlOrigin=eyJpIjoiM2NiY2... ) Issue Type: Bug Affects Versions: 6.2.5 Assignee: Unassigned Components: hibernate-core Created: 23/Jul/2023 20:54 PM Priority: Major Reporter: Alex Nistico ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) In Hibernate 6 entities are selected using JDBC arrays for their key lookup when bach size > 1, the problem is that the JDBC driver could create the array of object to bind by just calling toString() on the instances, and java.sql.Timestamp produces a string representation that is based on the system timezone, which is not necessarily the same timezone as the database failing to retrieve entities by id. The problem can be worked around by annotating the entity with @BatchSize(size=1), but that is not ideal. ( https://hibernate.atlassian.net/browse/HHH-16976#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16976#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#100232- sha1:a133497 )

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16253) [Envers] Schema Validation Failure With Audited (N)Clob Column with Hibernate 6 on H2

by Tristan Lins (JIRA)

Tristan Lins ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16253 ( https://hibernate.atlassian.net/browse/HHH-16253?atlOrigin=eyJpIjoiOGNkZD... ) Re: [Envers] Schema Validation Failure With Audited (N)Clob Column with Hibernate 6 on H2 ( https://hibernate.atlassian.net/browse/HHH-16253?atlOrigin=eyJpIjoiOGNkZD... ) Unfortunately, I'm lost here. From here, a Hibernate developer who knows the internal structures better would have to take over. This is not a simple bug fix, there is probably more to be rebuilt here. ( https://hibernate.atlassian.net/browse/HHH-16253#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16253#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#100232- sha1:4329f54 )

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16253) [Envers] Schema Validation Failure With Audited (N)Clob Column with Hibernate 6 on H2

by Tristan Lins (JIRA)

Tristan Lins ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16253 ( https://hibernate.atlassian.net/browse/HHH-16253?atlOrigin=eyJpIjoiNzI2YT... ) Re: [Envers] Schema Validation Failure With Audited (N)Clob Column with Hibernate 6 on H2 ( https://hibernate.atlassian.net/browse/HHH-16253?atlOrigin=eyJpIjoiNzI2YT... ) I guess I was a bit hasty. The attribute type is set in the BasicMetadataGenerator.applyNestedType(..) ( https://github.com/hibernate/hibernate-orm/blob/6.2.6/hibernate-envers/sr... ) method. Only the type name is used here. The sqlType is effectively lost here. ( https://hibernate.atlassian.net/rest/api/3/attachment/content/50523 ) ( https://hibernate.atlassian.net/rest/api/3/attachment/content/50524 ) ( https://hibernate.atlassian.net/browse/HHH-16253#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16253#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#100232- sha1:4329f54 )

2 years, 8 months

1
0
0 / 0

[JIRA] (HHH-16253) [Envers] Schema Validation Failure With Audited (N)Clob Column with Hibernate 6 on H2

by Tristan Lins (JIRA)

Tristan Lins ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16253 ( https://hibernate.atlassian.net/browse/HHH-16253?atlOrigin=eyJpIjoiODU3MD... ) Re: [Envers] Schema Validation Failure With Audited (N)Clob Column with Hibernate 6 on H2 ( https://hibernate.atlassian.net/browse/HHH-16253?atlOrigin=eyJpIjoiODU3MD... ) I think I might have found the spot. The BasicMetadataGenerator#buildProperty(..) ( https://github.com/hibernate/hibernate-orm/blob/6.2.6/hibernate-envers/sr... ) calls ColumnContainer#addColumnsFromValue(..) ( https://github.com/hibernate/hibernate-orm/blob/6.2.6/hibernate-envers/sr... ) , which calls Column.from(..) ( https://github.com/hibernate/hibernate-orm/blob/6.2.6/hibernate-envers/sr... ). And within this copy-function, the sql type gets lost. This looks like a fundamental error, because envers' Column class is not able to map a clob type at all. ( https://hibernate.atlassian.net/browse/HHH-16253#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16253#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#100232- sha1:4329f54 )

2 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues July 2023