• 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

delay between create and ejbcreate

 
Ranch Hand
Posts: 222
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi All,
We are facing a problem in an application using EJBs. We are using JBoss2.4, ejb 1.1 compliant beans, Oracle 8i database on Solaris server. We have around 20 tables in the database, out of which, 4 tables are used most frequently. In all these four tables, maximum inserts (create through bean's home interface) are being called, means no select, update, delete. In a day, around 12,000 to 13,000 records are inserted in all these four tables.
We have noticed that when the application server is started/restarted, the
application runs pretty smoothly... but after like around 3-4 days (each day around 12000-13000 records inserted)..... delay is noticed while inserting new records. The delay happens for insert, meaning between create() and ejbCreate() of the entitybean. The create() in home
interface gets called, and it takes long time in calling the ejbCreate on the server side.
The delay begins after 3-4 days, with a couple of seconds and incrementally increases to get into minutes. Once the delay starts in seconds, in less than 4 hours, it increases in minutes. At this time, when its getting delay in calling create on the bean of one of these four tables, calling create on the beans of other tables returns instantly without any delay. Ultimately we have to restart the application server and then this works well again for around 3-4 days.
Here, we are using the jboss with it's default configuration for caching and passivation policies. The default passivation period is 10 mins, max pool size of container is 100, and min pool size is 10. Do we need to tune any of these parameters or something else?
Ankit
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic