[Hibernate-JIRA] Created: (HHH-3030) NullPointerException happens in versioning

Viktor Schmidt (JIRA)

Tuesday, 29 January Tue, 29 Jan

10:22 a.m.

New subject: [Hibernate-JIRA] Commented: (HHH-3030) NullPointerException happens in versioning

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-3030?page=c... ] Viktor Schmidt commented on HHH-3030: ------------------------------------- We've seen this exception several times, too.. i guess there is a problem elsewhere, which causes an increment on a yet nonexistent version value ... a co-worker of me did found the real cause of this exception in his case: There is some non nullable value on the object which was not set... so at commit you get this misleading Exception. You should get a Not-Null Property exception (or something), but in some cases we get this NullPointer one.

...

NullPointerException happens in versioning ------------------------------------------ Key: HHH-3030 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3030 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: any Reporter: John Priority: Minor Here is the stack trace: java.lang.NullPointerException at org.hibernate.type.IntegerType.next(IntegerType.java:59) at org.hibernate.engine.Versioning.increment(Versioning.java:25) at org.hibernate.event.def.DefaultFlushEntityEventListener.getNextVersion(DefaultFlushEntityEventListener.java:358) at org.hibernate.event.def.DefaultFlushEntityEventListener.scheduleUpdate(DefaultFlushEntityEventListener.java:250) at org.hibernate.event.def.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:121) at org.hibernate.event.def.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:196) at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:76) at org.hibernate.event.def.DefaultAutoFlushEventListener.onAutoFlush(DefaultAutoFlushEventListener.java:35) at org.hibernate.impl.SessionImpl.autoFlushIfRequired(SessionImpl.java:969) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1114) at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79) ...... The code is: public Object next(Object current, SessionImplementor session) { return new Integer( ( (Integer) current ).intValue() + 1 ); } Should there be a null checking for the object "current"?

-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply

Rishik Dhar (JIRA)

Tuesday, 20 May Tue, 20 May

9:03 a.m.

New subject: [Hibernate-JIRA] Commented: (HHH-3030) NullPointerException happens in versioning

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-3030?page=c... ] Rishik Dhar commented on HHH-3030: ---------------------------------- I encountered the same problem and after a bit of painful hit and trials I realized the reason in my case was that the table in database corresponding to the object that was being loaded, modified and persisted (and encountered a NullPointerException) was that the version field was a newly introduced column in an existing (and being used by the Application) table with no values in the column to begin with. I have introduced the column and added the mapping however, while loading the objects from the DB, the value for "version" column is "null", hence the exception. I even tried modifying the setter method for the version field in the object being loaded, just to put a default value when a null was encountered, yet it didn't matter because the value is loaded from EntityEntry.getVersion() which is initialized as null as of now. Hope this info helps you!

...

NullPointerException happens in versioning ------------------------------------------ Key: HHH-3030 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3030 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: any Reporter: John Priority: Minor Here is the stack trace: java.lang.NullPointerException at org.hibernate.type.IntegerType.next(IntegerType.java:59) at org.hibernate.engine.Versioning.increment(Versioning.java:25) at org.hibernate.event.def.DefaultFlushEntityEventListener.getNextVersion(DefaultFlushEntityEventListener.java:358) at org.hibernate.event.def.DefaultFlushEntityEventListener.scheduleUpdate(DefaultFlushEntityEventListener.java:250) at org.hibernate.event.def.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:121) at org.hibernate.event.def.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:196) at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:76) at org.hibernate.event.def.DefaultAutoFlushEventListener.onAutoFlush(DefaultAutoFlushEventListener.java:35) at org.hibernate.impl.SessionImpl.autoFlushIfRequired(SessionImpl.java:969) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1114) at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79) ...... The code is: public Object next(Object current, SessionImplementor session) { return new Integer( ( (Integer) current ).intValue() + 1 ); } Should there be a null checking for the object "current"?

-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply

Thomas Modeneis (JIRA)

Wednesday, 28 May Wed, 28 May

10:48 a.m.

New subject: [Hibernate-JIRA] Commented: (HHH-3030) NullPointerException happens in versioning

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-3030?page=c... ] Thomas Modeneis commented on HHH-3030: -------------------------------------- I got this same exception here.... man, its a very ugly workaround... :( ive setted 0 to all version like this: UPDATE table SET version=0 WHERE version is null GO and now all is fine; Please Hibernate Developers, make org.hibernate.type.IntegerType.next be nullSafe. Thanks folks.

...

NullPointerException happens in versioning ------------------------------------------ Key: HHH-3030 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3030 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: any Reporter: John Priority: Minor Here is the stack trace: java.lang.NullPointerException at org.hibernate.type.IntegerType.next(IntegerType.java:59) at org.hibernate.engine.Versioning.increment(Versioning.java:25) at org.hibernate.event.def.DefaultFlushEntityEventListener.getNextVersion(DefaultFlushEntityEventListener.java:358) at org.hibernate.event.def.DefaultFlushEntityEventListener.scheduleUpdate(DefaultFlushEntityEventListener.java:250) at org.hibernate.event.def.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:121) at org.hibernate.event.def.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:196) at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:76) at org.hibernate.event.def.DefaultAutoFlushEventListener.onAutoFlush(DefaultAutoFlushEventListener.java:35) at org.hibernate.impl.SessionImpl.autoFlushIfRequired(SessionImpl.java:969) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1114) at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79) ...... The code is: public Object next(Object current, SessionImplementor session) { return new Integer( ( (Integer) current ).intValue() + 1 ); } Should there be a null checking for the object "current"?

-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply

Rishik Dhar (JIRA)

6:36 a.m.

New subject: [Hibernate-JIRA] Commented: (HHH-3030) NullPointerException happens in versioning

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-3030?page=c... ] Rishik Dhar commented on HHH-3030: ---------------------------------- Prashant, What you have done is stopped using the feature of "version" which is used for optimistic locking at the object level in case of concurrent update on a persistent object in the ORM session level cache. By removing the version field, the entity will no longer be managed by the Hibernate for optimistic locking and will lead to corruption of the state of data in your application. The change you have made may be okay if a concurrent modification of a persistent object never happens in your application, i.e. an object is always accessed sequentially by different transactions within the current session. However, consider this case, if there are two parallel transactions that need to perform a read-write operation on the same object, and both of them read the object simultaneously and update the object, then you transactions will simply ignore the changes made by the other transaction and try to commit their changes and end up corrupting the state of the data. For more information read here: http://www.redhat.com/docs/manuals/jboss/jboss-eap-4.3/doc/hibernate/Hibe... You may want to read this before making the change permanent. The only thing that you need to take care of if you decide to retain the version feature will be introduce the version column in your tables and set the default value as 0 for the respective entities mapped with the version property defined in the HBM.

...

NullPointerException happens in versioning ------------------------------------------ Key: HHH-3030 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3030 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: any Reporter: John Priority: Minor Here is the stack trace: java.lang.NullPointerException at org.hibernate.type.IntegerType.next(IntegerType.java:59) at org.hibernate.engine.Versioning.increment(Versioning.java:25) at org.hibernate.event.def.DefaultFlushEntityEventListener.getNextVersion(DefaultFlushEntityEventListener.java:358) at org.hibernate.event.def.DefaultFlushEntityEventListener.scheduleUpdate(DefaultFlushEntityEventListener.java:250) at org.hibernate.event.def.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:121) at org.hibernate.event.def.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:196) at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:76) at org.hibernate.event.def.DefaultAutoFlushEventListener.onAutoFlush(DefaultAutoFlushEventListener.java:35) at org.hibernate.impl.SessionImpl.autoFlushIfRequired(SessionImpl.java:969) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1114) at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79) ...... The code is: public Object next(Object current, SessionImplementor session) { return new Integer( ( (Integer) current ).intValue() + 1 ); } Should there be a null checking for the object "current"?

-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply

Roger Barnes (JIRA)

Tuesday, 14 July Tue, 14 Jul

9:10 p.m.

New subject: [Hibernate-JIRA] Commented: (HHH-3030) NullPointerException happens in versioning

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-3030?page=c... ] Roger Barnes commented on HHH-3030: ----------------------------------- I've created a workaround for this. It hasn't been thoroughly tested, but it appears to work. It subclasses IntegerType and overrides the next method so that it's nullsafe. To use it, replace the "integer" type in the version hbm definition with this one. public class NullSafeVersionIntegerType extends IntegerType { /** * This override avoids the NullPointerException thrown by IntegerType.next * when a null "current" object is passed in, and returns a 1 instead */ @Override public Object next(Object current, SessionImplementor session) { Object next; if (current != null) { next = super.next(current, session); } else { next = new Integer(1); } return next; } }

...

NullPointerException happens in versioning ------------------------------------------ Key: HHH-3030 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3030 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: any Reporter: John Priority: Minor Here is the stack trace: java.lang.NullPointerException at org.hibernate.type.IntegerType.next(IntegerType.java:59) at org.hibernate.engine.Versioning.increment(Versioning.java:25) at org.hibernate.event.def.DefaultFlushEntityEventListener.getNextVersion(DefaultFlushEntityEventListener.java:358) at org.hibernate.event.def.DefaultFlushEntityEventListener.scheduleUpdate(DefaultFlushEntityEventListener.java:250) at org.hibernate.event.def.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:121) at org.hibernate.event.def.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:196) at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:76) at org.hibernate.event.def.DefaultAutoFlushEventListener.onAutoFlush(DefaultAutoFlushEventListener.java:35) at org.hibernate.impl.SessionImpl.autoFlushIfRequired(SessionImpl.java:969) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1114) at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79) ...... The code is: public Object next(Object current, SessionImplementor session) { return new Integer( ( (Integer) current ).intValue() + 1 ); } Should there be a null checking for the object "current"?

-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply

Gail Badner (JIRA)

Tuesday, 27 April Tue, 27 Apr

4:25 p.m.

New subject: [Hibernate-JIRA] Resolved: (HHH-3030) NullPointerException happens in versioning

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-3030?page=c... ] Gail Badner resolved HHH-3030. ------------------------------ Assignee: Gail Badner Resolution: Rejected This is expected behavior. If an entity is mapped as having a version property, then Hibernate assumes that existing entities will have a non-null version. The database representation needs to be consistent with what is mapped. Hibernate only allows unsaved entities to have a non-null version. Please move further discussion to the user forum (https://forum.hibernate.org/). Thanks, Gail

...

NullPointerException happens in versioning ------------------------------------------ Key: HHH-3030 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3030 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: any Reporter: John Assignee: Gail Badner Priority: Minor Here is the stack trace: java.lang.NullPointerException at org.hibernate.type.IntegerType.next(IntegerType.java:59) at org.hibernate.engine.Versioning.increment(Versioning.java:25) at org.hibernate.event.def.DefaultFlushEntityEventListener.getNextVersion(DefaultFlushEntityEventListener.java:358) at org.hibernate.event.def.DefaultFlushEntityEventListener.scheduleUpdate(DefaultFlushEntityEventListener.java:250) at org.hibernate.event.def.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:121) at org.hibernate.event.def.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:196) at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:76) at org.hibernate.event.def.DefaultAutoFlushEventListener.onAutoFlush(DefaultAutoFlushEventListener.java:35) at org.hibernate.impl.SessionImpl.autoFlushIfRequired(SessionImpl.java:969) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1114) at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79) ...... The code is: public Object next(Object current, SessionImplementor session) { return new Integer( ( (Integer) current ).intValue() + 1 ); } Should there be a null checking for the object "current"?

-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006