PQ68569: THERE IS A LIMIT ON THE NUMBER OF CLONES STARTING AT ONE TIME. INITIALLY IT IS HARD CODED TO 5 THREADS (5 CLONES). | |||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description When starting a server group of more than 5 clones you will notice that only 5 clones start at one time. After the five clones are started then the next five will start together until all the clones are started.Local fix Problem summary **************************************************************** * USERS AFFECTED: All WebSphere Application Server AE * * versions 4.0.x. This fix exposes new * * functional. * **************************************************************** * PROBLEM DESCRIPTION: When starting a server group of more * * than 5 clones, only 5 clones start at * * one time. After the five clones are * * started then the next five will start * * together until all the clones are * * started. * **************************************************************** * RECOMMENDATION: * **************************************************************** Internally, there is an Asynchronous Task Engine that dispatches worker threads from a threadpool to perform the tasks such as initiate "start" on a application server. The size of this threadpool is hardcoded to 5, which is the reason why customer reports only 5 clones can start at one time because there is a limit of 5 Asynchronous Tasks performed at one time.Problem conclusion This fix exposes the threadpool to user and allows tweaking of the size of threadpool to cater more to the system. User would configure this threadpool size by modifying the following new system property in the admin.config file. com.ibm.ejs.sm.adminServer.asyncTaskThreadPoolSize = <int value> The <int value> is at minimum 5. If value set is less than 5, the default value of 5 will be used by WebSphere. The trade off for increasing this thread pool size is cost in memory resources. In testing on a desktop workstation, memory depletion or JVM crashes were observed when the default thread pool size was set to 10. User should be conservative in deciding the most optimal configuration for their system. The default size of this thread pool is well-tested, most users should find the current setting suitable for their environment.Temporary fix provided customer with test fix, waiting for updateComments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
SRLS
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ68569
IBM Group: Software Group
Modified date: Dec 23, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.