PQ78453: 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 PQ78453 addresses various defects * * in WebSphere Application Server V5.0 * * for z/OS. * **************************************************************** * RECOMMENDATION: * **************************************************************** APAR PQ78453 addresses the following defects in WebSphere Application Server V5.0 for z/OS: (MD17526) Updated WebSphere Client Development Kit for V5.1 for z/OS and OS/390 including Application Assembly Tool, Tivoli Performance Viewer, and Client Configuration tool. (MD17543) Customer can receive message: BBOO0223I Failure to obtain Utoken for Subject when using a j2c connection from an unprotected servlet using WebSphere Authorization. When coming from an unprotected servlet using WebSphere authorization, an unauthenticated identity with username "UNAUTHENTICATED" becomes the principal name for the invocation credential. This is a problem when trying to make a j2c connection becuase a utoken must get created. This is impossible with "UNAUTHENTICATED" since it's over the 8 character max. (MD17573) The WebSphere distributed version of java.security contains a provider that does not exist on z/OS. It should be removed. (MD17594) After creating a new Server with the administrative console and viewing the changed file, two serverindex.xml entries are shown, one from a different node, then the server was created on. While there was no real change to the serverindex.xml this is an issue that it appears to have updated files it should not have. (MD17596) Support is needed to enabled the transformer to rebuild the was.env and jvm.options when it finds a nodeagent that has the custom property recoveryNode set to true. (MD17659) When invoking the wsadmin.sh command in local mode the following message is issued, WASX7017E: Exception received while running file "jaclScript.jacl"; The root cause of the message is a java.lang.NullPointerException at com.ibm.ws.security.core.ContextManagerImpl.getServerCredential. When wsadmin.sh is invoked in local mode it should not attempt to obtain a Server Credential. (MD17681) When started out-of-place, the control region attempts to bind to the SSL port which it usually binds to, but since it is not running on the system where it is configured, that port may already be in use. WebSphere has documented the restriction that the SSL port must be unique across the sysplex in order to facilitate restarting out of place. However, this may not be possible or desirable in some installations. (MD17683) Incorrect long error messages and cursor position for JMS Server port parameters in Customization Dialog. On panel BBOWPJ32 of the customization dialog (Server Customization (2 of 2), under Configure Integral JMS Provider, leave the third field empty and press enter. The cursor jumps to the second field (Stat Interval Time (secs)), which does have an entry in it, and displays a correct short error message. Pressing F1 displays the long error message: "The field definition 'ASJQADDP' is missing in the panel )BODY section. When the field definition is missing, the cursor position is unpredictable." The same error message and cursor jump also takes place when only the fourth or fifth fields are empty, but with the field definitions of ASJDADDP and IJPJSSP, respectively in the long error message. If the first or second fields are left blank, correct long error messages of "Enter required field at the cursor position" are displayed. The reason why the long error message was displayed is because the VER command is not verifying a field variable. To fix this, the VER command needs to be changed to verify on variables A, B and C instead of ASJQADDP, ASJDADDP and IJPJSSP respectively. (MD17687) wsadmin times out with a java.io.InterruptedIOException when the specified userid does not exist. Bad UserID on WSADMIN causes CORBA::NO_PERMISSION exception in JNI/C++ code. Exception is not caught, and client does not know until java.io.InterruptedIOException on time out. (MD17696) Double delete of GIOP_Message object. Giop message is put into the orbr before call to process_inbound_request. If a oneway to the daemon, process_inbound_request returns without setting the pointer to the giop message in the orbr to zero. The giop message will be deleted by the caller of process_inbound_request and again by the orbr destructor.Problem conclusion APAR PQ78453 fixes various defects in WebSphere Application Server V5.0 for z/OS. (MD17526) Updated WebSphere Client Development Kit for V5.1 for z/OS and OS/390 including Application Assembly Tool, Tivoli Performance Viewer, and Client Configuration tool. (MD17543) Code was modified to use the SAF Unauthenticated identity instead of "UNAUTHENTICATED." This identity is set through the administrative console. The default is WSGUEST. (MD17573) The PKCS11 provider was removed from java.security (MD17594) The code to create the server was modified to not perform a save action on a document that was not updated. (MD17596) The transformer was limited to only transform on its local node. Now the transformer in certain cases needs to transform all the servers it has in its config tree. This support is required for peer restart and recovery using a non-shared HFS. (MD17659) When wsadmin.sh is invoked in the local, -conntype none, mode it will no longer attempt to obtain a Serve Credential. (MD17681) When staring a server out-of-place, if the SSL port for which the server is configured is not available, another available port will be used, and message BBOO0245W will be issued. This port is registered with the daemon so that other servers in the configuration can find it. (MD17683) Panel file bbowpj32.plib will be updated to verify for A, B and C instead of ASJQADDP, ASJDADDP and IJPJSSP respectively. (MD17687) Support has been modified to not throw exception in JNI/C++ for the SAF error. Propogate the bad RC back to java, and let the java layer issue the exception. (MD17696) Updated call to process_inbound_request to pass giop message as a parameter instead of in the orb request object. APAR PQ78453 is associated with SERVICE LEVEL W501000 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: UQ80302 Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PQ78453.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 #: PQ78453
IBM Group: Software Group
Modified date: Oct 3, 2003
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.