PQ74916: CHANGE SMEUI, SMAPI DEFAULTS - "PRODUCTION J2EE SERVER" AND "ISOLATION POLICY - MULTIPLE TRANSACTIONS PER SERVER REGION" | |||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Hang problem can occur when an application server does not have enough threads in the control and/or server regions. This can be due to the thread pool and transaction behavior characteristics that is setup for the server. Currently, when creating a new J2EE or non-J2EE server using the SMEUI or SMAPI interfaces, the defaults are the following: Production J2EE Server: NOT checked Isolation Policy: One transaction per server region With these defaults, the J2EE server will be initialized with the following characteristics: Production server: NO => Control region thread pool size: 3 - Treated as "Test" server - "Debugger Allowed" is checked as default. Isolation Policy: "One transaction per server" => Server region thread pool size: 1 This apar will change the SMEUI and SMAPI interfaces with the following as defaults when creating a new server: (Note: this was an option, but not as default) Production J2EE server: YES <= Production server is checked Isolation Policy: "Multiple transaction per server" Please note, in the past, when creating a new J2EE or non-J2EE server, these were options that were available but had to be manually selected With these settings, the following is set for the new server: Production server: YES => Control region thread pool size: 25 Isolation Policy: "Multiple transaction per server" => Server region thread pool size: 3 This will not eliminate the prior options of "non-Production" and "One transaction per server region" and can still be selected by the end-user manually when creating a new J2EE or non-J2EE server. The "Debugger Allowed" will not default and must now be checked when needed.Local fix When creating a new J2EE or non-J2EE server using the SMEUI or SMAPI interfaces, user must manually select the following options: Production J2EE Server: Must be checked (Yes) Isolation Policy: Multiple transaction per serverProblem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * version 4.0.1 for z/OS and OS/390 * **************************************************************** * PROBLEM DESCRIPTION: Hang problem can occur when an applicat * * server does not have enough threads in * * control and/or server regions. This ca * * due to the thread pool and transaction * * behavior characteristics that are setup * * the server. * **************************************************************** * RECOMMENDATION: * **************************************************************** Hang problem can occur when an application server does not have enough threads in the control and/or server regions. This can happen with J2EE servers and non-J2EE servers. One possible manifestation is as follows: (1) The HTTP server sends a servlet to the J2EE server (Webcontainer), and waits for a response, however (2) The J2EE server does not show the servlet active. (3) There is no abend but you may see minor code of C9C2110F. This hang can be due to the thread pool and transaction behavior characteristics that are setup for the server. Currently, when creating a new J2EE or non-J2EE server using the SM EUI or SMAPI interfaces, the defaults are as follows: Production J2EE Server: NOT checked Isolation Policy: One transaction per server region With these defaults, the J2EE server will be initialized with the following thread pool sizes: Production server: NO => Control region thread pool size: 3 - Treated as "Test" server - "Debugger Allowed" is checked as default. Isolation Policy: "One transaction per server" => Server region thread pool size: 1 The net effect of using theses default values when creating a new server is that the server may not have enough threads available to process all requests in a production environment.Problem conclusion This apar changes the SM EUI and SMAPI interfaces with the following as defaults when creating a new server: Production J2EE server: YES <= Production server is checked Isolation Policy: "Multiple transaction per server" Debugger allowed: NO <= Debugger Allowed is unchecked Please note, in the past, when creating a new J2EE or non-J2EE server, these were options that were available but had to be manually selected. With these settings, the following thread pool sizes will be in effect for new servers (when the default values are not overridden): Production server: YES => Control region thread pool size: 25 Isolation Policy: "Multiple transaction per server" => Server region thread pool size: 3 or more These new defaults will not eliminate the prior options of "non-Production" and "One transaction per server region," which can still be selected by the end-user manually when creating a new J2EE or non-J2EE server. The "Debugger Allowed" option will not default to YES (checked) as it did before, and must now be checked when needed. APAR PQ74916 requires a change to the WebSphere V4.0.1 for z/OS and OS/390 documentation. NOTE: Periodically, we refresh the documentation on our Web site, so the changes might have been made before you read this text. To access the latest on-line documentation, go to the product library page at: http://www.ibm.com/software/webservers/appserv/zos_os390/library WebSphere Application Server V4.0.1 for z/OS and OS/390 System Management User Interface (SA22-7838-05) will be changed as follows: In chapter 4, Administration Objects, in the section headed J2EE Server, under Properties,(1) Under Production J2EE Server, the second bullet should be changed to, "Default value is that this is a production server. (2) Under Debugger allowed, the second bullet should be changed to, "Default value is that a debugger is not allowed." (3) Under Isolation policy, the third bullet should be changed to, "Default value is Multiple transactions per server region." In chapter 4, Administration Objects, in the section headed Server, under Properties,(1) Under Production Server, the second bullet should be changed to, "Default value is that this is a production server. (2) Under Debugger allowed, the second bullet should be changed to, "Default value is that a debugger is not allowed." (3) Under Isolation policy, the third bullet should be changed to, "Default value is Multiple transactions per server region." WebSphere Application Server V4.0.1 for z/OS and OS/390 System Management Scripting API (SA22-7839-06) will be changed as follows: In Chapter 10, under the heading inputcreateserver.xml, the default values for productionserver, debuggerallowed, and isolationpolicy have been changed as follows: productionserver = 'Y' debuggerallowed = 'N' isolationpolicy = 'Multiple_Transactions_Per_Server_Region' In Chapter 10, under the heading inputcreatej2eeserver.xml, the default values for productionserver, debuggerallowed, and isolationpolicy have been changed as follows: productionserver = 'Y' debuggerallowed = 'N' isolationpolicy = 'Multiple_Transactions_Per_Server_Region' APAR PQ74916 is associated with SERVICE LEVEL W401508 of WebSphere Application Server version 4.0.1 for z/OS and OS/390.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 401
Software edition:
Reference #: PQ74916
IBM Group: Software Group
Modified date: Jul 3, 2003
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.