Fixes are available
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR8 Cumulative Fix for WebSphere Application Server
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
A Web Services client cannot connect to the remote provider when the client runs on WSAS v6.1.0.9. The client can connect when deployed to a WSAS v6.0.2.5 test server in RAD. [11/10/07 09:07:34:752 BST] 00000022 PivotHandlerW W com.ibm.ws.webservices.engine.PivotHandlerWrapper invoke WSWS3734W: Warning: Exception caught from invocation to com.ibm.ws.webservices.engine.transport.http.HTTPSender: WebServicesFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalExcepti on faultString: java.io.IOException: Async IO operation failed, reason: RC: 64 The specified network name is no longer available. faultActor: null faultDetail: java.io.IOException: Async IO operation failed, reason: RC: 64 The specified network name is no longer available.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IBM Websphere Application Server users of * * web services. * **************************************************************** * PROBLEM DESCRIPTION: Need option to suppress port numberss * * in outbound http(s) SOAP requests. * **************************************************************** * RECOMMENDATION: * **************************************************************** Some web service implementations do not properly tolerate the presence of the port number within the http POST request that sends the SOAP message.
Problem conclusion
A configurable property may be set to remove the port number if a Websphere Application Server web service client needs to interoperate with such a service. To remove the port number, set: Servers -> Application servers -> <serverName> -> Java and Process Management -> Process Definition -> Java Virtual Machine -> Custom Properties, name=com.ibm.ws.webservices.suppressHTTPRequestPortSuffix, value=true, save the configuration, and restart the server. The fix for this APAR is currently targeted for inclusion in fix pack 6.1.0.15. 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
PK54518
Reported component name
WEBSPH APP SERV
Reported component ID
5724J0800
Reported release
61W
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-10-11
Closed date
2007-10-29
Last modified date
2007-10-29
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
WEBSRVC
Fix information
Fixed component name
WEBSPH APP SERV
Fixed component ID
5724J0800
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
Document Information
Modified date:
28 December 2021