February 2020 - hibernate-issues - Jboss List Archives

Nathan Xu ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-13867 ( https://hibernate.atlassian.net/browse/HHH-13867?atlOrigin=eyJpIjoiY2RlN2... ) Re: StaleObjectStateException into a SINGLE transaction for entity with version field of type java.util.Date ( https://hibernate.atlassian.net/browse/HHH-13867?atlOrigin=eyJpIjoiY2RlN2... ) It turns out that the root cause is MySQL doesn’t adhere to SQL standard that default TIMESTAMP type’s fractional second precision should be 6 (to maintain backward compatibility). See https://dev.mysql.com/doc/refman/5.6/en/fractional-seconds.html In your specific case, if you specify precision explicitly, the bug should disappear. However, this seems still a bug of Hibernate in terms of MySQL dialect issue. I’ll think about how to fix it later soon. Thanks for your report! ( https://hibernate.atlassian.net/browse/HHH-13867#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13867#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#100120- sha1:2415f4c )

4 years, 4 months

1
0
0 / 0

[JIRA] (HHH-13867) StaleObjectStateException into a SINGLE transaction for entity with version field of type java.util.Date

by Nathan Xu (JIRA)

4 years, 4 months

1
0
0 / 0

[JIRA] (HHH-13867) StaleObjectStateException into a SINGLE transaction for entity with version field of type java.util.Date

by Nathan Xu (JIRA)

Nathan Xu ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-13867 ( https://hibernate.atlassian.net/browse/HHH-13867?atlOrigin=eyJpIjoiYjMzMz... ) Re: StaleObjectStateException into a SINGLE transaction for entity with version field of type java.util.Date ( https://hibernate.atlassian.net/browse/HHH-13867?atlOrigin=eyJpIjoiYjMzMz... ) Bug reproduced easily with your repo. Thanks for the bug report of high quality. Will follow up shortly and keep you in loop. I am a community contributor as well. ( https://hibernate.atlassian.net/browse/HHH-13867#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13867#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#100120- sha1:2415f4c )

4 years, 4 months

1
0
0 / 0

[JIRA] (HHH-13867) StaleObjectStateException into a SINGLE transaction for entity with version field of type java.util.Date

by Глеб Егунов (JIRA)

Глеб Егунов ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMWQwNjA1NTA4... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-13867?atlOrigin=eyJpIjoiMWQwNj... ) HHH-13867 ( https://hibernate.atlassian.net/browse/HHH-13867?atlOrigin=eyJpIjoiMWQwNj... ) StaleObjectStateException into a SINGLE transaction for entity with version field of type java.util.Date ( https://hibernate.atlassian.net/browse/HHH-13867?atlOrigin=eyJpIjoiMWQwNj... ) Change By: Глеб Егунов ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) He team\! We got stuck with the following issue: StaleObjectStateException arises during the update execution into the SINGLE transaction. Feel free to look and clone the minimal example from +*bitbucket*+: [https://bitbucket.org/gegunov/hibernate_issue /src/master/ |https://bitbucket.org/gegunov/hibernate_issue/src/master/] *WIKI* with examples are also attached there. Steps to reproduce: *prerequisites*: * Table DDL {code:java}CREATE TABLE `payment` ( `id` int(11) NOT NULL AUTO_INCREMENT, `status` varchar(45) DEFAULT NULL, `last_update_date` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP, PRIMARY KEY (`id`), UNIQUE KEY `id_UNIQUE` (`id`) ) ENGINE=InnoDB AUTO_INCREMENT=5 DEFAULT CHARSET=latin1{code} * Entity class with fields: 1) of type *java.util.Date* annotated by *@Version* e.g *lastUpdateDate* 2) of type java.util.String for *state* 3) of type Long (for *Id*) # Create entity having any state. # Then in the other transaction execute the following steps: ## *find* the created entity with entityManager.find ## *update* the field state (of type String) ## execute another one *select* from database using entityManager. It doesn't matter what it will return. It could even return *nothing*. In the provided code I deliberately use keys which not exist in DB ## *update* the entity again with different value. # When the transaction is being committed it will fail with the following error *_org.hibernate.StaleObjectStateException_*: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect) It should be said that the mentioned behavior is not reproduced with the version field of type *short*, only with *java.util.Date* ( https://hibernate.atlassian.net/browse/HHH-13867#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13867#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#100120- sha1:2415f4c )

4 years, 4 months

1
0
0 / 0

[JIRA] (HHH-13867) StaleObjectStateException into a SINGLE transaction for entity with version field of type java.util.Date

by Глеб Егунов (JIRA)

Глеб Егунов ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZTdhZmZkNjdi... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-13867?atlOrigin=eyJpIjoiZTdhZm... ) HHH-13867 ( https://hibernate.atlassian.net/browse/HHH-13867?atlOrigin=eyJpIjoiZTdhZm... ) StaleObjectStateException into a SINGLE transaction for entity with version field of type java.util.Date ( https://hibernate.atlassian.net/browse/HHH-13867?atlOrigin=eyJpIjoiZTdhZm... ) Change By: Глеб Егунов ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) He team \ ! We got stuck with the following issue: StaleObjectStateException arises during the update execution into the SINGLE transaction. Feel free to look at and clone the code on * minimal example from + * bitbucket + * + : [ https://bitbucket.org/gegunov/hibernate_issue/src/master/ |https://bitbucket.org/gegunov/hibernate_issue/src/master/] * README WIKI * with examples are also attached there. Steps to reproduce: *prerequisites*: * Table DDL {code :java }CREATE TABLE `payment` ( `id` int(11) NOT NULL AUTO_INCREMENT, `status` varchar(45) DEFAULT NULL, `last_update_date` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP, PRIMARY KEY (`id`), UNIQUE KEY `id_UNIQUE` (`id`) ) ENGINE=InnoDB AUTO_INCREMENT=5 DEFAULT CHARSET=latin1{code} * Entity class with fields: 1) of type *java.util.Date* annotated by *@Version* e.g *lastUpdateDate* 2) of type java.util.String for *state* 3) of type Long (for *Id*) # Create entity having any state. # Then in the other transaction execute the following steps: ## *find* the created entity with entityManager.find ## *update* the field state (of type String) ## execute another one *select* from database using entityManager. It doesn't matter what it will return. It could even return *nothing*. In the provided code I deliberately use keys which not exist in DB ## *update* the entity again with different value. # When the transaction is being committed it will fail with the following error *_org.hibernate.StaleObjectStateException_*: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect) It should be said that the mentioned behavior is not reproduced with the version field of type *short*, only with *java.util.Date* ( https://hibernate.atlassian.net/browse/HHH-13867#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13867#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#100120- sha1:2415f4c )

4 years, 4 months

1
0
0 / 0

[JIRA] (HHH-13867) StaleObjectStateException into a SINGLE transaction for entity with version field of type java.util.Date

by Глеб Егунов (JIRA)

Глеб Егунов ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZjM1NWY3ZjI5... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-13867?atlOrigin=eyJpIjoiZjM1NW... ) HHH-13867 ( https://hibernate.atlassian.net/browse/HHH-13867?atlOrigin=eyJpIjoiZjM1NW... ) StaleObjectStateException into a SINGLE transaction for entity with version field of type java.util.Date ( https://hibernate.atlassian.net/browse/HHH-13867?atlOrigin=eyJpIjoiZjM1NW... ) Issue Type: Bug Assignee: Unassigned Created: 14/Feb/2020 08:31 AM Priority: Major Reporter: Глеб Егунов ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) He team! We got stuck with the following issue: StaleObjectStateException arises during the update execution into the SINGLE transaction. Feel free to look at the code on *bitbucket* : https://bitbucket.org/gegunov/hibernate_issue/src/master/ *README* with examples are also attached there. Steps to reproduce: *prerequisites* : * Table DDL CREATE TABLE `payment` ( `id` int (11) NOT NULL AUTO_INCREMENT, `status` varchar(45) DEFAULT NULL, `last_update_date` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP, PRIMARY KEY (`id`), UNIQUE KEY `id_UNIQUE` (`id`) ) ENGINE=InnoDB AUTO_INCREMENT=5 DEFAULT CHARSET=latin1 * Entity class with fields: 1) of type *java.util.Date* annotated by *@Version* e.g *lastUpdateDate* 2) of type java.util.String for *state* 3) of type Long (for *Id* ) * Create entity having any state. * Then in the other transaction execute the following steps: * *find* the created entity with entityManager.find * *update* the field state (of type String) * execute another one *select* from database using entityManager. It doesn't matter what it will return. It could even return *nothing*. In the provided code I deliberately use keys which not exist in DB * *update* the entity again with different value. * When the transaction is being committed it will fail with the following error *org.hibernate.StaleObjectStateException* : Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect) It should be said that the mentioned behavior is not reproduced with the version field of type *short* , only with *java.util.Date* ( https://hibernate.atlassian.net/browse/HHH-13867#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13867#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#100120- sha1:2415f4c )

4 years, 4 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 2020