> Check the number of records being returned by your queries. > I had this problem and no matter what you turn the JVm Heap > size up to, it will not fix it. There is no good way to > track this down. What I ended up doing is after every query > ran, I logged the number of records returned. I discovered > that one query was returning over 90,000 records everytime > and the more often it ran, the more outofmemory errors I was getting. > Hope this helps.
Well, I don't think this is just related to the number of records returned. I suspect that there's a memory leak in the database drivers you're using, and big recordsets just help you see that leak faster. Lately, for our clients using MS SQL Server 2000, I've been deploying the MS JDBC drivers instead of the ones that come with CF, and so far that has seemed to improve performance and stability for some of them. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ phone: 202-797-5496 fax: 202-797-5444 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Sams Teach Yourself Regular Expressions in 10 Minutes by Ben Forta http://www.houseoffusion.com/banners/view.cfm?bannerid=40 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:182411 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
