Even a chimp can write code

Friday, July 16, 2004

WebSphere EJB pool morass

Apparently the only way one can configure the pool size for EJBs within WebSphere 4.0.x and 5.0.x is by specifying a system property for the container.  Neither the desployment descriptors, nor the Application Assembly Tool, nor the WAS Admin Console allow you to easily set the min and max pool sizes.
Instead, you must set a JVM argument com.ibm.websphere.ejbcontainer.poolSize, which applies to all manner of creatures -- message driven, stateless and entity beans. Wonderful! The property value for any serious application looks cryptic, if anything. Read their documentation for details.  When not specified, the values 50 and 500 are used.
They might as well tie our hands behind our backs.

Email this | Bookmark this


  • May I suggest a better alternative ??

    By Anonymous Anonymous, at July 20, 2004 at 9:14 AM  

  • Try reading the manuals again, pal. You can be as specific (to a specific bean) or generic (setting defaults for a specific bean type) as you want.

    By Anonymous Anonymous, at August 10, 2004 at 1:39 PM  

  • There is something even worse with the WAS 5.0 pools, at least for EJBs. The max pool size does not limit the number of EJB instances ever created. It just keeps around at most that many instances. So if you set the pool to 50, and you get blasted with 1000 requests. It will create 950 extra beans that will just be discarded. Hopefully your ejbCreate() method isn't too expensive.

    If you think this is crap, please open a PMR and complain as we have.

    By Anonymous Anonymous, at November 15, 2004 at 6:19 AM  

Post a Comment | Home | Inference: my personal blog