• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Weblogic Cache Exception.

 
Ranch Hand
Posts: 50
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi all,
In using WL 6.1 SP4 and I have a method in one facade session bean (with CMT and Required transaction level) that receives a Collection of InvoiceVO to insert them in the database. The max-beans-in-cache property of the InvoiceEJB entity bean is set in 100. When I pass a Collection with more than 100 invoices, the server insert the firsts 100 invoices and throws an weblogic.ejb20.cache.CacheFullException.
Why Weblogic has this behavior, and how can I tell it to change this behavior.
The following is the code of the facade method:
public void loadInvoices(Collection colInv)throws FacadeException {
 try{
   Iterator iterRec=colRec.iterator();
   while(iterRec.hasNext)){
     InvoiceVO invVO=(InvoiceVO)iterRec.next();
     getInvoiceLocalHome().create( //entity bean
       invVO.getInvNumber(),
       invVO.getInvCustomerName(),
       invVO.getInvDate(),
       invVO.getInvAmount(),
       ......,
       ......);
}
 }catch(Exception e){
   throw new FacadeException();
 }
}
[ January 02, 2003: Message edited by: Cristian Cardenas ]
reply
    Bookmark Topic Watch Topic
  • New Topic