PQ75363: THIS APAR ADDRESSES DEFECTS IN WEBSPHERE APPLICATION SERVER V5.0 FOR Z/OS. | |||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description This APAR addresses defects in WebSphere Application Server V5.0 for z/OS.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: APAR PQ75363 addresses various defects * * in WebSphere Application Server V5.0 * * for z/OS. * **************************************************************** * RECOMMENDATION: * **************************************************************** APAR PQ75363 addresses the following defects in WebSphere Application Server V5.0 for z/OS: (MD17199) The shell scripts bbowc2ns.sh and bbodc2ns.sh will not work after addnode. Running bbowc2ns or bbodc2ns after addnode will change the symbolic links for all the servers to point to the Deployment Manager's config tree, which is wrong. Customers will see the following error if they run bbowc2ns.sh after addnode: com.ibm.ws.management.util.zos.TransformationError: Invalid path build from key: /WebSphere/V5R0M0/AppServer/config/cells/SY1/nodes at com.ibm.ws.management.util.zos.gate.GenKeyFactory. createSubKeys(GenKeyFactory.java:102) at com.ibm.ws.management.util.zos.gate.RepositoryImpl. fullTransform(RepositoryImpl.java:463) at com.ibm.ws.management.util.zos.Config2Native. transformServer(Config2Native.java:180) at com.ibm.ws.management.util.zos.Config2Native. main(Config2Native.java:493) BBOJ0058I Transformer Looking: /WebSphere/V5R0M0/AppServer/ config/cells/SY1/variables.xml BBOJ0058I Transformer Looking: /WebSphere/V5R0M0/AppServer/ config/cells/SY1/nodes//variables.xml BBOJ0053I Transformer is writing to: /WebSphere/V5R0M0/Daemon/ config/cells/SY1/SY1/BBODMNB/was.env BBOJ0056I Transformer Processing Complete. (MD17205.1) Support is needed for support multiple base server node configurations on the same system, where each base server node is configured with the same node host name for its daemon IP name. Since there is no workload distribution for a base server (i.e. it is not clusterable) there is no reason to require the customer to specify a unique daemon IP name for each base server node that gets configured on a system. In the current implementation, as was done in v4, the daemon IP name is always registered with WLM (IWMDNREG in bbocsess.cpp). This should no longer be done for base server nodes. A new WASEnvironment variable will be added: daemon_wlmable=0 // means do not register daemon with wlm daemon_wlmable=1 is the default base server configuration will add following variable to cell-level variables.xml: name='WAS_DAEMON_ONLY_daemon_wlmable' value='false' (MD17209) In the Customization dialog generated instructions, BBOCCINS, for the Deployment Manager, the RACF jobs BBOCBRAJ and BBOCBRAK are named incorrectly. The correct job names should be BBODBRAJ and BBODBRAK respectively. (MD17213) Security Component not initialized message occurs when starting WAS 5.0 ND with security enabled. The following message is displayed on the operator console: SECJ0244I: Security service failed to start successfull The message results becuase code was added to load 3 Security Providers: IBMJCE, JSSEProvider, and IBMCertPathProvider. The problem is that the code is looking for IBMJSSEProvider, not JSSEProvider. (MD17217) Using the WebSphere V5.0 for z/OS administrative console, if you navigate to: Application Servers> serverx> Web Container> Advanced Settings. The value "NONE" is not in the select list of the networkQoS field. It needs to be added to the list. (17224) When an RRS resource votes to rollback during a call to ATRADCT and there are no XA resources enlisted in the global transaction, the internal state of the transaction may not be updated correctly. In this case, after the call to ATRADCT, the transaction is rolled back and forgotten. However, the transaction timer continues to run and when the transaction times out, the timer attempts to clean up the already-completed transaction, which results in an ABENDS0C4/ABEND0C4, reason code 0x00000010 in BBOBOA. (MD17225) When using the administrative console, with Japanese language enabled, the description text for the default EjbNameSpaceBinding location and and the base message for EjbNameSpaceBinding location appear concatenated as one message. Also, messages for Node agent and its functions refer to 'Deploy Manager' which is translated to Japansese and should not be translated for US English. (MD17227) The transformer's return code is always 0, and there was no way to get the error infoirmation or logs when using the script. (MD17231) During processing of a swam login, the swamLoginModule does not properly save the UserID. Since the userID is not saved, login processing goes down an improper code path which causes the Null pointer exception. (MD17261) When using JES3 in configuring the integral JMS provider with the customization dialog (on System Locations (1 of 2), set the 'Jes3 (Y/N)' field to Y), there is a typo on line 42 after the instructions are generated: //JES3ALOC EXEC PGM=IEFBR14,REION=1M PROBLEM CONCLUSION: (MD17261) Dialog skeleton BBOJPAGR will be updated to correct the typo REION to REGION. (MD17263) Using the administrative console if you navigate to: Environment > Manage WebSphere Variables. When the cell name contains "cell", a servletException will occur in contextScopeTile.jsp due to String index out of range: -3. If one uses the literal 'cell' in naming the cell, then the JSP contextScoptTile.jsp which is used to determine the scope fails to work. This is because the breaking up of the string /cells/names/nodes/names... cannot be done properly. (MD17267) WebContainer interval SMF records are not updated with the correct HttpSession interval data or the number or Servlets which have been loaded by a Web Application. The problem results becuase a call to the SmfWebContainerDataCollectorIntervalManager's flush method is never made. (MD17271) Console output for the following shell scripts is unreadable because the text is in ascii: launchClient.sh; GenPluginCfg.sh; JspBatchCompiler.sh; startManager.sh; startNode.sh; startServer.sh (MD17276) Trace buffer location does not initialize appropriately to what was specified in the ras_trace_outputLocation. (MD17302) While using local OS authentication to process a runas request, the following error occurs: "BBOS0107E Credential handling function RunAsSetSpecLatentCred failed." The SAF credential has "timed out" invalidating the credential. (M17349) Hang occurs when attempting to connect to administrative console for ND when security is enabled. Controller process returns gsk_socket_init 403 error. The problem is that the Dialog job attempts to generate the a certificate for the Deployment Manager with the same Distinguished Name as the one on the Application Server. There is subsequently no server certificate available in the keyring for the Deployment Manager. Additionally, the server certificates were set up in such a way that additional servers were difficult to set up. (M17363) In the webcontainer's Advanced Settings panel of the administrative console, the Transaction Class Mapping field will not take a fully qualified name. This error can be reproduced as follows: 1) In the administrative console, navigate to Servers > Application Servers > <server> > Web Container > Advanced Settings 2) In the Advanced Settings panel, put in a fully qualified path/file name such as /wasv5config/t5was/AppServer/MyTrMapFile.txt in the "Transaction Class Mapping" entry field. The administrative console will display the following error msg: Transaction Class Mapping is not a valid entry. (PQ74029) If a large number of concurrent connection requests are received by the server, they can be rejected with ECONNREFUSED whatever if the backlog of unprocessed connection requests exceeds the defined limit which is fixed at 10. (WS16994) WebSphere V5.0 for z/OS needs to provide the same PMI Orb Metrics vailable in WebSphere V4.0.1 for OS/390 and z/OS.Problem conclusion APAR PQ75363 fixes various defects in WebSphere Application Server V5.0 for z/OS. (MD17199) Dialog skeletons bbowc2ns and bbodc2ns will be updated to have the correct syntax for calling Config2Native. The resulting shell scripts will not produce any error if they are run after addnode. ()MD17205.1) Module bbocsess.cpp was modified to skip the IWMDNREG call when daemon_wlmable=0 is set in WASEnvironment (i.e. from was.env). Also, dialog skeleton BBOWVAA1 will be updated to add: name='WAS_DAEMON_ONLY_daemon_wlmable' value='false'. (MD17209) Dialog skeleton BBOCCINS will be updated to have the correct job names. (MD17213) Support was modified to load IBMJSSEProvider. (MD17217) The WebSphere V5.0 for z/OS administrative console has been "NONE" has been added to the select list of the networkQoS field on the Webcontainer Advanced Settings view. (MD17224) Support was added to properly clean up global transactions when RRS votes to rollback the transaction, and there are no XA resources enlisted. (MD17225) Support was modified to split the the description text for the default EjbNameSpaceBinding location and and the base message for EjbNameSpaceBinding location onto separate lines as expected and pick up the corrected translation with 'Deployment Manager' remaining in English. (MD17227) Support has been modified so that the Transformer now returns 0 is sucessful, and 8 if error. Also the transformer if passed a -trace option writes a file to the $WAS_HOME/logs/wsc2n.sh. (MD17231) Swam login processing will be changed to properly save the UserID being logged on. (MD17261) Dialog skeleton BBOJPAGR was updated to correct the typo REION to REGION. (MD17263) The JSP /secure/tiles/contextScopeTile.jsp was changed to correct this problem. The criteria which was used to parse the string for path was changed. (MD17267) The Web Container code has been changed to call SmfWebContainerDataCollectorIntervalManager's flush method at the end of each dispatch. (MD17271) The environment variable "CONSOLE_ENCODING" which is defined in setupCmdLine.sh should be one of the JVM args within each of the shell scripts: launchClient.sh; GenPluginCfg.sh; JspBatchCompiler.sh; startManager.sh; startNode.sh; startServer.sh In a typical English WAS system "CONSOLE_ENCODING" has the following value: "-Dws.input.encoding=cp1047 -Dws.output.encoding=cp1047" (MD17276) Initialization of trace buffer output location was corrected to reside to what was specified for ras_trace_outputLocation. (MD17302)The CredentialCache code had been modified to revalidat the SAF credential when the cache entry is invalid. (M17349) Modified the BBODBRAC member of the security Dialog to generate an ND certificate with a unique Distinguished Name. Modify the BBOWBRAC job to do the add Cluster Name to the Distinguished Name of the server definition. (M17349) The validation rule associated with the validation of the the Transaction Class Mapping entry field was modified to allow fully qualified names. (PQ74029) Four environment variables have been added added to define number of backlog connections which can occur before a connection refused condition reults. Documentation for these new envirionment varibles follows: A change to the WebSphere Application Server Version 5 InfoCenter will be available in the next refresh of the documentation. To access the latest online documentation, go to the product library page at: www.ibm.com/software/webservers/appserv/zos_os390/library/ The change will read as follows: protocol_http_backlog=n An integer value that indicates the maximum queue length for pending connections that use HTTP. You may set the maximum value up to 2147483647, but the specification of the SOMAXCONN statement in the TCP/IP profile may result in limitations to this. The default is 10. Example: protocol_http_backlog=25 protocol_https_backlog=n An integer value that indicates the maximum queue length for pending connections that use HTTPS. You may set the maximum value up to 2147483647, but the specification of the SOMAXCONN statement in the TCP/IP profile may result in limitations to this. The default is 10. Example: protocol_https_backlog=25 protocol_iiop_backlog=n An integer value that indicates the maximum queue length for pending connections that use IIOP. You may set the maximum value up to 2147483647, but the specification of the SOMAXCONN statement in the TCP/IP profile may result in limitations to this. The default is 10. Example: protocol_iiop_backlog=25 protocol_iiop_backlog_ssl=n An integer value that indicates the maximum queue length for pending connections that use IIOP SSL. You may set the maximum value up to 2147483647, but the specification of the SOMAXCONN statement in the TCP/IP profile may result in limitations to this. The default is 10. Example: protocol_iiop_backlog_ssl=25 (WS16994) Support for PMI Orb Metrics was provided. APAR PQ75363 is associated with SERVICE LEVEL W500101 of WebSphere Application Server V5.0 for z/OS.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
Publications Referenced
|
Document Information |
Current web document: swg1PQ75363.html
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ75363
IBM Group: Software Group
Modified date: Jul 3, 2003
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.