PK78840: JAX-RPC ONE-WAY OPERATION FAILS IF WEBSERVICE REQUEST IS VIA WEBSPHERE PROCESS SERVER.

Fixes are available

APAR status

Closed as program error.

Error description

Service Component Architecture (SCA) web service one-way
operation fails. The symptom seen is a lack of data between
the <soapenv:Body> and </soapenv:Body> tags.

This problem does not happen if requester and provider are
both using WebSphere Application Server.

This happens only if WebSphere Process Server is placed between
the sender and the WebSphere Application Server receiver.

The won't happen in (synchronous) request/response style
operation, nor will it happen if the sender is JAX-WS.

Local fix

1) Use request-response style instead of one-way style.
2) Use JAX-WS instead of JAX-RPC.

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
*                  V6.1 and V7.0, who use an SCA client to     *
*                  send a web service message.                 *
****************************************************************
* PROBLEM DESCRIPTION: The web service receives a message      *
*                      that has no content within the soap     *
*                      body. The web service may respond       *
*                      with a fault.                           *
****************************************************************
* RECOMMENDATION:  Install a fixpack that contains this APAR.  *
****************************************************************
The problem is related to how the implementation of the
Service Component Architecture (SCA) programming model
interacts with the base WebSphere Application Server Web
Services Engine. The problem is only related to one-way web
service operations.

The SCA programming model is used by the WebSphere Process
Server (WPS) and Enterprise Service Bus (ESB) products.

Problem conclusion

The interaction between the SCA programming model implementation
and the Websphere Application Server Web Services engine was
corrected.

The fix for this APAR is currently targeted for inclusion in
fixpack 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
PK78840
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
61I
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-01-16
Closed date
2009-02-04
Last modified date
2009-02-04

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

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

PK78840: JAX-RPC ONE-WAY OPERATION FAILS IF WEBSERVICE REQUEST IS VIA WEBSPHERE PROCESS SERVER.

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?