[hibernate-dev] Regressions after upgrading from ORM 4.1.6 to 4.1.8

Guillaume Smet guillaume.smet at gmail.com
Thu Nov 22 10:37:27 EST 2012

Hi Sanne,

On Thu, Nov 22, 2012 at 1:58 PM, Sanne Grinovero <sanne at hibernate.org> wrote:
> Hi Guillaume,
> could you please open a JIRA about that. Do you have suggestions on
> how we could reproduce the problem? Ideally if you could provide a
> unit test that would help.

Thanks for your answer.

Well, my question was about having some guidance on what we could look at.

The errors are quite hard to reproduce and we only have them in a
*big* application with a lot of entities when we are bulk loading a
lot of objects. We don't reproduce these problems on the smaller ones.
That's why a self contained test case is hard to get.

They are totally reproducible on this application though.

>From what we saw in the code, at least one of the stacktraces comes
from a place modified in 4.1.8. That's why we hoped it could ring a
bell just to have the stacktraces.

Typically this one:
Caused by: java.lang.NullPointerException
    at org.hibernate.engine.internal.Cascade.cascadeProperty(Cascade.java:259)
    at org.hibernate.engine.internal.Cascade.cascade(Cascade.java:165)
    at org.hibernate.event.internal.AbstractFlushingEventListener.cascadeOnFlush(AbstractFlushingEventListener.java:160)
    at org.hibernate.event.internal.AbstractFlushingEventListener.prepareEntityFlushes(AbstractFlushingEventListener.java:151)
    at org.hibernate.event.internal.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:88)
    at org.hibernate.event.internal.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:51)
    at org.hibernate.internal.SessionImpl.flush(SessionImpl.java:1213)
    at org.hibernate.ejb.AbstractEntityManagerImpl.flush(AbstractEntityManagerImpl.java:986)

could be related to this particular commit:

Should we try to reproduce it in a debug environment with a
conditional breakpoint to see if we can have more information about
the context?

For the other one, I don't have any idea yet.

In this commit, I find a little weird that the hashCode is tested
before testing the type but I don't think it might be related to the
problem at hand.

I'm opening a JIRA issue.

We are of course commited to getting to the bottom of this but I'm not
very familiar with the ORM code base.


More information about the hibernate-dev mailing list