PM79959: NULLPOINTEREXCEPTION DURING JAX-RPC WEB SERVICE INVOCATION

Fixes are available

APAR status

Closed as program error.

Error description

When enableInProcessConnections is set in the Web Container the
problem occurs when the handler operates two web service
endpoints in a single thread. When the first web service
endpoint is accessed, the handler is invoked. At this time the
WebServiceContext it has is for the first Web Service.

It then sends the SOAP message to the second web service
endpoint engine and will create the second WebServiceContext
instance and injects the reference to the same thread.

After the second web service is returned the handler tries to
get the MessageContext from the first WebServiceContext
instance. At that time the reference it holds points to the
second WebServiceContext instance. And as the second web
service has returned, the MessageContext and other resources
inside the second web service instance have been released.

Local fix

```
na
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server using JAX-RPC web services and       *
*                  inProcessConnections                        *
****************************************************************
* PROBLEM DESCRIPTION: NullPointerException during JAX-RPC     *
*                      WebServices invocation                  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When enableInProcessConnections is set in the Web Container,
and one JAX-RPC web service calls another in a stack,
and both are in the same local JVM, both will run on the same
thread.  In some cases this can lead to loss or corruption of
threadlocal data

Problem conclusion

Logic is added to detect this condition and not use the same
thread when the problem might occur.

If problems occur when enableInProcessConnections is active,
the JVM property jaxrpc.useSafeIPC should be set to true.  The
default value is false.

When set, web services calling each other in the same JVM will
not run on the same thread.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.47, 7.0.0.29, 8.0.0.7 and the fixpack after
8.5.0.2.

For information on setting a JVM property see:
http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?
topic=/com.ibm.websphere.nd.doc/info/ae/ae/xrun_jvm.html

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
PM79959
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-01-04
Closed date
2013-03-11
Last modified date
2013-03-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

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP
R800 PSY
UP
R850 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":"610","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 October 2021

Tips

PM79959: NULLPOINTEREXCEPTION DURING JAX-RPC WEB SERVICE INVOCATION

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

R800 PSY

R850 PSY

Document Information

Share your feedback

Need support?