Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » EclipseLink » Cursor in Eclipselink lazy loading(Cursor in Eclipselink lazy loading )
Cursor in Eclipselink lazy loading [message #1739662] Wed, 03 August 2016 14:49 Go to next message
Tareq Zaman is currently offline Tareq ZamanFriend
Messages: 2
Registered: August 2016
Location: USA
Junior Member
Hi,

We use Eclipselink version 2.5.2.v20140319 to connect to SQL server
2008 from Weblogic 12C EJB container. We have connection pool set up
in Weblogic server, using Eclilpselink sessions.xml for connectivity
setup. What we are seeing simple lazy loading SQL queries creating
Fetch API cursor on the database side. These fetch API cursors taking
huge memory. Does anybody know if lazy loading creates cursors by
default or there is a way to turn it off?
I have been looking up on this thing, not able to get concrete
evidence. Any pointers would be appreciated.
Thank you for reading this.

TZ
Re: Cursor in Eclipselink lazy loading [message #1741080 is a reply to message #1739662] Mon, 22 August 2016 19:36 Go to previous message
Chris Delahunt is currently offline Chris DelahuntFriend
Messages: 1275
Registered: July 2009
Senior Member
Default isn't quite default when you are talking about using sessions.xml. Sessions.xml is legacy native EclipseLink/TopLink api access giving full control over everything. It could be that your application was configured to use cursors, but you need to look at what those cursors are accessing then trace back to your mappings to help narrow it down. If you can isolate the process triggering the read in the database, that would also help.
Previous Topic:Copying Tenant Data
Next Topic:Isolated L1 cache lifetime with no @Transactional boundary
Goto Forum:
  


Current Time: Thu Dec 14 02:08:55 GMT 2017

Powered by FUDForum. Page generated in 0.02020 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software