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?
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.