#25 ✓resolved
samar

error upgrading to grails 1.1.1

Reported by samar | May 17th, 2009 @ 08:50 AM

getting error after upgrading to grails 1.1.1

2009-05-17 19:15:19,984 [705052256@qtp0-2] ERROR hibernate.AssertionFailure - a
n assertion failure occured (this may indicate a bug in Hibernate, but is more l
ikely due to unsafe use of the session)
org.hibernate.AssertionFailure: collection [grailscrowd.core.Mailbox.messages] w
as not processed by flush()

    at org.hibernate.engine.CollectionEntry.postFlush(CollectionEntry.java:2

28)

    at org.hibernate.event.def.AbstractFlushingEventListener.postFlush(Abstr

actFlushingEventListener.java:356)

    at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlus

hEventListener.java:51)

    at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1027)
    at org.springframework.orm.hibernate3.HibernateAccessor.flushIfNecessary

(HibernateAccessor.java:390)

    at org.codehaus.groovy.grails.orm.hibernate.support.GrailsOpenSessionInV

iewInterceptor.flushIfNecessary(GrailsOpenSessionInViewInterceptor.java:115)

    at org.springframework.orm.hibernate3.support.OpenSessionInViewIntercept

or.postHandle(OpenSessionInViewInterceptor.java:181)

    at org.codehaus.groovy.grails.orm.hibernate.support.GrailsOpenSessionInV

iewInterceptor.postHandle(GrailsOpenSessionInViewInterceptor.java:65)

    at org.springframework.web.servlet.handler.WebRequestHandlerInterceptorA

dapter.postHandle(WebRequestHandlerInterceptorAdapter.java:61)

    at org.codehaus.groovy.grails.web.servlet.GrailsDispatcherServlet.doDisp

atch(GrailsDispatcherServlet.java:270)

    at org.springframework.web.servlet.DispatcherServlet.doService(Dispatche

rServlet.java:807)

    at org.springframework.web.servlet.FrameworkServlet.processRequest(Frame

workServlet.java:571)

    at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServ

let.java:511)

    at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502

)

    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(Servlet

Handler.java:1124)

    at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerR

equestFilter.java:70)

    at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(Servlet

Comments and changes to this ticket

  • dima767 (at gmail)

    dima767 (at gmail) May 24th, 2009 @ 05:40 PM

    • State changed from “new” to “resolved”
  • samar

    samar May 24th, 2009 @ 10:49 PM

    can u tell me what changes did u do to fix this error. and also action do i need to take from my end to fix this error??

  • dima767 (at gmail)

    dima767 (at gmail) May 25th, 2009 @ 07:10 AM

    I don't remember exactly, but it has something to do with Hibernate lazy collection proxies being accessed outside of a Session, etc. The fetch type of 'eager' has been set for 'messages' collection in 'Mailbox' model, etc. You could see the exact diffs by going to GitHub (it shows you diffs visually quite nicely).

    On your end, you don't have to do anything other then fetching a fresh copy of the source code from GitHub, doing 'grails upgrade', installing necessary plugins and that's it.

  • samar

    samar May 26th, 2009 @ 08:58 AM

    great work dima, I guess i want to part of grails-crowd development. Can i can contribute to this project and make this a very robust and enterprise application like linked-in

  • dima767 (at gmail)

    dima767 (at gmail) May 26th, 2009 @ 01:06 PM

    Sure. Feel free to clone (fork) the GitHub repo and hack away. When you have some features ready, just send me a 'pull' request, so I could incorporate the code into my repo's 'master' branch, etc. That's the beauty of git and GitHub! :-)

    If you are not familiar with 'git way of working', GitHub has some nice pointers:

    http://github.com/guides/home

    BTW, I just started using new GitHub's 'issues' instead of Lighthouse:

    http://github.com/dima767/grails-crowd/issues

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

Online community for Grails developers worldwide

People watching this ticket

Tags

Pages