PK82030: JAVAX.MANAGEMENT.INSTANCENOTFOUNDEXCEPTION ATTEMPTING TO START LISTNERPORT JMX MBEAN IN ADJUNCT REGION.

Fixes are available

APAR status

Closed as program error.

Error description

When WebSphere Application Server acts as a Message Queue (MQ)
external and a Message Driven Bean (MDB) using Activation
Specs in bindings mode is activated at Server startup time,
an ffdc event may be generated.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
*                  V7.0                                        *
****************************************************************
* PROBLEM DESCRIPTION: When WebSphere Application Server acts  *
*                      as a Message Queue (MQ) external and    *
*                      a Message Driven Bean (MDB) using       *
*                      Activation Specs in bindings mode       *
*                      is activated at Server startup time,    *
*                      an ffdc event may be generated.         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When the ListenerPortMBeanProxy, a proxy for the ListenerPort
java management extensions (JMX) Management bean (MBean), is
activated in the control region, it attempts to start the
ListenerPort MBean in the servant region(s).  It also
incorrectly attempts to start the ListenerPort MBean in the
adjunct region.  This results in an ffdc event which looks like:
FFDC Exception:javax.management.InstanceNotFoundException
SourceId:com.ibm.ws390.management.connector.corba.
  CorbaConnectorImpl.invokeTypeName ProbeId:864
Reporter:com.ibm.ws390.management.connector.corba
  .CorbaConnectorImpl@6ea56ea5
javax.management.InstanceNotFoundException
 at com.ibm.ws390.management.connector.corba.CorbaConnectorImpl
  .invokeTypeName
 at com.ibm.ws390.management.connector.corba
  ._CorbaConnectorImplBase._invoke
 at com.ibm.ws390.orb.CommonBridge.invoke
 at com.ibm.ws390.orb.ORBEJSBridge.invoke
 at sun.reflect.NativeMethodAccessorImpl.invoke0
 at sun.reflect.NativeMethodAccessorImpl.invoke
 at sun.reflect.DelegatingMethodAccessorImpl.invoke
 at java.lang.reflect.Method.invoke
 at com.ibm.ws390.orb.parameters.ORBEJSBridgeInvoke.
   ORBEJSBridgeInvokeParmSetter
Aside from the ffdc event which is generated, no harm results.

Problem conclusion

The code has been modified such that activation of the
ListenerPort MBean is not attempted in the adjunct region.

APAR PK82030 is currently targeted for inclusion in
Service Level (Fix Pack) 7.0.0.5 of WebSphere
Application Server.

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
PK82030
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-03-06
Closed date
2009-03-17
Last modified date
2009-08-03

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
WEBSPHERE FOR Z
Fixed component ID
5655I3500

Applicable component levels

R700 PSY UK48200
UP09/07/27 P F907

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"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
10 February 2022

Tips

PK82030: JAVAX.MANAGEMENT.INSTANCENOTFOUNDEXCEPTION ATTEMPTING TO START LISTNERPORT JMX MBEAN IN ADJUNCT REGION.

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

R700 PSY UK48200

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?