PK80836: java.lang.String[] objects may be serialized incorrectly by JAX-RPC Web Services

Fixes are available

APAR status

Closed as program error.

Error description

JAX-RPC Web Service clients may serialize java.lang.String[]
objects incorrectly. This usually causes an exception
on the receiver of the SOAP message.

Local fix

```
N/A.
```

Problem summary

****************************************************************
* USERS AFFECTED:  WebSphere Application Server JAX-RPC        *
*                  clients that invoke multiple web services   *
*                  with String[] arguments.                    *
****************************************************************
* PROBLEM DESCRIPTION: The java.lang.String[] argument to the  *
*                      web service may be serialized           *
*                      incorrectly.                            *
****************************************************************
* RECOMMENDATION:  Install a Fix Pack which contains this APAR.*
****************************************************************
JAX-RPC defines a standard mapping of java.lang.String[]
objects to xml.

There are certain other xml patterns that map to
java.lang.String[].

If a client JAX-RPC stub uses the standard String[] mapping,
the mapping is stored in the JAX-RPC TypeMappingRegistry.

If a second JAX-RPC stub (for a different web service running
in the same JVM) has an alternative java.lang.String[]
mapping, the mapping is stored in the same JAX-RPC
TypeMappingRegistry.

These two different mappings are differentiated by
the xml QName associated with the mapping.

According to the JAX-RPC Specification, the JAX-RPC web service
engine obtains the mapping from the TypeMappingRegistry when
it converts the java.lang.String[] into xml.  The JAX-RPC
engine uses the QName defined in the wsdl/xml to obtain the
correct mapping.

In some cases, the QName key is not known.
For example, if a bean property is declared as a
java.lang.Object and the actual object is a
java.lang.String[], there is no QName.  In such cases, the
JAX-RPC engine is supposed to use the standard mapping.

If the engine obtains the wrong mapping from the
TypeMappingRegistry, an incorrect message will be
serialized.  The receiver of the message will likely fail.

In the failing scenario, there are multiple JAX-RPC stubs for
different web services.  One of the stubs references a
java.lang.String[] object from a java.lang.Object bean
property.  The engine obtains the wrong mapping and serializes
incorrect data.  The receiver (the web service) of the message
fails.

Problem conclusion

IBM's implementation of the TypeMappingRegistry is
hierarchical.  The standard mappings are at the bottom of the
hierarchy and the specific mappings are at the top of the
hierarchy.  Due to an error in the search algorithm, the
specific mapping was chosen instead of the standard mapping.
Due to the nature of the algorithm, this fix is limited to
objects of type java.lang.String[].

The search algorithm is corrected to obtain the standard
mapping for java.lang.String[] when the QName is not known.

The fix for this APAR is currently targeted for inclusion in
fixpack 6.0.2.35, 6.1.0.25, and 7.0.0.5.  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
PK80836
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
2009-02-17
Closed date
2009-03-09
Last modified date
2009-03-09

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

Tips

PK80836: java.lang.String[] objects may be serialized incorrectly by JAX-RPC Web Services

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?