PQ98073: SHIP INTERNAL DEFECT FIXES FOR SERVICE LEVEL W502020. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Ship internal defect fixes for Service Level W502020.Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: APAR PQ98073 addresses the following * * defect in WebSphere Application Server * * V5.0 for z/OS: * * * * (MD19377) A misleading message * * +BBOJ0077I * * security.use.localos.authorization * * = true is issued during server startup * * regardless of the configuration. * * * * (MD19726) When configuring the * * Performance Monitoring Infrastructure * * (PMI) service using the Administrative * * Console, the Reset button does not * * restore the panel to the current local * * configuration values. * * * * (MD20284) LogFullException occurs due * * to unnecessarily logging repeated * * XAResource entries in the transaction * * log, corresponding to JMS resources * * over the lifetime of the server. * * * * (MD20408) There is no check to make * * sure the user enters a valid IP address * * with fields between 0 and 255 in * * Servers->Application Servers-> * * <server name>->WebContainer-> * * HTTPTransports->host in the * * administrative console. * * * * (MD20576) An ABENDS0C4/ABEND0C4 in * * module BBOTOTS causes the controller to * * terminate. * **************************************************************** * RECOMMENDATION: * **************************************************************** APAR PQ98073 addresses the following defect in WebSphere Application Server V5.0 for z/OS: (MD19377) In the server log the following message will be displayed regardless of the configuration: +BBOJ0077I security.use.localos.authorization = true This is misleading and can cause the customer to believe that something is wrong. (MD19726) The PMI is configured by selecting Servers > Application Servers > server_name > Performance Monitoring Service on the Administrative Console. The Reset button on this panel should reset the panel's values to the current local configuration values; however, it doesn't. The Startup checkbox, the Initial Specification Level radio buttons, and the specification list do not return to their local configuration values. (MD20284) When using JMS, the transaction log can fill up due to unnecessarily logging. This may occur when using JMS together with a Connection Factory created under the Integral JMS Provider or under external WebSphere MQ in CLIENT mode, since in both of these cases entries will be added to the transaction log corresponding to the associated XAResources. The problem is especially likely to occur if you set a nonzero "AgedTimeout" under your ConnectionFactory's "Connection Pool" properties. The following exception may be seen from the controller region address space: BBOO0220E WTRN0104E: Details of recovery log failure: com.ibm.ws.recoverylog.spi.LogFullException: Maximum file size of 1024k would be exceeded at com.ibm.ws.recoverylog.spi.RecoveryLogImpl.keypoint at com.ibm.ws.recoverylog.spi.LogHandle.getWriteableLogRecord at com.ibm.ws.recoverylog.spi.RecoverableUnitImpl.writeSections at com.ibm.ws.recoverylog.spi.RecoverableUnitImpl.forceSections at com.ibm.ws.recoverylog.spi.RecoverableUnitImpl.forceSections at com.ibm.ws390.recoverylog.spi.ControllerRequestProcessor.dri at com.ibm.ws390.recoverylog.spi.ControllerRequestProcessor.pro (MD20408) An invalid IP address with fields less than 0 or greater than 255 is accepted in Servers->Application Servers-> <server name>->WebContainer->HTTPTransports->host in the administrative console. (MD20576) The controller terminates with an ABENDS0C4/ABEND0C4. The stack trace for the thread which took the 0C4 will be similar to the following: 7C8907E0 +0000017A jni_GetPrimitiveArrayRegion 1E6464C0 +00000BAE BBOT_XaRecoveryTableManager::getCurrentS... 1E7DEFF8 +000005FA BBOT_TransactionManager_CR::work_request... 1EA463C8 +00000BA0 ACR_ExecutionThread::RemoveAndProcessWor... 1EA3DAB0 +00000122 ACR_ExecutionRoutine 063C20B0 -00000106 CEEPGTFN 063C1F50 +0000005A CEEPLPKA The function jni_GetPrimitiveArrayRegion is attempting to access storage at location zero. The zero value was obtained by a failed attempt to get storage due to an out of memory condition in the controller JVM. . Symptoms of this issue can also have the following callback stacks: . jni_GetPrimitiveArrayRegion BBOT_XaRecoveryTableManager::getCurrentSerializedTable (bbotxpdm*) BBOT_TransactionManager_CR::work_request_dispatch(acrwObj&) ACR_ExecutionThread::RemoveAndProcessWork(ThreadCleanUp*) . OR . xeExceptionSignal oemcOutOfMemoryError com/ibm/ws/recoverylog/spi/LogHandle.keypointStarting com/ibm/ws/recoverylog/spi/ServiceLog.keypoint com/ibm/ws/recoverylog/spi/LogHandle.writeRecord com/ibm/ws/recoverylog/spi/RecoverableUnitSection.write com/ibm/ws/recoverylog/spi/RecoverableUnitSection.force com/ibm/ws390/tx/partnerLog/XaRecoveryTableManager.addEntry com/ibm/ws390/tx/partnerLog/ XaRecoveryTableManager.addEntryToCurrentTable INVOKDMY com/ibm/ws390/tx/partnerLog/ XaRecoveryTableManager.addEntryToCurrentTable mmipExecuteJava xeRunJniMethod jni_CallBooleanMethodA BBOT_XaRecoveryTableManager::addEntryToCurrentTable(bbotxpdm*) BBOT_TransactionManager_CR::work_request_dispatch(acrwObj&) ACR_ExecutionThread::RemoveAndProcessWork(ThreadCleanUp*)Problem conclusion APAR PQ98073 fixes the following defect in WebSphere Application Server V5.0 for z/OS. (MD19377) The files that are input to the process of creating the control.jvm.options file have been modified to remove the entry for security.use.localos.authorization = true. (MD19726) Clicking the Reset button on the PMI configuration panel will now restore the panel's values to the current local configuration values. (MD20284) Fixed the logging procedure since we only need to add one entry to the transaction log corresponding to the JMS resources for which we had previously been logging multiple entries. (MD20408) A check is performed when the user selects 'Apply', 'OK' or 'New' that verifies each of the fields in the address is between 0 and 255. If not, an error message is displayed indicating an invalid IP address was entered. (MD20576) Code was added to ensure the value passed to jni_GetPrimitiveArrayRegion is not zero. APAR PQ98073 is associated with SERVICE LEVEL W502020 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: UQ96100 Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PQ98073.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 #: PQ98073
IBM Group: Software Group
Modified date: Mar 22, 2005
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.