PQ78455: 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 PQ78455 addresses various defects * * in WebSphere Application Server V5.0 * * for z/OS. * **************************************************************** * RECOMMENDATION: * **************************************************************** APAR PQ78455 addresses the following defects in WebSphere Application Server V5.0 for z/OS: (MD17830) In the administrative console, Plugin ID for the location service daemon panel for help needs to point to the environment module. Navigate to: System Administration -> z/OS Location Service config view. The help links do not work. (MD17887) The JMX MBean state support failed to check for a null object name before invoking the local MBean server to get the MBeanInfo for the object name. This results in the following stacktrace: Unable to obtain MBean state data; javax.management.RuntimeOper ationsException: JMXcr0002E Invalid object name. at com.tivoli.jmx.MBeanRepository.checkObjectName(Unknown Source) Note that no harm is caused by the exception reported in this stacktrace as the exception is caught and processing resumes just as if the MBean server had not been invoked to obtain the MBeanInfo. (MD17909) Removing Node from the configuration with $AdminConfig remove command will corrupt configuration. AdminConfig remove comand allows users to remove Node without any kind of checking. The remove command should remove servers only and if user wants to remove a node, a warning message should be given to the user. (MD17950) PMI Request Metrics is not supported in WebSphere V5.0 for z/OS. A link to configure it exists on the administration console on the Navigation panel. This has to be removed. (WS13585.14) The feature provides support for dynamicproxy MBean extensions through new application programming interfaces. Plus it enables aggregation support for PMI related MBeans. This feature enables dynamicproxy MBean extensions through the following application programming interfaces (APIs): package: com.ibm.websphere.management.dynamicproxy interfaces: AggregationHandler, EventHandler, InvocationHandler classes: StateObject This support requires that each MBean provider implement the correct interfaces to provide user provided hook points and update their MBean descriptors to specify their own implementations. Following describes each API: 1. AggregationHandler DynamicProxy MBean result aggregation handler interface. Implementation of this interface can be specified in MBeanDescriptor's MBean xml tag's attribute called "aggregationHandlerClass." This interface defines the method that must be implemented by MBean provider who wants to handle result aggregation in dynamicproxy enabled MBean for WebSphere for z/OS for all MBean methods that uses "multicall" or "spray" proxyInvokeType and returns a return value. Implementation of this interface should be able to first determine exactly which method this aggregation is to be processed for and then properly aggregate all servant MBeans' results that are passed in and compile up a single result to be returned. 2. EventHandler DynamicProxy MBean event aggregation handler interface. Implementation of this interface can be specified in MBeanDescriptor's MBean xml tag's attribute called "eventHandlerClass." This interface defines the method that must be implemented by MBean provider who wants to handle event aggregation in dynamicproxy enabled MBean for WebSphere for z/OS. Implementation of this interface should be able to properly handle all incoming servant MBeans' events & aggregate them to filter out duplicate events from multiple SR MBeans and send only ONE event back to the listener of this dynamicproxy MBean. Also implementation of this class should be able to properly adjust the current dynamicproxy MBean's state accordingly to MBean provider's requirements. 3. InvocationHandler Invocation handler interface for dynamicproxy MBean which requires more rich & customized state management before and after invoking its MBean's method. Implementation of this interface can be specified in MBeanDescriptor's MBean xml tag's attribute as "invocationHandlerClass." This interface defines the preInvoke and postInvoke methods that can be implemented by WebSphere for z/OS dynamicproxy MBeans that require state management information in order to properly coordinate with its associated servant MBeans in cases where multicall invoke type is required. 4. StateObject StateObject abstract class which needs to be extended by the MBean provider. Subclass of this StateObject can be specified in MBeanDescriptor's MBean xml tag's attribute called "stateObjectClass" in order for runtime to new it up before the dynamicproxy MBean completes its initialization & attach it onto dynamicproxy's InvocationHandler for keeping track of dynamicproxy's current state. It is implementation provider's responsibility to make sure that their code is reentrant. example MBeanDescriptor header: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE MBean SYSTEM "MbeanDescriptor.dtd"> <MBean type="SampleStateMBean" aggregationHandlerClass="joe.bob.SampleAggregationHandler" eventHandlerClass="joe.bob.SampleEventHandler" invocationHandlerClass="joe.bob.SampleInvocationHandler" stateObjectClass="joe.bob.SampleState" version="5.0" platform="dynamicproxy" description="Sample state MBean.">Problem conclusion APAR PQ78455 fixes various defects in WebSphere Application Server V5.0 for z/OS. (MD17830) Changed the plugin ID for the help panel in the location service daemon config view to point to the environment module instead of the z/OS module. (MD17887) The JMX MBean state support was modified to check if the MBean proxy object name is null. The local MBean server is now only invoked to obtain the MBean info for the MBean proxy if the MBean proxy object name is not null. (MD17909) Support has beem modified to check if the config id is a type Node then give a warning message and instructions so user can do the correct steps required or reset the change. (MD17950) Removed the PMI Request Metrics link from the administrative console. (WS13585.14) Current dynamicproxy MBean functionality is being extended to provide more flexible and complete support for user-supplied hook points for various types of actions such as result aggregation handling, event aggregation handling, invocation pre/post handling, and state management. PMI related MBeans will exploit the aggregation handling support to aggregate their servant MBeans' results within their controller dynamicproxy enabled MBean using this new support. APAR PQ78455 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: UQ80304 Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PQ78455.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 #: PQ78455
IBM Group: Software Group
Modified date: Oct 3, 2003
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.