We're working on an ecommerce site which has a rather large (> 3M) record products table. We were hoping that the Collection which is returned when an entity bean's collection field getter is called would be smart .. that the entity beans would be instantiated as needed vs all instantiated at once. Alas, it appears that this is not the case. I initially ran out of memory trying to get the collection until I applied the ApplicationAdministrator.flushEJBCache hack, but the elapsed time is still just too large when dealing with that collection. My question is how are people handling this kind of problem? Should I just abandon CMP for this stuff and do it in a traditional fashion, perhaps a temporary table, via JDBC? Maybe cache the handles from the CMP collections for reuse? Go for a database specific solution? tia john d
- Anyone heard from evermind? Robert Krueger
- Re: Anyone heard from evermind? Klaus Thiele
- RE: Anyone heard from evermind? J.T. Wenting
- Re: Anyone heard from evermind? Karl Avedal
- Re: Anyone heard from evermind? Robert Krueger
- RE: Anyone heard from evermind? Kevin Duffey
- Can orion ssl bind to non-default port ... Keith Kwiatek
- Re: Can orion ssl bind to non-defa... Sach Jobb
- Re: Large Collections John D'Ausilio
- Re: Large Collections Robert Krueger
- RE: Anyone heard from evermind? J.T. Wenting
- SSL and JSSE... how do you do it? Keith Kwiatek
- Re: Anyone heard from evermind? Jim Archer
- SV: Anyone heard from evermind? Klaus . Myrseth
- RE: Anyone heard from evermind? Kemp Randy-W18971
- Re: Anyone heard from evermind? Ernst de Haan
- RE: Anyone heard from evermind? Kemp Randy-W18971
- Re: Anyone heard from evermind? Karl Avedal
- Re: Anyone heard from evermind? Jim Archer