Win a copy of Microservices Testing (Live Project) this week in the Spring forum!
  • 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
  • Tim Cooke
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Liutauras Vilda
  • Henry Wong
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Al Hobbs
  • Carey Brown
Bartenders:
  • Piet Souris
  • Mikalai Zaikin
  • Himai Minh

Default Behavior of default work manager while handling MDBs

 
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi All,

We are working on Weblogic 10.3.3 with EJB 2.1 and our application uses the default work manager with Fair Share Based Request Class . I have a couple of questions that I need help on

(1) Did read on the net that the maximum number of concurrent MDB's spawned is 16, how does Weblogic handle things internally when JMS requests are greater than 16, how are they taken up for processing?
In our application, each JMS request triggers an EOD process which is triggered for a country for EOD Account Interest Calculation.
We have some some strange behavior in our Production Box, on month end processing specifically when the load is high, requests get queued up and it does not follow a FIFO model, requests which come in late are processed earlier than the ones which are waiting to be executed - Why does this happen?

(2) If we configure a workmanager specifically to handle this, what is the thumb rule to get the min and max threads right?

Please let me know.
 
reply
    Bookmark Topic Watch Topic
  • New Topic