• 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

Server Listening mode problem

 
Ranch Hand
Posts: 42
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello All,
Does the JMS server use the threads from the pre-defined Thread pool for passing the messages to the listeners?
Our application has a number of components that write messages to the JMS queue. The JMS Server passes the messages to a listener which either writes the messages to a file or into the database. As the number of messages increase we find that the HTTP server(running on the same server as the application server) stops accepting any more requests. Is it because the threads from the Thread pool are busy with the JMS server?

Thanks,
Ashutosh
 
Ranch Hand
Posts: 2713
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
JMS uses a separate thread pool from other components in WebLogic. This can be configured by going to Server->ServerName->Services->JMS. The default value is 15, which is sufficient for most applications.
Tuning guidelines say that you should have at least 1 thread for each JMS Server, 1 thread for each MDB instance or Message Listener, and 1 thread for each Message Bridge.
 
reply
    Bookmark Topic Watch Topic
  • New Topic