Eclipse Community Forums: EclipseLink » Cursor in Eclipselink lazy loading

Help

Home

Home » Eclipse Projects » EclipseLink » Cursor in Eclipselink lazy loading(Cursor in Eclipselink lazy loading )

Show: Today's Messages :: Show Polls :: Message Navigator

Cursor in Eclipselink lazy loading [message #1739662]

Wed, 03 August 2016 14:49

Tareq Zaman

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

Report message to a moderator

Re: Cursor in Eclipselink lazy loading [message #1741080 is a reply to message #1739662]

Mon, 22 August 2016 19:36

Chris Delahunt

Messages: 1389
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.

Report message to a moderator

Previous Topic:	Isolated L1 cache lifetime with no @Transactional boundary
Next Topic:	Embeddable mapping issues

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 19 11:01:18 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter