PM05963: NullPointerException error may occur after a JAX-RPC Handler is deleted.

Fixes are available

APAR status

Closed as program error.

Error description

A NullPointerException error may occur after a JAX-RPC Handler
is deleted.

Here is an example:

[18/08/09 22:03:57:586 CEST] 0000034f PivotHandlerW E
com.ibm.ws.webservices.engine.PivotHandlerWrapper
bindExceptionToResponse WSWS3400I: ...

java.lang.NullPointerException
at
com.ibm.ws.webservices.engine.handlers.jaxrpc.JAXRPCHandler$2.
invoke(JAXRPCHandler.java:415)

Local fix

```
n/a
```

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server V6.1 and   *
*                  V7.0 users of JAX-RPC web services          *
****************************************************************
* PROBLEM DESCRIPTION: A NullPointerException may occur if a   *
*                      handler is deleted during a JAX-RPC     *
*                      web service invocation.                 *
****************************************************************
* RECOMMENDATION:  Install a fixpack containing this APAR      *
****************************************************************
If a handler is deleted during a JAX-RPC web service
invocation, an exception similar to the following may occur:

NullPointerException

[18/08/09 22:03:57:586 CEST] 0000034f PivotHandlerW E
com.ibm.ws.webservices.engine.PivotHandlerWrapperbindExceptionTo
Response WSWS3400I:...

java.lang.NullPointerException          at
com.ibm.ws.webservices.engine.handlers.jaxrpc.JAXRPCHandler$2.in
voke(JAXRPCHandler.java:415)

Problem conclusion

During a JAX-RPC web service invocation, another thread
initiates the deletion of a handler which causes the
handlerChain value in the JAXRPCHandler object to be set to
null.  The code in JAXRPCHandler was not checking for a null
handlerChain before attempting to invoke the handler.  The
code is corrected to check for a null value.  If the
handlerChain value is null, it is skipped.  Otherwise the
handler is invoked.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.31 and 7.0.0.11.  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
PM05963
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
61I
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-01-25
Closed date
2010-02-22
Last modified date
2010-02-22

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

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:
28 December 2021

Tips

PM05963: NullPointerException error may occur after a JAX-RPC Handler is deleted.

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

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?