Fixes are available
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for IBM i
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Windows
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for AIX
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for HP-UX
7.0.0.9: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Solaris
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Linux
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for IBM i
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Windows
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for HP-UX
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for AIX
7.0.0.11: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Solaris
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
The problem scenario is the following: . web service client web service provider ------------------ -------------------- WAS JAX-WS target external web service --> forward --> web service client proxy endpoint . When a JAX-WS web service client running in WebSphere Application Server V7.0 attempts to call a remote web service over HTTPS, the javax.net.ssl.SSLHandshakeException exception might be logged to WebSphere logs when the call is directed through an HTTP server configured as a forward proxy. You might observe the following entries in a JSSE trace: . [11/12/09 15:14:58:546 CST] 00000019 SystemOut O WebContainer : 1, WRITE: TLSv1 Handshake, length = 63 [11/12/09 15:14:58:546 CST] 00000019 SystemOut O [Raw write]: length = 68 [11/12/09 15:14:58:546 CST] 00000019 SystemOut O 0000: 16 03 01 00 3f 01 00 00 3b 03 01 4a fc 7a d2 be ...........J.z.. 0010: f7 22 05 71 1e de 1e 47 8b 89 73 dd c0 02 e3 9f ...q...G..s..... 0020: 1e b7 a0 48 89 e4 52 47 30 ed 28 00 00 14 00 04 ...H..RG0....... 0030: 00 05 00 2f 00 33 00 32 00 0a fe ff 00 16 00 13 .....3.2........ 0040: 00 66 01 00 .f.. WebContainer : 1, fatal error: 80: problem unwrapping net record javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection? . [11/12/09 15:14:59:171 CST] 00000019 SystemOut O 2009-11-12 15:14:59,171 [WebContainer : 1] ERROR someApplicationCode - Unexpected error occured javax.xml.ws.WebServiceException: javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection? at org.apache.axis2.jaxws.ExceptionFactory.createWebServiceExceptio n(ExceptionFactory.java:175) at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException( ExceptionFactory.java:70) at org.apache.axis2.jaxws.ExceptionFactory.makeWebServiceException( ExceptionFactory.java:128) at org.apache.axis2.jaxws.core.controller.impl.AxisInvocationContro ller.execute(AxisInvocationController.java:559) at org.apache.axis2.jaxws.core.controller.impl.AxisInvocationContro ller.doInvoke(AxisInvocationController.java:118) at org.apache.axis2.jaxws.core.controller.impl.InvocationController Impl.invoke(InvocationControllerImpl.java:93) at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invokeSEIM ethod(JAXWSProxyHandler.java:338) at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invoke(JAX WSProxyHandler.java:159) at someApplicationCode.someMethod(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessor Impl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod AccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:599) at org.apache.axis2.jaxws.server.dispatcher.JavaDispatcher.invokeTa rgetOperation(JavaDispatcher.java:81) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPo stRequest(HTTPTransportUtils.java:275) at com.ibm.ws.websvcs.transport.http.WASAxis2Servlet.doPost(WASAxis 2Servlet.java:1389)
Local fix
N/A.
Problem summary
**************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * Feature Pack for Web Services using a * * forward proxy with HTTPS. * **************************************************************** * PROBLEM DESCRIPTION: If a JAX-WS web service client uses a * * forward proxy with HTTPS, a * * SSLHandshakeException occurs. * **************************************************************** * RECOMMENDATION: Install a Fix Pack which includes this APAR.* **************************************************************** When a JAX-WS web service client attempts to call a remote web service over HTTPS a SSLHandshakeException occurs when the call is directed through an HTTP server configured as a forward proxy.
Problem conclusion
Tunneling was not being used in the web services transport layer for proxies. A JVM property has to be set to true to enable this new behavior. The JVM property is: com.ibm.ws.websvcs.transport.enableProxyTunnel This property is false by default. APAR PK77482 fixes this same problem in the V6.1 WebSphere Application Server Feature Pack for Web Services. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.9. 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
PM01180
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-11-12
Closed date
2009-12-03
Last modified date
2009-12-03
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
R700 PSY
UP
Document Information
Modified date:
24 October 2021