APAR status
Closed as program error.
Error description
When a Java service is invoked through WSIF, if the Java method
invoked hangs, WSIF will not timeout waiting for the response.
If an EJB service is invoked through WSIF, if the remote method
invoked hangs or does not respond, WSIF will not timeout. WSIF
will hang waiting for a response.
If a Web Service over SOAP/HTTP is invoked through WSIF, and the
Web Service does not respond, WSIF will not timeout after the
number of seconds specified in the wsif.properties property
"wsif.syncrequest.timeout". This happens for the Apache SOAP
provider and the Web Services for J2EE (Maelstrom) provider.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WSIF. *
****************************************************************
* PROBLEM DESCRIPTION: The wsif properties *
* "wsif.syncrequest.timeout" and *
* "wsif.asyncrequest.timeout" present *
* in the file "wsif.properties" are *
* described in the file as the maximum *
* number of seconds or milliseconds to *
* wait for a response to a request. *
* *
* This is misleading. These properties *
* are not used in all types of Web *
* Service invokation. *
* *
* For example, when invoking a local *
* Java class defined with a Java WSDL *
* binding, these properties are not *
* used. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
This behaviour is a known, designed feature of the WSIF
framework. The code change documents that these properties
are optional for a WSIF provider.
Problem conclusion
Delivered in WebSphere Application Server, version 5.0.2
cumulative fix 10. Delivered in WebSphere Application Server,
version 5.1.1 cumulative fix 4.
Please refer to the Recommended Updates page for delivery dates:
http://www-1.ibm.com/support/docview.wss?rs=180&context=SSEQTP
&uid=swg27004980
Temporary fix Comments
APAR information |
APAR number |
PQ98749 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
10W |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-12-21 |
Closed date |
2005-02-01 |
Last modified date |
2005-02-01 |
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 |
|