PQ66463: NEW FUNCTION | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as unreproducible in next release. Error description New FunctionLocal fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V4.0.1 for z/OS and OS/390 * **************************************************************** * PROBLEM DESCRIPTION: APAR PQ66463 addresses various problems * * in WebSphere Application Server * * V4.0.1 for z/OS and OS/390. * **************************************************************** * RECOMMENDATION: * **************************************************************** The following problems are addressed in APAR PQ66463: (MD14270) OTS issues minor code C9C21808 in a server region because its thread level control block has been overlaid. Medium weight threads, which is the default for java threads, cause problems when they end because the TCB is reused. Since the TCB is reused our task level resource manager does not get control to free the BTCB and set STCBBCBA to zero. boss_thread_destructor does get control for medium weight threads and frees btcb_ras_trace_fp_object_ptr, calls cleanup routines which free things like btcb_otsp. When a second java thread runs on the reused TCB we think the areas pointed to by btcb_otsp and btcb_ras_trace_fp_object_ptr are still valid. In reality the areas have been reallocated to someone else and OTS issues minor code C9C21808 in a server region because its thread level control block has been overlaid. (MD14304) Tracing messages that include J2EEName (AMC) do not display correctly. Message inserts are corrupted. (MD14313) 'OS thread identity to runas enabled' property value 'SET' allows the J2EE server to access methods within J2EE applications. This property can be managed by checking and unchecking the field 'Enable Setting OS Thread Identity to RunAs Identity' in SM EUI. Message BBOU0590I, 'OS thread identity to runas enabled :' should display 'SET' or 'NOT SET' based on the value set to that property. (MD14331) WebSphere Application Server for z/OS gives default values for the queues used by the publish/subscribe APIs for JMS. The names supplied for these queues do not match those supplied by WebSphere AE. (MD14339) nullPointerException from WS390ContainerManager.java in method createHome can be received. The problem happens when EJB inheritance is used. The child EJB causes the Parent EJB BeanMetaData to get loaded before the createHome is done on the parent. (MD14388) In WS390ApplicationManager, the method buildClassPath currently reads past the application root, and jar files that are in subdirectories will NOT be found. (MD14430) Under stress runs, eventually a UTOKEN request will fail with message BBOU0736E due to a NSC token of zero being returned from a failed NSC token requst. The NSC token is used to build a bad UTOKEN, resulting in the error. (MD14436) ClassNotFoundException can occur after Server Region recycle due to the error of not all the ejb jar files being read during classloader initialization when running in Application Mode. (MD14472) If LOGSTREAM NAME is not defined during bootstrap, the current.env specifies LOGSTREAMNAME= with no value. When the address space is started, a default logstream name is generated with BBO. followed by the first part of the DAEMON_IPNAME. If the DAEMON_IPNAME value contains lower case letters, those are included in the logstream name. This is not valid because all letters in the logstream name must be upper case. ( PQ63576)In file bboslapd.conf file, there are include statements that includes the schema files. They are required only on z/OS R1.3 and earlier releases where RDBM or TDBM with SDBM is used. z/OS 1.4 or higher releases of z/OS no longer supports RDBM, and therefore the schema files are no longer shipped. The include statments should be removed from bboslapd.conf file.Problem conclusion Temporary fix Comments APAR PQ65206 provides the following problem resolution: (MD14270) Support has been modified to force java threads to be heavy weight threads by updating module bbolsys.cpp to set the environment variable JAVA_THREAD_MODEL to HEAVY. (MD14304) Support was been modified to correctly display tracing messages that include J2EEName. (MD14313) Support was modified to display the 'OS thread identity to runas enabled' property in the joblog Message BBOU0590I. (MD14331)The default queue names for the publish/subscribe APIs have been changed in WebSphere Application Server for z/OS to match those being used by WebSphere AE. (MD14339) Support has been modified to save the home returned from EJSContainer.LoadBeanMetaData method in a Hashtable with the J2EEName as the key to the home. Support will now save the home that is returned on the get to the Hashtable and return that value if it was found. (MD14388) Method buildClassPath has been modified to get the jar file path having the application directory as the root. (MD14430) Support has bee modified to initialize 2 previously uninitialized variables that could cause a problem if they contain data that appears valid. Support was also changed to return an error if an NSC token is not found, and to check that the NSC token is valid before using it to build a UTOKEN. (MD14436) Support has been modified to read all the ejb jar files with visibility mode in Application Mode. (MD14472) Support has been modified such that characters will be converted to upper case when copying them from the DAEMON_IPNAME value to build a default logstream name. APAR PQ66463 also resolves the issue reported by APAR PQ62669. APAR PQ62669 addresses the occurence of ABENDS0C1/ABEND0C1, ABENDS0C4/ABEND0C4, or ABENDS0C6/ABEND0C6 in LE or WebSphere for z/OS methods due to storage overlays occurring when a small LE stack size is specified. APAR PQ66463 also resolves the issue reported by APAR PQ63576. Support has been added to the "WebSphere for z/OS Customization" dialog panels to prompt the user as to whether their target system is running on z/OS v1.4 or later. If the user answered Y (yes), the include statements in bboslapd.conf are not needed and therefore not generated. Otherwise, the include statements will be generated. APAR PQ66463 is associated with SERVICE LEVEL W401400 of WebSphere Application Server V4.0.1 for z/OS and OS/390.
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: UQ70037 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 #: PQ66463
IBM Group: Software Group
Modified date: Oct 14, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.