PQ56454: THIS APAR ADDRESSES DEFECTS IN WEBSPHERE APPLICATION SERVER V4.0.1 FOR Z/OS AND OS/390. | |||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description This APAR addresses defects in WebSphere Application Server V4.0.1 for z/OS and OS/390.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V4.0.1 for z/OS and OS/390. * **************************************************************** * PROBLEM DESCRIPTION: APAR PQ56454 addresses various problems * * in WebSphere Application Server V4.0.1 * * for z/OS and OS/390. * **************************************************************** * RECOMMENDATION: * **************************************************************** APAR PQ56454 addresses the following problems in WebSphere Application Server V4.0.1 for z/OS and OS/390: (MD12666) Currently the System Management User Interface (SM EUI) does not allow J2EE Ejb References to be resolved outside the current WAS/390 installation. In the WAS/390 System Management Administration Application (SM EUI) Resource and Reference Resolution dialog a user has to resolve Ejb References when installing a J2EE Application. So far these references can only be resolved to beans that have previously been installed on the same WAS/390 image. This is enforced by the SM EUI as the target for a reference has to be selected from a combobox which on selection translates the target bean to it's assigned JNDI name. It is not possible to manually enter that JNDI name. Without this capability it is not possible for Ejb's installed on WAS/390 to communicate with beans installed on other systems. (MD12771) The storage for Supported Securities, that is anchored to a Session is not freed up when we clean up the security session. The storage size that is being leaked is at least 1032 bytes per request in the control region. The frame count for the control region on sdsf increases over time, and eventually gets an out of storage abendS878/abend878.Problem conclusion APAR PQ56454 provides the following problem resolution: (MD12666) The System Management User Interface (SM EUI) has been modified to allow J2EE Ejb References to be resolved outside the current WAS/390 installation. (MD12771) When a call to securitySessionCleanup is made, we check the status of the SupportedSecurity (sessSecAreaPtr->secOfferedPtr). If is not NULL, then we free up that storage. ________________________________________________________________ The following publication was revised as a result of APAR PQ56454: ________________________________________________________________ WebSphere Application Server V4.0.1 for z/OS and OS/390 System Management Scripting API SA22-7839-02 ________________________________________________________________ This APAR requires changes to 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/ ________________________________________________________________ Chapter 4, pg. 75 (new section) Example output file The output file may look like this: acceptassertedid.1 Y administratorname.1 CBADMIN allowkerberos.1 Y allownonauthenticatedclients.1 Y allowserverregiongarbagecollection.1 Y allowssl.1 N allowsslclientcerts.1 Y allowuseridpasswd.1 Y conversationname.1 API Functiontest dcekeytabfile.1 dcequalityofprotection.1 No_Protection debuggerallowed.1 N enablerunasidentity.1 Y garbagecollectioninterval.1 50000 identityofthecontrolregion.1 IBMUSER identityoftheserverregion.1 IBMUSER isolationpolicy.1 Multiple_Transactions_Per_Server_Region j2eeserverdescription.1 APIFCT Description of changed server j2eeservername.1 J2EESRV localidentity.1 CBGUEST logstreamname.1 olthostname.1 oltport.1 7000 procname.1 BBOASR1 productionserver.1 Y remoteidentity.1 CBGUEST replicationpolicy.1 One_Per_Server sendassertedid.1 Y serverregionjvmname.1 serverregionrequiresjvm.1 N serverregionstacksize.1 0 smfintervallength.1 100 smfwrcontaineractivity.1 Y smfwrcontainerinterval.1 Y smfwrserveractivity.1 Y smfwrserverinterval.1 Y sslracfkeyring.1 CBKeyring sslv2timeout.1 100 sslv3timeout.1 600 sysplexname.1 PLEX1 transactionfactory.1 N usedce.1 N useibmconfidential.1 Y useridpassticket.1 N security.1 ISM_UserID_Password environment.1 CLASSPATH = 'Demo:test1' PATH = 'test2' DEFAULT_CLIENT_XML_PATH = '/sm/xml' status 0 message.1 OK count 1 ________________________________________________________________ Chapter 4, pg. 76 (changed section) Values of default xml file The table below includes all of the attributes that are known for this server action. The required ones must be defined in the default xml file and can be overwritten by the XMLGEN ("Chapter 5. XMLGEN" on page 195), script. The default xml file is listed in section "inputchangej2eeserver.xml" on page 230. ________________________________________________________________ Chapter 4, pg. 76 (changed section) ---------------------------------------------------------------- Parameter name |Values |Required ---------------------------------------------------------------- conversationname |Name of the conversation | x ---------------------------------------------------------------- j2eeservername |Name of the J2EE server | x ---------------------------------------------------------------- j2eeserverdescription |Description of the J2EE server| ---------------------------------------------------------------- ... |... |... ---------------------------------------------------------------- oltport |Character value between 1 | x |and 65535 | ---------------------------------------------------------------- ... |... |... ---------------------------------------------------------------- ________________________________________________________________ Chapter 4, pg. 78 (changed section) Example script Here is an example script: /* REXX function */ call syscalls 'ON' signal on error say "FCT Test #changej2eeserver" name. = 0 name.1 = "conversationname" name.2 = "j2eeservername" name.3 = "j2eeserverdescription" name.4 = "identityofthecontrolregion" name.5 = "identityoftheserverregion" name.6 = "serverregionstacksize" name.7 = "productionserver" name.8 = "debuggerallowed" name.9 = "olthostname" name.10 = "oltport" name.11 = "isolationpolicy" name.12 = "replicationpolicy" name.13 = "serverregionrequiresjvm" name.14 = "serverregionjvmname" name.15 = "localidentity" name.16 = "remoteidentity" name.17 = "transactionfactory" name.18 = "allowserverregiongarbagecollection" name.19 = "garbagecollectioninterval" name.20 = "logstreamname" name.21 = "procname" name.22 = "enablerunasidentity" name.23 = "allownonauthenticatedclients" name.24 = "allowuseridpasswd" name.25 = "useridpassticket" name.26 = "usedce" name.27 = "dcequalityofprotection" name.28 = "dcekeytabfile" name.29 = "allowssl" name.30 = "allowsslclientcerts" name.31 = "allowkerberos" name.32 = "acceptassertedid" name.33 = "sendassertedid" name.34 = "useibmconfidential" name.35 = "sslracfkeyring" name.36 = "sslv2timeout" name.37 = "sslv3timeout" name.38 = "security" name.39 = "smfwrserveractivity" name.40 = "smfwrcontaineractivity" name.41 = "smfwrserverinterval" name.42 = "smfwrcontainerinterval" name.43 = "smfintervallength" name.44 = "environment" val. = 0 val.1 = "API Functiontest" val.2 = "J2EESRV" val.3 = "APIFCT Description of changed server" val.4 = "IBMUSER" val.5 = "IBMUSER" val.6 = "0" val.7 = "Y" val.8 = "N" val.9 = "" val.10 = "7000" val.11 = "Multiple_Transactions_Per_Server_Region" val.12 = "One_Per_Server" val.13 = "N" val.14 = "" val.15 = "CBGUEST" val.16 = "CBGUEST" val.17 = "N" val.18 = "Y" val.19 = "50000" val.20 = "" val.21 = "BBOASR1" val.22 = "Y" val.23 = "Y" val.24 = "Y" val.25 = "N" val.26 = "N" val.27 = "No_Protection" val.28 = "" val.29 = "N" val.30 = "Y" val.31 = "Y" val.32 = "Y" val.33 = "Y" val.34 = "Y" val.35 = "CBKeyring" val.36 = "100" val.37 = "600" val.38 = "ISM_UserID_Password" val.39 = "Y" val.40 = "Y" val.41 = "Y" val.42 = "Y" val.43 = "100" val.44 = "CLASSPATH='Demo:test1' PATH='test2' DEFAULT_CLIENT_XML_PATH='/sm/xml'" rc = 4 i = 1 /* Generate XML Input */ do while(name.i <> '0') rc = XMLGEN("tempin" name.i val.i) if (rc == 4) then do say "FCT Test #changej2eeserver failed while XMLGEN" exit end i = i+1 end; /* Call the function: changej2eeserver */ rc = CB390CFG("-action 'changej2eeserver' -xmlinput 'inputchangej2eeserver.xml' -input 'tempin' -output 'changej2eeserver'") if (rc == 4) then do say "FCT Test #changej2eeserver failed" exit end /* Parse the result */ rc = XMLPARSE("changej2eeserver" "ALL") if (rc == 4) then do say "FCT Test #changej2eeserver failed while XMLPARSE" exit end say "FCT Test #changej2eeserver completed" return 0 exit error: say "Error in FCT Test #changej2eeserver" rc "at line" sigl say sourceline(sigl) exit ________________________________________________________________ Chapter 4, pg. 81 (new section) Example output file The output file may look like this: acceptassertedid.1 Y administratorname.1 CBADMIN allowkerberos.1 Y allownonauthenticatedclients.1 Y allowserverregiongarbagecollection.1 Y allowssl.1 N allowsslclientcerts.1 Y allowuseridpasswd.1 Y conversationname.1 API Functiontest dcekeytabfile.1 dcequalityofprotection.1 No_Protection debuggerallowed.1 N enablerunasidentity.1 Y garbagecollectioninterval.1 50000 identityofthecontrolregion.1 IBMUSER identityoftheserverregion.1 IBMUSER isolationpolicy.1 Multiple_Transactions_Per_Server_Region j2eeserverdescription.1 APIFCT Description of changed server j2eeservername.1 J2EESRV localidentity.1 CBGUEST logstreamname.1 olthostname.1 oltport.1 7000 procname.1 BBOASR1 productionserver.1 Y remoteidentity.1 CBGUEST replicationpolicy.1 One_Per_Server sendassertedid.1 Y serverregionjvmname.1 serverregionrequiresjvm.1 N serverregionstacksize.1 0 smfintervallength.1 100 smfwrcontaineractivity.1 Y smfwrcontainerinterval.1 Y smfwrserveractivity.1 Y smfwrserverinterval.1 Y sslracfkeyring.1 CBKeyring sslv2timeout.1 100 sslv3timeout.1 600 sysplexname.1 PLEX1 transactionfactory.1 N usedce.1 N useibmconfidential.1 Y useridpassticket.1 N security.1 ISM_UserID_Password environment.1 CLASSPATH = 'Demo:test1' PATH = 'test2' DEFAULT_CLIENT_XML_PATH = '/sm/xml' status 0 message.1 OK count 1 ________________________________________________________________ APAR PQ56454 is associated with SERVICE LEVEL W401013 of WebSphere Application Server V4.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 #: PQ56454
IBM Group: Software Group
Modified date: Feb 2, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.