APAR status
Closed as program error.
Error description
Problem reported on WSAS 5.0.2
This problem occurs with a wsdl file that specifies a service
with three separate ports, each with its own binding and port
type, and where the different messages associated with the same
operation use different part names for the different port
types. The Gateway can finish up using an incorrect part name
for a binding that is not the target.
This causes an incorrect XML request message (with
xsi:type="apachesoap:Element" inserted) to be sent to the
target service. The target service then returns an error:
Server was unable to read request; Element is an invalid node
type.
Local fix
Graham reported that "A fix to this problem has been devloped
and tested."
Problem summary
****************************************************************
* USERS AFFECTED: In Websphere Application Server Network *
* Deployment, all users of Web Services *
* Gateway with a target service that has *
* multiple ports in its WSDL file. *
****************************************************************
* PROBLEM DESCRIPTION: This problem occurs with a WSDL file *
* that specifies a service with three *
* separate ports, each with its own *
* binding and port type, and where the *
* different messages associated with the *
* same operation use different part *
* names for the different port types. *
* The Gateway can finish up using an *
* incorrect part name for a binding that *
* is not the target. *
* This causes an incorrect XML request *
* message (with *
* xsi:type="apachesoap:Element" inserted) *
* to be sent to the target service. The *
* target service then returns an error: *
* Server was unable to read request; *
* Element is an invalid node *
* type. *
****************************************************************
* RECOMMENDATION: All users of the Web Services Gateway should *
* apply this fix. *
****************************************************************
Incorrect request messages may be sent to a target service that
has multiple ports in its WSDL file.
Problem conclusion
This problem is fixed in the next cumulative fix of WebSphere
Application Server Network Deployment v5.0.2 (Cumulative fix 3)
and in the next cumulative fix of v5.1 (cumulative fix 1).
Temporary fix Comments
APAR information |
APAR number |
PQ79552 |
Reported component name |
WAS NETWRK DEPL |
Reported component ID |
5630A3601 |
Reported release |
00W |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2003-10-13 |
Closed date |
2003-12-08 |
Last modified date |
2003-12-08 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R103 PSY |
UP |
R10A PSY |
UP |
R10H PSY |
UP |
R10I PSY |
UP |
R10P PSY |
UP |
R10S PSY |
UP |
R10W PSY |
UP |
|