PK75378: NULL POINTER EXCEPTION CAUSED BY FAILURE TO GET MBEAN WHICH LEADS TO STOPDEPLOYMENT FAILURE

Fixes are available

APAR status

Closed as program error.

Error description

In WebSphere Application Server V6.1 on AIX 5.2 there was a
Null Pointer Exception caused by failure to get an mbean. This
causes StopDeployment to fail and it does not perform proper
synchronization in this environment.

StopDeployment runs on the nodeagent process so it will try to
get AdminService for nodeagent. Since nodeagent is actually
running at that time, AdminServiceFactory.getAdminService()
will not return null.


The following errors can be found in the systemout.log of
nodeagent:

[10/15/08 19:34:15:507 CDT] 000016b1 NodeSyncTask  A
ADMS0003I: The
configuration synchronization completed successfully.
[10/15/08 19:34:16:002 CDT] 000016b2 ServiceLogger I
com.ibm.ws.ffdc.IncidentStreamImpl initialize FFDC0009I: FFDC
opened incident stream file.
[10/15/08 19:34:21:016 CAT] 000016b2 ServiceLogger I
com.ibm.ws.ffdc.IncidentStreamImpl resetIncidentStream
FFDC0010I: FFDC closed incident stream file
/usr/WebSphere6.1/AppServer/profiles/prof1/logs/ffdc/nodea
gent_000
[10/15/08 19:34:21:041 CDT] 000016b2 AppBinaryProc E   Exception
from  run: java.lang.NullPointerException

Local fix

```
n/a
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
****************************************************************
* PROBLEM DESCRIPTION: Application update fails for one node   *
*                      in a cluster due to a                   *
*                      NullPointerException.                   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Application update fails for one node in a cluster due to a
NullPointerException. During application update it will
stop the application and it will try to query the Application
MBean. If the Application MBean is not running during this
call it will cause a NullPointerException.

Nodeagent FFDC log showed:
Exception = java.lang.NullPointerException
Source =
com.ibm.ws.management.application.sync.AppBinaryProcessor.run
probeid = 1347
Stack Dump = java.lang.NullPointerException
at
com.ibm.ws.management.application.sync.StopDeploymentTask.stopDe
ployment(StopDeploymentTask.java:150)
at
com.ibm.ws.management.application.sync.StopDeploymentTask.fullAp
pUpdate(StopDeploymentTask.java:129)
at
com.ibm.ws.management.application.sync.StopDeploymentTask.perfor
mTask(StopDeploymentTask.java:74)
at
com.ibm.ws.management.application.sync.AppBinaryProcessor$AppBin
Thread.run(AppBinaryProcessor.java:896)
at java.lang.Thread.run(Thread.java:801)

Problem conclusion

Code was changed to make sure queryNames does not return null
by checking for null and returning an empty Set instead.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.0.2.33, 6.1.0.23 and 7.0.0.3. Please refer to the
recommended updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PK75378
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-11-11
Closed date
2008-12-11
Last modified date
2008-12-11

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
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R60A PSY
UP
R60H PSY
UP
R60I PSY
UP
R60P PSY
UP
R60S PSY
UP
R60W PSY
UP
R60Z PSY
UP
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

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

Document Information

Modified date:
29 December 2021

Tips

PK75378: NULL POINTER EXCEPTION CAUSED BY FAILURE TO GET MBEAN WHICH LEADS TO STOPDEPLOYMENT FAILURE

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

R60A PSY

R60H PSY

R60I PSY

R60P PSY

R60S PSY

R60W PSY

R60Z PSY

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?