PK93531: A WEB SERVICE CLIENT USING THE JAVAX.XML.RPC.CALL API MIGHT FAIL WITH A NULLPOINTEREXCEPTION.

Fixes are available

APAR status

Closed as program error.

Error description

A web service client that uses the javax.xml.rpc.Call API to
invoke a web service might fail with the following error:

Caused by: java.lang.NullPointerException
at
com.ibm.ws.webservices.multiprotocol.ServiceContext.getPortBindi
ngNamespace(ServiceContext.java:455)
at
com.ibm.ws.webservices.multiprotocol.AgnosticCall.getProtocolNam
espace(AgnosticCall.java:384)
at
com.ibm.ws.webservices.multiprotocol.AgnosticCall.getProtocolS
pecificCall(AgnosticCall.java:343)
at
com.ibm.ws.webservices.multiprotocol.AgnosticCall.invoke(Agnosti
cCall.ja va:217)
at
com.ibm.ws.webservices.multiprotocol.AgnosticCall.invoke(Agnosti
cCall.ja va:194)
...

Local fix

```
No work-around.
```

Problem summary

****************************************************************
* USERS AFFECTED:  Users of JAX-RPC clients that use           *
*                  the javax.xml.rpc.Call API to invoke web    *
*                  services.                                   *
****************************************************************
* PROBLEM DESCRIPTION: A JAX-RPC client using the              *
*                      javax.xml.rpc.Call API might fail       *
*                      with a NullPointerException.            *
****************************************************************
* RECOMMENDATION:  Install a fixpack that contains this APAR.  *
****************************************************************
Consider a client that, after instantiating a
javax.xml.rpc.Call object, does the following:

import javax.xml.namespace.QName;
...
call.setPortTypeName(new
QName("http://com.sample/Hello","HelloWorldPortType");

Upon calling the invoke(QName, Object[]) method on this Call
object, this NullPointerException would occur:

Caused by: java.lang.NullPointerException
 at
com.ibm.ws.webservices.multiprotocol.ServiceContext.getPortBindi
ngNamespace(ServiceContext.java:455)
 at
com.ibm.ws.webservices.multiprotocol.AgnosticCall.getProtocolNam
espace(AgnosticCall.java:384)
 at
com.ibm.ws.webservices.multiprotocol.AgnosticCall.getProtocolSpe
cificCall(AgnosticCall.java:343)
 at
com.ibm.ws.webservices.multiprotocol.AgnosticCall.invoke(Agnosti
cCall.java:217)
 at
com.ibm.ws.webservices.multiprotocol.AgnosticCall.invoke(Agnosti
cCall.java:194)
...

Problem conclusion

The web services engine was fixed so that the internal object
being invoked is no longer null, preventing the
NullPointerException.

The fix for this APAR is currently targeted for inclusion in
fix pack 6.1.0.29 and 7.0.0.9  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
PK93531
Reported component name
WAS WEB 2.0 FEA
Reported component ID
5724J0852
Reported release
61I
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-08-10
Closed date
2009-09-24
Last modified date
2009-09-24

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 APP S
Fixed component ID
5724J0800

Applicable component levels

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

PK93531: A WEB SERVICE CLIENT USING THE JAVAX.XML.RPC.CALL API MIGHT FAIL WITH A NULLPOINTEREXCEPTION.

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

Document Information

Share your feedback

Need support?