PK76950: AVOID EXTRANEOUS STACK TRACE WHEN Z/OS MBEAN PROXY NOT A NOTIFICATION HANDLER

Fixes are available

APAR status

Closed as program error.

Error description

During the start of any application server, three
java.lang.ClassNotFoundExceptions occur in its control region:
- com.ibm.ws390.management.proxy.SchedulerMBeanProxy
- com.ibm.ws390.management.proxy.EndpointMBeanProxy
- com.ibm.ws390.management.proxy.GridEndpointMBeanProxy
CNFE CNFEs
.
These are benign but are confusing to the customer when
examining the logs for other issues.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
*                  V6.1.0 for z/OS                             *
****************************************************************
* PROBLEM DESCRIPTION: During application server startup,      *
*                      java.lang.ClassNotFoundException may    *
*                      be seen in the control region JVM logs. *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
During server startup, when the Control Admin Service attempts
to register the proxy MBean (Java Management Extensions (JMX)
management bean) for the Scheduler, Endpoint, and/or
GridEndpoint MBeans, a java.lang.ClassNotFoundException
exception like the following may be seen:

java.lang.ClassNotFoundException:
  com.ibm.ws390.management.proxy.SchedulerMBeanProxy
    at java.lang.Class.forNameImpl(Native Method)
    at java.lang.Class.forName(Class.java:130)
    at com.ibm.ws.management.descriptor
       .MBeanDescriptorLoader.setProxyOperationInfo
    at com.ibm.ws.management.descriptor
       .MBeanDescriptorLoader.setDescriptorFields
    at com.ibm.ws.management.descriptor
       .MBeanDescriptorLoader.parseMBeanInfo
    at com.ibm.ws.management.descriptor
       .MBeanDescriptorLoader.startElement
    at org.apache.xerces.parsers.AbstractSAXParser.startElement
...

The exception is seen because there is no MBean proxy defined
since the MBean does not implement the ServantNotification
Interface, which it is not required to do.

Problem conclusion

The code has been modified such that the stack trace is not
printed unless the finest trace level is requested.

APAR PK76950 is currently targeted for inclusion in
Service Level (Fix Pack) 6.1.0.23 of WebSphere
Application Server V6.1 for z/OS.

Please refer to URL:
//www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
for Fix Pack availability.

Temporary fix

Comments

APAR Information

APAR number
PK76950
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-12-04
Closed date
2008-12-15
Last modified date
2009-06-30

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

PK90244

Fix information

Fixed component name
WEBSPHERE FOR Z
Fixed component ID
5655I3500

Applicable component levels

R610 PSY UK44403
UP09/03/21 P F903

Fix is available

Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK76950: AVOID EXTRANEOUS STACK TRACE WHEN Z/OS MBEAN PROXY NOT A NOTIFICATION HANDLER

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R610 PSY UK44403

Fix is available

Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

Document Information

Share your feedback

Need support?