• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Tim Cooke
  • Liutauras Vilda
  • Jeanne Boyarsky
Sheriffs:
  • Paul Clapham
  • Rob Spoor
  • Junilu Lacar
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Piet Souris
  • Carey Brown
Bartenders:

fetch=FetchType.LAZY causes transaction timeout

 
Ranch Hand
Posts: 41
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
In one part of my web app i have 4 entities that are linked to eachother by an arraylist, they are annotaded with @OneToMany and the fetchtype is default which is fetch=FetchType.LAZY.

My problem is that it takes to long to get all those entities that are linked in the chain, According to Spring they must be retrived in a transaction, thats fine but it takes to long so it will result in
a transaction rollback, the transaction timeout is set to 5 min and it is deployed o websphere. the guys that are in charge of websphere do not want to raise the transaction timeout due to other applications on the server and unnecessary use
of resources, also they dont know what effect it will have on other applications if raised. How can i solve this ?
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic