  | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Tomcat - JSP/Servlet container | | Struts - A MVC web framework | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | JSP - A mailing list about Java Server Pages specification and reference | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | |
Struts & Hibernate
|
|
|
  | | | Regarding restricting number of instant for MDB | Regarding restricting number of instant for MDB 2004-08-27 - By SOURABH Srivastava
Back Changing max-beans-in-free-poo to 6 will degrade the performance. You change this to
max beans in pool = 100 initial = 30
If you feel there will be too many messages, then create 5-10 extra threads in the server and allocate those threads to JMS queue.
Thanks Sourabh
__ ____ ____ ____ ____ ____ ____
From: An interest list for Sun Java Center J2EE Pattern Catalog on behalf of Kamaraj, Pushparaj Sent: Mon 7/19/2004 3:03 AM To: J2EEPATTERNS-INTEREST@(protected) Subject: Regarding restricting number of instant for MDB
Hi, We are having Message driven bean and other session beans in the same container. The characteristics of MDB is whenever a message is added to the JMS queue it will be instantiated to serve the message. We are expecting there will be large number of messages coming to JMS queue. If the system start associating a MDB for each message then there will be many processes running in parallel, which will reduce the system performance. How to restrict the maximum number of active MDB in the system? And the configuration should not affect other session bean instants. If we restrict the maximum instant to 10, at the most there will be only 10 MDBs and other request will be waiting in the JMS queue.
We are using the following configuration to achieve the above requirement. Is that correct?
<message-driven-descriptor> <pool>
<max-beans-in-free-pool>6</max-beans-in-free-pool>
<initial-beans-in-free-pool>3</initial-beans-in-free-pool> </pool> </message-driven-descriptor>
Thanks, K.Pushparaj.
__ ____ ____ ____ ____ ____ ____ ____ ______ Confidential: This electronic message and all contents contain information from Syntel, Inc. which may be privileged, confidential or otherwise protected from disclosure. The information is intended to be for the addressee only. If you are not the addressee, any disclosure, copy, distribution or use of the contents of this message is prohibited. If you have received this electronic message in error, please notify the sender immediately and destroy the original message and all copies.
===================================================================Companion Site: http://www.corej2eepatterns.com J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
===================================================================Companion Site: http://www.corej2eepatterns.com J2EE BluePrints: http://java.sun.com/blueprints/corej2eepatterns List Archive: http://archives.java.sun.com/archives/j2eepatterns-interest.html Unsubscribing: email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
|
|
 |