PK32746: Z/OS WEBSPHERE VERSION 6.0.2X ONLY SOCKETCHANNEL CLOSE() ON SOAP FOR WEB SERVICES. | |||||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description WS-AT on z/OS WebSphere 6.0.2.x has encountered a problem for the pure interop case where WebSphere cannot rely on the WAS-WAS deferred registration optimization. This problem has been corrected in WebSphere version 6.1.x. .. In the job-log with tracing enable we saw the following.. .. Trace: 2006/08/23 11:00:15.848 01 t=8C4608 c=UNK key=S2 ThreadId: 0000003a FunctionName: com.ibm.ws.tcp.channel.impl.SocketIOChannel SourceId: com.ibm.ws.tcp.channel.impl.SocketIOChannel Category: FINE ExtendedMessage: SocketChannel close, local: /10.2.100.7:9080 remote: /10.65.4.156:3283 .. The close() called was on com.ibm.ws.http.channel. inbound.impl.HttpInboundLink. .. The customer tried to set requestResendEnabled (com.ibm.websphere.webservices.http.requestResendEnabled) as stated in technote 21202377, but still encounter the problem. .. What I am think was happening was that the client is sending back a HTTP 202 and the SOAP port is timeout. Hence the reason for the close() on the socket. ..Local fix ..Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V6.0.1 for z/OS using Web Services - Atomic * * Transactions (WS-AT). * **************************************************************** * PROBLEM DESCRIPTION: WS-AT on WebSphere Application Server * * for z/OS fails when participating * * with a non-WebSphere coordinator. * **************************************************************** * RECOMMENDATION: * **************************************************************** 1. An invocation is made on a web service in WebSphere Application Server running on z/OS with a WS-AT transaction context. 2. The application server should register with the transaction coordinator, and get the transaction coordinator address from the WS-AT transaction context. 3. The transaction coordinator should then send the register response back to WebSphere Application Server. At this point, the Web Service running on the application server is expected to process the request that was received in 1. above and send a response back to the application running on the originating coordinating server. The response is not being sent, with the port eventually timing out. WS-AT running on WebSphere Application Server for z/OS incorrectly implemented a deferred registration optimization function that was inappropriate when attempting to register with a non-WebSphere server - the deferred registration model should only be utilized in a non-interop environment.Problem conclusion The WS-AT registration was changed to not use the deferred registration model when participating with a non-WebSphere coordinator. APAR PK32746 is currently targeted for inclusion in Service Level (Fix Pack) 6.0.2.22 of WebSphere Application Server V6.0.1 for z/OS.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PK32746.html
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 601
Software edition:
Reference #: PK32746
IBM Group: Software Group
Modified date: Sep 11, 2007
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.