[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [eclipselink-users] Paging large record set with EclipseLink Query using Sybase runs out of memory
|
It sounds like your driver is causing the memory issue, so it may not help,
but you can set the cache to weak using the persistence.xml property,
"eclipselink.cache.type.default"="Weak". The default is "SoftCache" which
should also allow memory to gc, but weak will allow more gc. You could also
try an isolated cache, "eclipselink.cache.shared.default"="false".
gsilverman wrote:
>
> Sybase does not support a Limit function, if that's what you mean by
> "similar to Oracle". It does support syntax such as "select top 50 from
> ...", So, I can certainly do a search by ordering the list using the
> native query mechanism in EclipseLink JPA, but I'd rather stay away from
> using native SQL.
>
> As for the Sybase driver, I'm using the latest jconnect-3.0. I tried
> EntityManager.clear() before each page query and that did not help. I even
> tried EntityManager.close() and created a new one for each query and,
> again, I still ran out of memory. By the way, what do you mean by "weak
> cache" and how do I go about setting that up?
>
>
>
>
-----
---
http://wiki.eclipse.org/User:James.sutherland.oracle.com James Sutherland
http://www.eclipse.org/eclipselink/
EclipseLink , http://www.oracle.com/technology/products/ias/toplink/
TopLink
Wiki: http://wiki.eclipse.org/EclipseLink EclipseLink ,
http://wiki.oracle.com/page/TopLink TopLink
Forums: http://forums.oracle.com/forums/forum.jspa?forumID=48 TopLink ,
http://www.nabble.com/EclipseLink-f26430.html EclipseLink
Book: http://en.wikibooks.org/wiki/Java_Persistence Java Persistence
--
View this message in context: http://www.nabble.com/Paging-large-record-set-with-EclipseLink-Query-using-Sybase-runs-out-of-memory-tp19655400p19724283.html
Sent from the EclipseLink - Users mailing list archive at Nabble.com.
